Check Windows Update pending reboot indicators
Inspect recent installed updates, common reboot indicators and Windows Update related service state without starting an update scan, installing anything or resetting update components.
Run the Windows Update diagnostic
pwsh -NoProfile -File .\Invoke-WindowsDiagnostics.ps1 `
-Updates -PrivacyMode -ExportMarkdownFor optional recent update-related Event Log entries, run the standalone module:
pwsh -NoProfile -File .\scripts\windows-update-check.ps1 `
-IncludeEventLog -SinceDays 14 -MaxEvents 20When this guide is useful
- Windows Update says a restart is required but the reason is unclear.
- An application installer, driver or management tool reports a pending reboot.
- Updates appear installed but Windows Update remains in an unusual state.
- A support request needs recent update history and related service context.
What the update report checks
Windows version and build
The operating-system version and build provide context for update history and support discussions.
Recently installed updates
Recent update records exposed by built-in Windows read-only sources.
Pending reboot indicators
Common registry-backed indicators used by Windows components and servicing processes to signal that a restart may be required.
Update-related services
Current state and start mode for relevant Windows Update and servicing services without starting or stopping them.
Optional Event Log evidence
Recent Windows Update related warnings and errors when the standalone option is requested.
Findings summary
Unavailable sources, reboot indicators and other notable state are summarized before the detailed output.
How to interpret pending reboot indicators
A reboot indicator is evidence, not a complete diagnosis
Different Windows components can leave separate indicators. One indicator may remain after the operation that created it, while another may appear only during a specific servicing stage.
Compare the indicator with update timing
Recent installed updates, installer activity and Event Log timestamps help determine whether the reboot state is current and relevant to the reported problem.
Service state depends on trigger-start behavior
Some Windows Update services do not run continuously. A stopped service is not automatically a fault; start mode, recent events and the observed update behavior matter.
Do not infer that all updates are current
The diagnostic reads local history and state. It does not contact Microsoft Update or prove that no newer update is available.
What the toolkit does not do
- It does not decide whether restarting is safe at the current moment.
- It does not verify update availability against an online catalog.
- It does not repair Windows Update components.
- It does not replace organization-specific update-management tools.
Reasonable next steps
- Record the pending reboot indicators and the most recent update timestamps.
- Check whether important work, encryption operations or managed maintenance policies affect restart timing.
- Review optional update events when the local state appears inconsistent.
- Follow the approved restart or servicing procedure for the machine.