Manually Check Windows Updates and Verify They Installed

You can check for Windows updates now and confirm they installed by opening Windows Update in Settings, running a manual scan, installing any found updates, restarting if prompted, and then verifying the OS build and installed KB entries or logs. Below are a short preparation checklist, exact GUI and command-line steps you can run immediately, how to read status messages, how to confirm installs, and practical fixes and rollback options. This guide targets modern Windows desktops and laptops (Windows 10/11 and common Server builds). Managed devices may behave differently; I call out those differences where they matter.

Quick checklist: what to prepare and what you’ll see

• Have an account with administrative rights or an IT-approved exception that lets you install updates.

• Confirm a reliable internet connection. If you suspect network restrictions, try another network such as a personal hotspot.

• Free disk space: allow a few GB for cumulative updates; feature updates need much more. Clear or move files if space is low.

• Save work and close apps; many updates require a restart.

• Optional: a recent backup, system image, or at least create a system restore point before major changes.

• If the PC is managed, check whether update settings are locked by Group Policy or MDM before forcing changes.

Expected final result: the Windows Update screen shows the system is up to date or lists the latest feature update; Update history lists installed KB numbers and dates; winver shows the expected build or feature number for any feature update you installed. If you inspect logs, WindowsUpdate.log, CBS.log, and Windows Update events in Event Viewer will show successful install entries when an install completed.

Step-by-step: GUI method to check, download, install, and confirm

Open Windows Update in Settings and follow the prompts to scan, download, install, and confirm. The steps below show the common paths and checks.

1. Open Windows Update.

Start → Settings → Windows Update

2. If Settings is unavailable or locked, use Control Panel on some Server or OEM builds.

Control Panel → System and Security → Windows Update

3. Click Check for updates.

4. If updates are found, click Download or Install and watch the status lines: Downloading, Installing, or Restart required.

5. If the page asks for a restart, choose Restart now or schedule one. A pending restart blocks completion of subsequent updates.

6. After restart, open Windows Update → Update history to review installed items and KB numbers.

7. Confirm the OS build and version.

Press Windows Key + R, type winver, press Enter

8. Pause or defer updates temporarily using Pause updates or Advanced options in Windows Update. Use deferral only when you understand the policy effects or follow IT guidance.

9. To uninstall a problematic update:

Settings → Windows Update → Update history → Uninstall updates

For a major feature update, use Settings → System → Recovery → Go back if that option is still available.

Step-by-step: CLI method (PowerShell and Command Prompt)

Use an elevated shell to scan, install, or list updates. The commands below are the usual choices; availability can vary by Windows release.

1. Open PowerShell or Windows Terminal as Administrator.

2. Optional: install the community PSWindowsUpdate module once if you plan to use it.

Install-Module -Name PSWindowsUpdate -Force -Scope AllUsers
Get-Module -ListAvailable PSWindowsUpdate

3. List and install updates with PSWindowsUpdate.

Get-WindowsUpdate
Install-WindowsUpdate -AcceptAll -AutoReboot

4. Alternate built-in client triggers (behavior varies by release).

wuauclt /detectnow
wuauclt /reportnow

UsoClient StartScan
UsoClient StartDownload
UsoClient StartInstall
UsoClient RestartDevice

5. List installed updates.

Get-HotFix

wmic qfe list brief /format:table

6. Check the OS build from the command line.

[System.Environment]::OSVersion.Version
winver

7. Check and restart the Windows Update service when needed.

Get-Service wuauserv
Stop-Service wuauserv -Force
Start-Service wuauserv

How to interpret update status messages and common statuses

Short answer: the status lines tell you whether Windows found updates, is downloading or installing them, needs a restart, or failed. Use the logs for details when statuses seem stuck.

• Up to date or You're up to date: Windows checked and no new updates were installed. This can follow a recently completed install.

• Checking for updates: a scan is in progress.

• Downloading: the update is being retrieved; large feature updates can take much longer.

• Installing: files are being applied; this can include background phases and then a required restart.

• Restart required or Pending restart: installation reached a step that needs a reboot to finish.

• Failed to install (with an error code): the update did not complete. Error codes appear in Update history or Event Viewer; check logs to find the failure point.

• Some settings are managed by your organization: Group Policy or MDM controls update options; you cannot override this without authorization.

When a status looks stuck, check Event Viewer → Applications and Services Logs → Microsoft → Windows → WindowsUpdateClient → Operational and WindowsUpdate.log for more detail.

How to confirm installation and where to read logs

Quick answer: use Update history, Get-HotFix or wmic qfe to confirm KBs, winver for build changes, and read WindowsUpdate.log, CBS.log, and Event Viewer for step-by-step results.

1. Quick verification checks:

• Windows Update → Update history shows installed items and KB numbers.

• Run winver to read the OS edition and build number.

