Situation: We have got a lot reports that Outlook opens and closes right away after Windows 10 updates.
Also Outlook or Office repair takes forever. It doesn’t fix the problem. outlook.exe /safe has the same problem.
Troubleshooting: 1. Uninstall update KB4565483, KB4565633, KB4565503
2. Install KB4560960.
3. Roll back Microsoft Office to latest June 2020 release. To do that, please follow these steps:
- Open a command prompt by typingCMD in search bar. Click on ‘Command Prompt’ .
- In the command prompt type
cd "\Program Files\Common Files\microsoft shared\ClickToRun"and press enter. - You will now be in the ClickToRun folder. Type
officec2rclient.exe /update user updatetoversion=16.0.12827.20470and press enter. - Microsoft Office is downloading the previous version of Microsoft Office.. It may take a few minutes to complete.
- When the roll back complete, you will see a screen stating ‘Updates were installed.’ You can press the Close button on this screen.
- Now, you ca test the Outlook.
Please view this step by step video:
3. Downlead ODT. Download Office Deployment Tool from Official Microsoft and re-install.
4. Try System Restore.
Please view the step by step video:
Run Windows System Restore to restore your system to an earlier state
Update
Microsoft 365 Admin Centers have alerts about this issue. This is the message on the Active Investigation page:
“There is a new symptom of Outlook is crashing on launch starting 7/15. A fix has been published but will take time to propagate to worldwide availability. Outlook will automatically look for the fix on launch, so if this issue persists through multiple launches please use Outlook Web Access for an hour then try again.
If this issue persists beyond four hours please contact Microsoft Support by whichever means works best for you.”
Link to the investigation page: https://support.microsoft.com/en-us/office/active-investigation-into-outlook-crashing-on-launch-9c59ad4b-813c-432a-afdc-f14717a4528d?ui=en-us&rs=en-us&ad=us
Also, inside the 365 Admin Center, we were given this ETA: “Estimated time to resolve: We expect this issue to be completely resolved for all affected users by July 15, 2020 at 9:30 PM UTC.”
