Outlook 2019 Loading Profile Stuck
There are a few things that could cause your issue. One of them is that the latest Office version (including 365 and 2019) are trying to connect to autodiscover via https instead of http. When this is not active, a timeout occurs causing a delay. This can happen if load balancing the exchange environment and only using http for autodiscover.You can follow your autodiscover methods by starting outlook, right clicking the outlook icon in the sys tray with Ctrl pressed and click on something like test autodiscover.
Outlook won't connect to 365. Stuck on trying to connect (self.Office365) submitted 2 years ago by jazzauk. If repairing your Outlook data files didn't resolve your issue, move on to the next step. Step 6: Create a new user profile. Your profile stores a variety of settings that control how Outlook looks and feels. You can create a new profile and then add your email accounts to the new profile. Close Outlook.
There are three check marks, only leave autodiscover enabled and test. Check where the delay is.If this does not shows a delay you have to dive deeper with procmon.exe and/or wireshark to see if tcp connections are made without replies.Another one is outlook trying to find your tenant within office 365 first, also causing delays. You can disable this with a reg key:HKEYCURRENTUSERSOFTWAREPoliciesMicrosoftoffice16.0outlookautodiscoverDWORD: ExcludeExplicitO365EndpointValue = 1Next gen firewalls hav8ng a web filter are also known for delaying connections to exchange (and office 365). Thank you for the detailed answer. Https is configured on our side, so this won't be an issue.I filtered procmon on send/receive and noticed a 22 second delay after it started sending packets to and.It succesfully received packets from on https, but then it waited 22 seconds, to resume sending packets to our actual mailserver.The procmon starts with sending packets to our mailserver, but then transitions to that 40.x and 52. Wan ip, which are unkown to me.Any thoughts on this?concerning the reg key: for us i had to place this in HKEYCURRENTUSERSOFTWAREMicrosoftoffice16.0outlookautodiscover(so not in policies)I tried doing a gpupdate /force on server and logging in with a user account but the results were the same. After some trial and error I have reached the following conclussions: the reg key does not improve the speed of loading profile.I ran a procmon and it pretty much shows the following:Connects to 52.X and 40.X wan ip, receives packets, and then it hangs for 20-30 seconds on: TCP reconnect to our dns wan ip for autodiscover on https.I tries to reconnect 2 times, and then it proceeds to send to the dns record of that wan ip.The weird part is that I have other domains where it does load fast.
It seems o2019 doesn't like some of our autodiscover wan records. Very strange.
Hi All,After upgrading in house Exchange 2016 from CU5 to CU7, I noticed all Outlook 2016 CTR stuck at Loading Profile for more than 60 secs. After it is connected, everything is normal.I have tried following steps to check:. Tried with Office 2013 CTR, Outlook loads straight away. Web OWA is normal - No problem with server. Outlook connection test is normal. Delete all profiles, add new one. Still stuck at loading.
Disable Cache mode. Disabled all Add-in, Hardware graphic acceleration. Disable AV. Outlook.exe /safeOutlook.exe /safe fixes just for a day or after a few closing/opening, Loading profile comes back again.There is no difference in term of Avg Resp, Avg Proc when Outlook loading fast & slowI now also notice the message 'Microsoft Outlook is synchronizing folders' appear and stay quite often. Rarely seen that before.Outlook should show Starting then done. Never seen Loading Profiles message before CU7 upgrade. CU8 is too new so I am hesitate to upgrade to it at the moment.Could anyone give me a hint how to check and find out what is going on?
Are there some settings changed on server after upgrade?Thanks.Ken. Hi Ken,What’s your detailed Outlook version? Are the users affected by this problem all running the same build of Outlook? Outlook.exe /safe fixes just for a day or after a few closing/opening, Loading profile comes back againAfter closing, do you still open Outlook in safe mode? If Outlook behaves normally in safe mode, this issue could be related to third-party add-ins.In that case, please open Outlook and go to File Options Add-ins. Select COM Add-ins and then click Go. Uncheck the Add-ins in the list one by one and then restart Outlook to eliminate the problematic add-in.Any updates, please feel free to post back.Regards,PerryPlease remember to mark the replies as answers if they helped.
If you have feedback for TechNet Subscriber Support, contact. Click to learn more. Visit the dedicated to share, explore and talk to experts about Microsoft Teams. Ken and Perry,I have encountered the exact same set of circumstances over the last month. In Mid-December the issue began occurring. About 50 clients using the same Office 2016 click-to-run install. The issue does not occur on clients with full openlicense, only on those with click-to-run install.
(Version 1711, Build 8730.2165 Click-To-Run)One difference is that we are running our own Exchange 2013 CU19 (though we were running CU16 when the problem first began. I migrated to CU19 as one of the attempts to resolve). This would indicated that the problem is not with Exchange 2016CU7 as you were thinking. Prior to installing 2013 CU19, we hadn't updated the CU on our Exchange server for 6+ months.I'm very encouraged that my Outlook symptoms are the same as yours Ken.
At least I'm not going crazy!Outlook.exe /safe will resolve the issue until opening and closing Outlook in normal mode a few times, or by the next morning problem with 'loading profile' for 45-120 seconds returns.My Attempts to resolve:- Disable all add-ins (no effect)- Disable Symantec Endpoint (no effect)- Rebuild Outlook profile (no effect)- Attempt online rather than cached mode (no effect)- Quick Repair of Office (no effect)- Online Repair of Office (no effect)- Outlook 2013 or 2010 do not experience the same issueSymptom remains. I'm very frustrated because my user community is complaining daily! I sure hope Microsoft gets on this issue soon! I have got loads of time invested in troubleshooting!Please keep me updated on your progress, guys. I'll do the same, Gary. Hi Ken,Thank you for your update.I’d like to suggest you to create a new profile and add a different account(not an Exchange 2016 CU7 account).
Outlook 2019 Stuck Loading Profile
Then try to launch Outlook using the new profile to check whether the issue is related to Exchange 2016 CU7.Besides, since this issue occurs to many users, we could also try on one problematic computer and then see if issue persists. This helps eliminate whether the issue was caused by any software conflicts.Regards,PerryPlease remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact. Click to learn more.
Outlook 2019 Loading Profile Stuck On Yahoo
Visit the dedicated to share, explore and talk to experts about Microsoft Teams. Perry,You indicate you need more information to isolate the problem. What you are suggesting, we have already done.1) It is not Exchange, as the same problem occurs on different versions of locally hosted Exchange (2010, 2013 CU19, and 2016 CU7).
Hi Perry,Gary's response was exactly what I was trying to say. We have tried all those tests and the outcome would confirmed Outlook 2016 CTR (365 as well?) problem.Problem still remains on latest build 8827.2148I just downgraded my Outlook to build 16.0. 8229.2086 perpasci2132's comment and confirmed thatOutlook starts fast instantly with this build. So problem started to begin some where between 8229.2086 and 8730.2165 build.Please investigate this MS!!!However, downgrade is not a solution because it will update to latest version again itself.Thanks pasci2132 for your great idea. I did not know that we can downgrade using command same as upgrade.Office 2016 CTR keeps officec2rclient.exe at C:Program FilesCommon Filesmicrosoft sharedClickToRun.Cheers,Ken. Hi,This issue has been submitted in an internal way.
Any updates, I will post back to inform you. Currently, you could revert to a previous version of Office as a workaround.However, downgrade is not a solution because it will update to latest version again itself.To prevent the newest version of Office Click-to-Run from being automatically reinstalled, follow these steps:1. Click File, and then click Office Account.2. In the Product Information column, click Update Options, and then click Disable Updates.You could also refer to for more information.Thank you for your understanding and support.Regards,PerryPlease remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact. Click to learn more.
Visit the dedicated to share, explore and talk to experts about Microsoft Teams. Thank you for Perry and Gary's response.Just want to add a note here if anyone wants to downgrade.After downgraded, Outlook worked normally but I got error related to office cached when trying to opening Word, Excel files. The file does not open when first double click on the file.
Double click again, a pop up windows asking to repair cached then Word,Excel content is displayed.Updated to latest build again, no more office cached issue, but of course stuck at Loading profile again.So I'm not recommend to rollback for many users.Cheers,Ken. Hi guys,I had the exact same problem on my system here but unfortunately the downgrade didn't solve the issue. But the build in troubleshooting tool told me that is has connection problems with IPv6. So I disabled IPv6 and upgraded to version 16.0.8827.2131using the command line and now it is solved.So not sure what really solved the problem (either disable IPv6 or down- and upgarde) but I'm happy and wanted to say thanks to everyone here. It was a livesaver and brought me to the right direction.Eike. Hi guys,I had the exact same problem on my system here but unfortunately the downgrade didn't solve the issue. But the build in troubleshooting tool told me that is has connection problems with IPv6.
So I disabled IPv6 and upgraded to version 16.0.8827.2131using the command line and now it is solved.So not sure what really solved the problem (either disable IPv6 or down- and upgarde) but I'm happy and wanted to say thanks to everyone here. It was a livesaver and brought me to the right direction.EikeHi Eike,Good to know something had worked for you.I did downgrade and upgrade but did not help. Probably ipv6 related.Where did you disable ipv6? Exchange server or Client?Does anyone know if there is any consequences after disabling ipv6?Regards,Ken.