I don't know what the normal procedure is, but that doesn't make any sense I think. Also removing the other autodiscover options via Regedit doesn't seem to make a difference. But it seems that Outlook now check this autodiscover redirect on starting Outlook when it has already beenĬonfigured. I know it's normal for an Exchange account which relies on "http redirect" to have to wait on the initial configuring outside the network. I've tested from those location the "http redirect" manually and it responds immediately.Īlso show that everything is OK (tested with autodiscover). After another 10 sec it does it again and then it immediately gets the connection and Outlook opens.
What I saw, was that Outlook not untill 15 sec reached out to the site. So after checking all the "normal" causes, I also ran a procmon. Outlook on the customers side (tested on clean installs and clean profiles from different locations) experience a ~35sec delay since a few months. Our own company mailbox has no issues starting up, it start within 3 sec (also remotely). We run a multi-tenant Exchange environment.Īs a result we use the "http redirect" function for the different customers in this environment. Why does Outlook search other network adapters? I also you recommend to just disable any network adapter you're not using. Tried the "Run this program in compatibility mode for" on the shortcut.Īfter this, outlook would open within 5 seconds and not hang on loading profile anymore. Ran the SARA (Support and Recovery Assistance) troubleshootingġ2. Started outlook.exe /safe which opens fast.ġ1. Deleted the Outlook folder (including all OST files) and let things get re-created.Ħ.
Full repair (gave me an error and used Microsoft's tool to remove all office projects and re-installed everything.)Ĥ. Outlook 2016 hangs on loading profile for over 2 minutes.ģ. Is anyone else having this issue? Does anyone have any ideas that I have not tried? So, I'm asking them to deal with the problem until I can find a solution. I can't ask my users to run Outlook.exe /safe multiple times a week to make the problem goĪway. Disabling Hardware Acceleration has no effectīecause this is so widespread, and it is only occurring on those clients that have the click-to-run installation, it's actually a pretty big pain in the neck. Delete and rebuild profile has no effect.ĥ. Outlook.exe /safe makes the problem go away on any given client, but it returns within a few hours, making this solution highly unfeasible for obvious reasons.Ģ.
I have tried the following,īut have been unable to make the problem go away completely.ġ. They went from an almost instantaneous load (about a second), to anywhere from 45 seconds to 5 minutes. Installed a standalone Outlook 2016, and the Office 2011 suite is still active.I manage a small company network (about 60 users) with our own Exchange 2013 server and mostly Office 2016 clients.Ībout Dec 20th, 2017 my Outlook clients that are using the retail Click-to-Run installation began loading very slowly. It keeps freezing, spinning the wheel of death, and restarting.
Every 5th or 6th email sent has an error, and gets sent back to my drafts.
Email under a certain category created in the Inbox was gone (folder empty), and was found in the trash folder.ģ. Certain categories disappeared and old emails that were moved to other folders or deleted came back. I will list a few of their stated issues.ġ. Upon syncing back to the exchange server, they started having numerous problems with data, latency issues and freezing. Process, but after the latency issues I removed and re-setup their email accounts.
I initially, just automatically allowed the import of Outlook 2011 data during the install
I was upgrading a few clients from Outlook 2011 for MAC to Outlook 2016 for MAC, and afterwards they complained about Outlook being very slow after each function.