If they are, then perhaps you can try deleting this before doing a new install. If this issue occurs, it may be worth to do a full uninstall using the Microsoft tool and then see if these registry keys are still present. Please note I have not done any further research in to this and has not had any other machines where I can replicate this. He has done a few things but as per him, the main changes he did was deleting the following registry keys: But our user, being a programmer, had continued to play with this and gotten it fixed by the next day. This was as far as we got by the end of the work day. It only goes as far as the 27th row where it gets a 401 from the server for authentication. When our user did the Fiddler capture, it showed the following: I am including the above as it shows the process to do a Fiddler capture. SAZ file (it is already a compressed file so there is no need to compress it again).

Save the file on the Desktop -> File > Save > All Sessions.Ĭollect the saved. Open Fiddler and configure HTTPs decryption: Tools > Fiddler Options… > HTTPs, check the Decrypt HTTPs traffic option and acknowledge all the prompts.Ĭlick Rules, select Automatically Authenticate Note: Make sure you closed all the programs on your PC before preceding to Fiddler logs. If both of the provided solutions don’t work please do the following: Before deleting “Identity” please copy and save it in your desktop.

Right-click the Identity key and choose Delete.

If you are Office 20 users, open this key in the Registry Editor: HKEY_CURRENT_USER > Software > Microsoft > Office > 16.0 > Common > Identity.

If the Problem persists please do the following: Microsoft support, in their infinite wisdom, suggested the following to assist: In this particular instance even this did not result in any progress. So please try this first as this is typically a safe process.

Using this tool and installing again from the Office 365 portal usually fixes most problems. A more complete uninstall can be achieved by using the Office Removal Tool. This does not mean the ‘Online repair’ accessible through the Control Panel – Uninstall a Program. One of the common processes that fixes issues with a local Outlook install is to do a re-install. A test Office 365 cloud account newly set up had the same issue on the affected machine, so it was something local.

The user could log in on another machine in the same network with his account. If we tried to add a new profile it will still be stuck retrieving profile data. The Outlook would get stuck at loading the profile stage. This was on an up-to-date Outlook on a Office 365 user at the time of this post. This post is on a resolved but no-idea-what-fixed-it issue related to Outlook.

Outlook 2019 hangs at loading profile