• Get-HotFix or wmic qfe lists installed KB entries.

2. Create a readable Windows Update log from Event Tracing (run as Administrator).

Get-WindowsUpdateLog -LogPath C:\Users\Public\Desktop\WindowsUpdate.log

This puts WindowsUpdate.log on the Desktop; search it for Installation Successful, SUCCEEDED, or the KB number.

3. Other logs to check:

• C:\Windows\Logs\CBS\CBS.log (Component-Based Servicing).

• Event Viewer → Applications and Services Logs → Microsoft → Windows → WindowsUpdateClient → Operational.

4. What each source proves:

• Update history and Get-HotFix show the system recorded an update as installed.

• winver shows a build change for feature updates.

• WindowsUpdate.log, CBS.log, and Event Viewer show detailed steps and error codes. If both Update history and logs show success, the install completed.

5. Distinguishing update types:

• Cumulative updates appear as KB entries under Quality Updates and usually do not change the major build number.

• Feature updates show as named upgrades and change the OS build shown by winver.

Common failure reasons and practical fixes

Short answer: failures usually come from network, low disk space, pending restarts, service problems, or policy blocks. Fix the root cause, retry, and use targeted rollback options when needed.

1. Common failures and immediate actions:

• Download stuck: check network connectivity, disable metered connection if set, or try a different network.

• Pending restart blocking further installs: save work and restart the device.

• Install failed with no clear reason: free disk space and retry. If retries fail, clear the update cache by stopping Windows Update, renaming SoftwareDistribution, and restarting the service.

Stop-Service wuauserv -Force
Rename-Item -Path C:\Windows\SoftwareDistribution -NewName SoftwareDistribution.old
Start-Service wuauserv

• Services misbehaving: restart Windows Update and BITS.

Stop-Service wuauserv -Force
Stop-Service bits -Force
Start-Service bits
Start-Service wuauserv

2. Policy or managed-device blocks: if Settings shows "Some settings are managed by your organization," Group Policy or MDM may restrict updates. Contact your IT team; do not bypass corporate controls without authorization.

3. Retry strategies: after fixing space, network, or service issues, run Settings → Windows Update → Check for updates, or rerun your CLI scan and download commands. If a specific update repeatedly fails, download its KB package from the Microsoft Update Catalog and install it with wusa.exe. Confirm the package matches your OS build and architecture before installing.

4. Rolling back updates safely:

• For quality or driver updates: Settings → Windows Update → Update history → Uninstall updates.

• For a feature update: Settings → System → Recovery → Go back (available only within the rollback window). If Go back isn’t present, restore from a system image or use System Restore if you have an appropriate restore point.

5. Use System Restore or a clean boot when appropriate:

• Use System Restore if you have a restore point from before the update and the system is unstable.

• Try a clean boot (disable non-Microsoft startup items and services) if third-party software interferes; then retry the update.

6. When to contact IT or Microsoft support: if the PC is managed, update options are blocked by policy, critical company apps fail after an update, or you see repeated error codes you cannot resolve. Provide Event Viewer entries, WindowsUpdate.log, and KB numbers when asking for help.

How to pause, defer, retry, or roll back an update safely

Short answer: use the pause and Advanced options for temporary holds, retry after fixing the cause, force-install a downloaded KB with wusa, and rollback from Update history or Recovery when needed.

1. Pause updates temporarily.

• Settings → Windows Update → Pause updates and choose the pause period.

2. Defer feature updates (if your edition allows it).

• Settings → Windows Update → Advanced options → Choose when updates are installed.

3. Retry an update after fixing the root cause: run Settings → Windows Update → Check for updates, or rerun your CLI scan and download commands.

4. Force-install a specific KB you downloaded (run as Administrator).

wusa C:\path\to\update.msu /quiet /norestart

5. Roll back a problematic update:

• Quality/driver: Settings → Windows Update → Update history → Uninstall updates.

• Feature update: Settings → System → Recovery → Go back (if present). If not, restore from a backup or system image.

How to check for optional driver and feature updates; cumulative vs feature updates

Short answer: use Windows Update → Optional updates for drivers, and Windows Update for feature updates. Cumulative updates show as KBs; feature updates show as named upgrades and change the build.

1. Optional and driver updates:

• Settings → Windows Update → Optional updates. Expand categories and install selected items.

2. Feature updates:

• Settings → Windows Update will show a feature update when Microsoft or your organization makes it available. Feature updates are larger and change the build number shown by winver.

3. Cumulative vs feature updates:

• Cumulative updates appear as KB numbers under Quality Updates and usually do not change the major build number.

• Feature updates appear as named upgrades and change the OS build visible in winver.

4. If you need a driver not listed in Optional updates, check the device vendor’s support site or the Microsoft Update Catalog and verify compatibility with your OS build before installing.