Home/Tools
Supporting utilityChecklistIntermediateChanges system state

Windows Update readiness and repair evidence pack

A patch readiness and repair evidence pack for reboot state, servicing health, update logs, and approved repair actions.

Good For

  • patch readiness

  • Windows Update failures

  • maintenance windows

  • server health evidence

  • repair validation

How to Use It

  1. Capture read-only service state, pending reboot signals, update history, and recent Windows Update events first.

  2. before repair commands so the starting servicing state is documented.

    Read-only command: verify target and scope

    DISM /ScanHealth

  3. Escalate into `DISM /RestoreHealth` and `sfc /scannow` only when repair work is approved and the maintenance window is clear.

  4. Record transcript output, any remaining component-store warnings, and the Windows Update retry result.

  5. Use the combined evidence pack to separate systems that merely need reboot/window follow-up from systems that need deeper repair.

Execution Modes

  • local
  • remote-single-host

Inputs and Outputs

Inputs

  • computer name
  • KB number
  • error code
  • maintenance window
  • backup or restore owner

Outputs

  • verbose-console
  • csv
  • log-file
  • operator-notes

Command Starter

Changes system state: review before running

# ---------------------------------------------------------------------
# Phase A — read-only readiness evidence
# ---------------------------------------------------------------------
Get-Service wuauserv, bits, cryptsvc, TrustedInstaller |
Select-Object Name, Status, StartType
Get-WinEvent -LogName 'Microsoft-Windows-WindowsUpdateClient/Operational' -MaxEvents 80 |
Select-Object TimeCreated, Id, LevelDisplayName, Message
DISM /Online /Cleanup-Image /ScanHealth
# ---------------------------------------------------------------------
# Phase B — approved repair actions
# These commands can change servicing and system-file state.
# ---------------------------------------------------------------------
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Validation

  • Starting service, reboot, update, and servicing state is captured.

  • Repair output completes without unresolved corruption or records the exact failure code.

  • The target update scan or install can be attempted again with new evidence.

Reporting

  • attach before and after servicing evidence to patch tickets

  • record DISM, SFC, reboot, and update scan results

  • promote repeated use into a patch readiness report

Safety Notes

  • Repair commands can change component store and protected system files.

  • Do not run repair or reboot steps outside an approved maintenance window.

  • Keep before-state logs and backup or restore notes with the ticket.

Keep Moving

Take the workflow further

Use the related Learn guide, practice the workflow in a Lab, or choose another Tool.

Primary Windows Server workflow: update failure runbookWindows Update Repair ChecksWindows Update reports troubleshooting