Office Applications crash or cannot start
This article only addresses the crash scenario where mso30win32client.dll is the module name in a crash signature.
For other scenarios, see the following articles:
- Excel not responding, hangs, freezes, or stops working
- PowerPoint isn't responding, hangs, or freezes
- I get a "stopped working" error when I start Office applications on my PC
- Help protect your files in case of a crash
If you still couldn't find a solution with Office Applications crashing or not starting, you might check the Microsoft Community Office Commercial Admin Center Forums.
Microsoft Office 2016 applications may crash or cannot start. The applications that have been seen to be affected are Excel, Outlook, Skype for Business, Word, Access, Publisher, Project and OneNote.
Additionally, in the Application Event log, you may find a crash signature similar to the following in event ID 1000:
Application Name: <application>.exe Application Version:16.0.4266.1001 Module Name: mso30win32client.dll Module Version: 16.0.4266.1001 Offset: <varies>
- The Application Name will be the name of the executable of the application, such as excel.exe, outlook.exe, lync.exe, winword.exe, msaccess.exe, mspub.exe, winproj.exe, or onenote.exe.
- The Application Version, Module Version and Offset will vary.
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
To work around this issue, follow these steps:
Exit all Office 2016 applications.
Start Registry Editor. To do this, use one of the following procedures, as appropriate for your version of Windows.
- Windows 10, Windows 8.1 and Windows 8:Press Windows Key + R to open a Run dialog box. Type regedit.exe and then press OK.
- Windows 7: Click Start, type regedit.exe in the search box, and then press Enter.
Locate and then select the following registry key:
Locate the ShownFirstRunOptin registry value in the key that is specified in step 3. If you do not find ShownFirstRunOptin, go to step 5. If you do find it, go to step 7.
If you do not find the ShownFirstRunOptin registry value, point to New on the Edit menu, and then click DWORD (32-bit) Value.
Type ShownFirstRunOptin, and then press ENTER.
Right-click ShownFirstRunOptin, and then click Modify.
In the Value data box, type 1, and then click OK.
On the File menu, click Exit to exit Registry Editor.