A cumulative update fails with 0x80073712. The internet has a standard fix: run DISM, run SFC, reboot, reset SoftwareDistribution, reboot again, and finally reinstall the server. That’s a lot of work, and none of it tells you what was actually wrong.

WU-Troubleshooter skips that part. It checks things in a fixed order and stops guessing.

wire → client → errors → repair. In that order. Rebooting is not a step.

Get it on GitHub

What it does

  • The wire. DNS, TCP, TLS and proxy-aware HTTP checks against every documented Windows Update endpoint. If something on the path swaps out Microsoft’s certificate (SSL inspection), it tells you, because Windows Update will quietly refuse to work through it.
  • The client. Services, the SYSTEM proxy, update source and policy, pending reboots, disk space, clock, BITS, the datastore and recent events. Optionally a live scan.
  • The errors. Reads the modern WU logs and groups failures by HRESULT, so you see “seven times 0x80073712” instead of 4,000 lines. Known codes come with a hint about what usually fixes them, and what doesn’t.
  • The repair. Only when you ask for it. Each fix has its own switch and supports -WhatIf. A plain run changes nothing.

It understands WSUS, too. On a WSUS-managed server, “can’t reach Microsoft” is how it’s supposed to work, so it reports that as INFO, not a red FAIL.

Quick start

# everything, in order, into .\logs\WUDiag_<timestamp>\
.\Invoke-WUDiagnostics.ps1

# just the network path
.\Test-WUOnlineConnectivity.ps1

# the local client, plus a live online scan
.\Test-WULocalClient.ps1 -RunLiveScan

# recent WU errors from the last 3 days
.\Get-WUErrors.ps1 -HoursBack 72

The case that started it

A batch of servers, all deployed from the same image, failed the same CU. The toolset said Connectivity PASS, LocalClient PASS, Errors FAIL, so the network and the client were fine. The error scan put the corruption in an en-gb language pack. DISM was never going to fix that one. Removing and re-adding the language pack fixed it, and the golden image got rebuilt so new servers don’t start out broken.

The full story is in the release post.

Is it for you?

Yes, if you run Windows Server 2025 (it also works on Server 2016+, Windows 10 and 11) and you’d like a diagnosis before you start trying fixes. It needs Windows PowerShell 5.1 or PowerShell 7 and an elevated session. MIT licensed.