locked
Outlook 2016 crashing on startup. RRS feed

  • Question

  • My installation of Outlook 2016 always crashes upon startup. Always. I tried an upgrade from 2013 as well as a fresh install. I even tried completely reformating my Windown 7 x64 machine and installing Outlook 2016 all over again. But, I always receive the same error.

    These are the problem details:  Problem signature: Problem Event Name: APPCRASH Application Name: OUTLOOK.EXE Application Version: 16.0.4266.1003 Application Timestamp: 55ceb248 Fault Module Name: AppVIsvSubsystems32.dll Fault Module Version: 5.0.10331.0 Fault Module Timestamp: 55843043 Exception Code: c0000005 Exception Offset: 0008a0ac OS Version: 6.1.7601.2.1.0.256.4 Locale ID: 1033 Additional information about the problem: LCID: 1033 skulcid: 1033 Read our privacy statement online:http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

    I tried reading up on the dll file which is a fault module and ALL lead to the same answer that it is related to Microsoft Virtualization engine error and whatever they suggest, nothing is helping out. I have also tried uninstalling via the Fixit tool, and re installed. BUT I get the same error.

    I would also like to add the error alternates between that DLL file and mso30win32client.dll. It just altenates

    Let me just clarify. I have not created any account on Outlook as of now. So, no profiles or OST/PST files are present since no mail account is configured.

    Friday, September 25, 2015 5:53 PM

Answers

  • I had the same issue in my environment and it was due to McAfee HIPS (Host Intrusion Prevention) 8.0.0. Disabling HOST IPS allowed me to run Outlook 2016. The Host IPS API engine was the reason for the crash. Our issue is still being debugged by McAfee.

    • Proposed as answer by PaCpiS Sunday, October 11, 2015 8:20 PM
    • Marked as answer by Steve Fan Monday, October 12, 2015 8:58 AM
    Thursday, October 8, 2015 8:40 PM

All replies

  • Having the exact same issue. Running on Windows 7 within Moka5.
    Friday, September 25, 2015 8:12 PM
  • Have you completely uninstalled Office 2013? Make sure that you have already deleted all products of Office 2013 such as Visio 2013, Project 2013 etc. If no, do it and reinstall Office 2016.

    Let me know if it worked!

    Wednesday, September 30, 2015 5:38 AM
  • I have the same issue.

    However, Outlook 2016 did work well for me for about two weeks. After the latest updates (?) it has stopped working for me.

    (Safe mode still works). I have deactivated all addins, but no change.

    Saturday, October 3, 2015 9:00 PM
  • I have completely removed MS Office. I performed a complete re-format and tried installing this. YET I face this issue. I removed MS Office via the Fixit tool too. Nothing helps.
    Tuesday, October 6, 2015 6:28 AM
  • I had the same issue in my environment and it was due to McAfee HIPS (Host Intrusion Prevention) 8.0.0. Disabling HOST IPS allowed me to run Outlook 2016. The Host IPS API engine was the reason for the crash. Our issue is still being debugged by McAfee.

    • Proposed as answer by PaCpiS Sunday, October 11, 2015 8:20 PM
    • Marked as answer by Steve Fan Monday, October 12, 2015 8:58 AM
    Thursday, October 8, 2015 8:40 PM
  • Thanks a lot MilanD3, you've saved me a lot of headaches !
    Sunday, October 11, 2015 8:21 PM
  • I have the same issues - i upgraded to Office 365/2016 and could not longer start outlook.

    I run Windows 10 - build 105860

    the error is as follows:

    Faulting application name: OUTLOOK.EXE, version: 16.0.4266.1003, time stamp: 0x55ceb433
    Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x568d21f8
    Exception code: 0xc0000005
    Fault offset: 0x00000000000178e8
    Faulting process id: 0x42f4
    Faulting application start time: 0x01d15246f801ca6b
    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE
    Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll
    Report Id: 8f531310-4ec1-4c97-9f53-0418a74d2536
    Faulting package full name: 
    Faulting package-relative application ID: 

    Outlook is a critical application for me - is there something that can be done?

    Monday, January 18, 2016 11:45 PM
  • Bringing this seemingly dead thread back to life because it was way at the top of hits on Bing.

    I've got a user who's Outlook crashes on opening every time, too.

    We're on Office 365. We don't even have Exchange installed. Every other user is having no problems at all.

    I checked for updates, no luck. I wiped out his OST file to see if it was corrupt, no luck. I removed the Outlook folders totally from AppData. Nothing. You get the idea.

    I've had trouble in the past with a machine thinking it was on a metered connection, so emails wouldn't send, on another user's tablet. I expect this may be similar since it works okay outside of the company LAN.

    Machine is Windows 10 running Security Essentials (or whatever it's called now) the exact same as every other machine in the organization.

    The mapisvc.inf doesn't exist anywhere on his PC, so that's not a useful solution in this case.

    Except an interesting caveat I just found out about -- on Saturday he worked from home and forgot to connect to the VPN, and it started working. Repeatedly, it loaded fine. I asked him to try his cell phone's hotspot and other connections, but no word back yet.

    If I find a solution I'll let you guys know. Extremely frustrating.

    -J

    Monday, March 27, 2017 9:29 PM
  • Same problem here but after the 16176 Build update.
    Monday, April 17, 2017 4:58 PM
  • Also having the same error with multiple machines.

    Something of note; the dll isn't located in \OFFICE16\, it's actually located in \ClickToRun\, which is why it's throwing 0.0.0.0 for the version.

    I found a "FILE PATHS" Registry entry at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Office\16.0\Common\FilesPaths" that seems to dictate where the system thinks the files are located.  However, they are all located in \ClickToRun\, not \OFFICE16\.  Attempting to manually change the values only resulted in their being reverted back upon reboot.

    Thursday, April 20, 2017 4:38 PM
  • Not a solution but a work-around we use is to right-click the application (start menu, file explorer, desktop, etc) and pick More > Run as administrator and enter the user's password (the same user credentials it fails for when running normally). Our users run without admin privs.

    It seems to be profile related so a new user profile or running as another user allows the app to run. (Running Win 10 pro, 32-bit mode.)

    In our case, it's an in-house application that calls crystal reports to export to PDF or Excel (2016) that fails with MSO20win32client.dll at fault. We think it has something to do with permissions.

    The error starts happening after MS forces down KB4023057 and it doesn't happen for all users, and sometimes after the next update of that KP is forced down it may start working again.

    We suspect it happens if the user is logged in when the KB gets installed, and may also relate to applications being open (in particular any office app, whether the user is actively using the app or not).


    • Edited by PReinie01 Wednesday, January 23, 2019 7:24 PM add OS info
    Wednesday, January 23, 2019 7:23 PM