Read the Windows Update log when an update keeps failing — via Microsoft Learn

Commandlow riskNeeds adminWindows 11Windows 10

Windows Update no longer writes a readable log; it writes trace (.etl) files. One PowerShell command converts them into a WindowsUpdate.log on your desktop so you can search for the error code.

Takes effect right away

Command

Run in an administrator PowerShell / Terminal window.

Get-WindowsUpdateLog

Undo

Remove-Item "$env:USERPROFILE\Desktop\WindowsUpdate.log"

The file is a snapshot — run the command again to refresh it. For installation-stage failures also look at %SystemRoot%\Logs\CBS\CBS.log.

Sources

Get-WindowsUpdateLog — by Microsoft Learn
Windows Update log files — by Microsoft Learn

Source reviewed: 2026-11-02
Link checked: 2026-11-02
Tested hands-on: Not by Oddbyte.Me

Oddbyte.Me hasn't tried this on every Windows build, so keep the undo handy.

windows update logupdate errortroubleshootpowershellcbs.log

More in Windows Update

Set Active Hours so updates never restart you mid-work — via Microsoft Learn

Hidden settinglow risk

Windows won't automatically restart for updates during your active hours. You can set them by hand or let Windows learn them from your activity; admins can also enforce a range by policy.

Reclaim space from old updates (WinSxS cleanup) — via Microsoft Learn

Commandmedium riskAdmin

Old versions of updated components pile up in the WinSxS folder. A DISM command removes superseded versions now instead of waiting for Windows' own scheduled cleanup. Never delete WinSxS files by hand — that can break Windows.

Delay feature updates by up to a year — via Microsoft Learn

Group Policylow riskAdminPro / Enterprise / Education

Instead of pinning a version, you can ask Windows to wait a set number of days (0–365) after a feature update is released before offering it — letting others find the bugs first. Monthly security updates keep coming.