The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to go to the article in the Microsoft Knowledge Base:

Resolution. If all affected C++ binaries that are built by using Visual C++ 2013 use the C Runtime DLL (msvcr120.dll), install the updated Microsoft Visual C++ 2013 Redistributable – 12.0.40660.0 or a later version.

The Windows Error Reporting tool, Dw20.exe, collects information automatically whenever an Office program stops responding. With this tool, you can send a report directly to Microsoft. Microsoft uses the data to address problems and enhance future program versions .

Fixes an issue that occurs when Windows Explorer is hosting a shell extension that was created by using Microsoft Foundation Class (MFC) and the Explorer.exe process stops responding (hangs).

You might see Error 0xC0000142 when you start an Office application. To help you resolve this, try the solutions below. We’ve listed the most common solutions first so try the steps in the order they're listed.

Fixes an issue in which the ISServerExec.exe process crashes, and the SSIS package execution fails intermittently when you execute an SSIS 2012 or SSIS 2014 package.

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. Describes an issue where Lync (Skype for Business) or Outlook crash. Provides a resolution.

To open File Explorer in Windows 11, select File Explorer on the taskbar or press the Windows logo key + E on your keyboard. Here are some things to try if File Explorer won't open. Check for updates. Restart your device. Reset your PC.

To do this, use one of the following methods. Method 1: Update the protection agents from the Data Protection Manager Administrator Console. Open the Data Protection Manager Administrator Console. Select the Management tab, and then select the Agents tab.

In Microsoft Exchange Server 2019 and Exchange Server 2016, threads of MSExchangeMapiMailboxAppPool are stuck in lock contention (clr!AwareLock::Contention), which causes the affected server to stop responding with 100% CPU usage for a long time (1+ hour).