Windows Office error WindowsUpdate_00000537

Some users of Microsoft Office 2013 Plus are facing a curious Windows error. Windows Update reports error WindowsUpdate_00000537 and WindowsUpdate_dt000.


The error description and first diagnose

I came across this error within this thread in German Microsoft Answers forum. The user wrote:

Installing an update for Microsoft Office Plus 2013 via Windows Update, the process terminates with error: “WindowsUpdate_00000537” “WindowsUpdate_dt000”.

I also recognized this error on systems with Microsoft Office 2010 installed. My proposal, given in the above forum tread was:

  • Try to launch Windows Services manager (see this Turkish MS Answers forum post) and check, it BITS service is running.
  • The forum post here mentions other root causes like printer spooler service.
  • Check, it another Office version has been installed and (incompletely) uninstalled.  Try to repair Office using control panel “Remove programs” page.

Beside the hints above, I haven’t found too much other information about this error. This Technet forum thread discusses the error, but without a solution.

Windows or Office damaged?

Within the German forum thread I received the feedback, that an install file (.cab) has been reported as damaged. Another search brought me to this Symantec web site, where the error codes has been documented. Error 0x00000537 stands for “The sub-authority part of a security ID is invalid for this particular use.” – indicates a broken security ID.

A French MS Answers forum thead proposes a Windows repair. You can try first the checks discussed within my blog post Check and repair Windows system files and component store. If that doesn’t fix the issue, try a Windows repair via Inplace Upgrade (install Windows from a running Windows install). Maybe it helps


Similar articles:
Windows 10 Wiki
How to decode Windows errors?
Windows 10: Analyze upgrade errors
Windows: How to decode update 0x8024…. errors


This entry was posted in issue, Update, Windows and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *