>Rename C:\Program Files (x86)\Microsoft Office\ folder to _Microsoft Office_oldįaulting module name: OUTLOOK.EXE, version: 1.20266, time stamp: 0x5ef2a169įaulting application start time: 0x01d65ad12c696e89įaulting module path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.In this article I explain the way to backup your Outlook account settings and then restore (transfer) them to another computer. > O365/Outlook repair installation (long version) with reboot.
> Attempt to load new Outlook profile with same user account creds. I am seeing the same thing on one client desktop, at first with an older version, then after troubleshooting same version as listed in initial thread. Just figured I would let everyone else know, they are not alone! Ran the Microsoft Support and Recovery AssistantĪt this point I'm going to hold off additional troubleshooting until MS provides an update. Tried the registry fix outlined here (one of my users had Office V16):ĥ. One thing to note: This does not seem limited to Exchange Online users as I've received calls from people using GSuite as well.
I have checked the event viewer on a few systems so far and this is the common message across all of them (Event ID 1000).įaulting application name: OUTLOOK.EXE, version: 1.20266, time stamp: 0x5ef2a169įaulting module name: mso98win32client.dll, version: 0.0.0.0, time stamp: 0x5ef2771fįaulting application start time: 0x01d65ac7a6b5d1b9įaulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXEįaulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso98win32client.dll Others report Outlook opens for a few seconds, then crashes. Some users report they cannot get past the "Loading profile" message before Outlook crashes. 100% of the calls have been in reference to the Outlook app crashing. I've had a barrage of phone calls this morning regarding this issue.
0 kommentar(er)
