After you install either the April 2016 or May 2016 updates for Microsoft Office 2016 or Office 2013, you may experience random crashes of Microsoft Skype for Business 2016, Lync 2013, Outlook 2016 or Outlook 2013. When this issue occurs, you may find an Application Error that resembles the following in the Application event log on the affected computer:
Note If you review the events in the Application event log on the affected computer, you may find any of the following crash signatures for Event ID 1000.
Note The Application version, Module version and Offset may vary.
If you have not yet scanned Lync (Skype for Business) and Outlook by using the Office Configuration Analyzer Tool (OffCAT), you can do so to help determine whether you are affected by this issue. You can download and install OffCAT from the Microsoft Download Center:
To fix this issue, follow the steps for your Office version and installation type. See the 'More Information' section to determine whether your Office installation is Click-to-Run or MSI-based.
To fix this issue, install the June 7, 2016, update for Outlook 2016. For information about this update, click the following article number to view the article in the Microsoft Knowledge Base:
3115147 June 7, 2016, update for Outlook 2016 (KB3115147)
Click-to-Run based Installations:
To fix this issue, make sure that your Office 2013 Click-to-Run installation is at version 15.0.4815.1002 or a later version. If it is not at this version or a later version, update your Office 2013 installation. To do this, follow these steps.
Open any Office application, such as Outlook or Word.
Click File, and then click Office Account or Account.
View the Version that is listed under Office Updates.
If the version is not at 15.0.4815.1002 or a later version, click Update Options, and then click Update Now.
Note If you had previously disabled updates, click Enable updates after you click Update Options, and then click Update Now.
To fix this issue, install the May 3, 2016, update for Outlook 2013. For information about this update, click the following article number to view the article in the Microsoft Knowledge Base:
3115031 May 3, 2016, update for Outlook 2013 (KB3115031)
Note If you had previously followed the workaround to disable MSOAuth, remove the MsoAuthDisabled registry data after you have installed the this update to resolve this issue.
If you are running Office 2016, you can work around the issue by following the steps in method 1. If you can't install the appropriate update that's mentioned in the 'Resolution' section for Office 2013 to fix this issue, you can work around the issue by using one of the following methods:
Method 1: Uninstall the relevant update(s)
Follow the steps to uninstall the relevant updates based on your Office installation type and version. See the 'More Information' section to determine whether your Office installation is Click-to-Run or MSI-based.
Uninstall the April 5, 2016, and May 3, 2016 updates for Outlook 2016 and Office 2016 by following the steps in the 'How to uninstall this update' section of the following articles:
3115101 May 3, 2016, update for Outlook 2016 (KB3115101)
3115096 May 3, 2016, update for Office 2016 (KB3115096)
3114972 April 5, 2016, update for Outlook 2016 (KB3114972)
3114970 April 5, 2016, update for Office 2016 (KB3114970)
Uninstall the April 5, 2016, update for Outlook 2013 and the April 5, 2016, update for Office 2013 by following the steps in the 'How to uninstall this update' section of the following articles:
3114941 April 5, 2016, update for Office Outlook (KB3114941)
3114928 April 5, 2016, update for Office 2013 (KB3114928)
Click-to-Run based Installations:
Revert to the March 2016 version of Office 2016 by following the steps in the following article in the Microsoft Knowledge Base:
2770432 How to revert to an earlier version of Office 2013 or Office 2016 Click-to-Run
For more information about Click-to-Run based installations of Office 2016, see the following article:
Disable MSOAuth in Outlook 2013 by following these steps:
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 select the following key in the registry.
After you select the key that was specified in step 3, click the Edit menu, point to New, then select DWORD Value.
Type MsoAuthDisabled, and then press Enter.
Right-click MsoAuthDisabled, and then click Modify.
In the Value data box, type 1, and then click OK.
Exit Registry Editor.
This method is only applicable to Outlook 2013. You cannot use the MsoAuthDisabled registry data for Outlook 2016.
After you disable MSOAuth, you may be prompted for credentials when you start Outlook or Skype for Business.
Remove the MsoAuthDisabled registry data after you have installed the appropriate update in the Resolution section to resolve this issue.
You can follow these steps to review the Application event log:
In Control Panel, open Administrative Tools.
Double-click Event Viewer.
In the left pane, select Application under Windows Logs.
In the Actions pane, click Filter Current Log.
In the Filter Current Log dialog box, enter 1000 (as shown in the following figure) and then click OK.
To determine whether your Office installation is Click-to-Run or MSI-based, follow these steps:
Start an Office application, such as Outlook or Word.
On the File menu, click Office Account or Account.
For Office Click-to-Run installations, an Update Options item is displayed. For MSI-based installations, the Update Options item is not displayed.