How to Trigger a Manual Scan With UsoClient on Windows 11

Windows Update on Windows 11 normally runs on its own schedule. Sometimes you need to check for updates immediately, but the Settings app or the Get Updates button does not respond or is stuck. The UsoClient command-line tool lets you force a manual scan, download, install, or restart sequence from the Command Prompt or PowerShell. This article explains what UsoClient is, how to run it, and what each parameter does so you can take control of Windows Update when the graphical interface fails.

What Is UsoClient and Why Use It

UsoClient.exe is a built-in Windows 11 executable located in the System32 folder. It communicates directly with the Windows Update service, bypassing the graphical interface in Settings. When the Settings app freezes, shows an error, or refuses to check for updates, UsoClient provides a reliable alternative. The tool accepts several command-line parameters that map to specific update actions: scan, download, install, restart, and refresh settings. No additional software or administrative rights beyond a standard administrator account are required. You run the command from an elevated Command Prompt or PowerShell window.

Steps to Run a Manual Scan With UsoClient

1. Open Command Prompt as Administrator
   Press the Windows key, type cmd, right-click Command Prompt in the search results, and select Run as administrator. Click Yes in the User Account Control prompt. Alternatively, right-click the Start button and select Windows Terminal (Admin).
2. Start a manual update scan
   In the Command Prompt window, type the following command and press Enter:
   UsoClient StartScan
   This command tells the Windows Update service to contact Microsoft’s servers and check for available updates. You will see no on-screen progress bar. The scan runs in the background. Wait 60 to 90 seconds before proceeding to the next step.
3. Download any found updates
   After the scan completes, run:
   UsoClient StartDownload
   This command downloads all updates that were discovered during the scan. Depending on your internet speed and the size of the updates, this may take several minutes. You can check download progress by opening Settings > Windows Update and looking at the status bar.
4. Install the downloaded updates
   Once the download finishes, run:
   UsoClient StartInstall
   This command installs all downloaded updates. Some updates may require a restart to complete. If you are prompted to restart, proceed to the next step.
5. Restart the device if needed
   Run:
   UsoClient RestartDevice
   This command triggers a full system restart. Save your work before running it. After the restart, Windows will finish applying any pending updates.

Additional UsoClient Commands and Their Uses

Refresh Windows Update settings

If Windows Update is misconfigured or Group Policy changes are not taking effect, run:
UsoClient RefreshSettings
This command reloads the update configuration from the registry and Group Policy without requiring a reboot. It is useful after modifying update-related policies or if the Settings page shows incorrect information.

Scan for updates silently

To perform a scan without triggering any download or install, use UsoClient StartScan alone. This is helpful when you only want to check whether updates are available without committing to a download. You can then decide later whether to proceed with StartDownload.

Combine commands in a single session

You can run all three commands in sequence without closing the Command Prompt window. After StartScan finishes, immediately run StartDownload, then StartInstall. This method automates the full update cycle from a single command prompt session.

Common Issues When Using UsoClient

UsoClient is not recognized as an internal or external command

This error occurs when the Command Prompt is not running as administrator. Close the Command Prompt window, reopen it with administrator privileges, and retry the command. If the problem persists, verify that the file C:\Windows\System32\UsoClient.exe exists. If it is missing, run the System File Checker tool: open an elevated Command Prompt and type sfc /scannow.

Scan runs but no updates are found

If UsoClient StartScan completes but Windows Update shows no available updates, the issue may be with your internet connection, the Windows Update service, or Microsoft’s servers. Check that the Windows Update service is running. Press Win + R, type services.msc, and press Enter. Locate Windows Update in the list. Its status should be Running. If it is stopped, right-click it and select Start. Then rerun the scan.

Updates fail to download or install

Corrupt update cache files can cause download or install failures. To clear the cache, stop the Windows Update service, delete the contents of C:\Windows\SoftwareDistribution, and restart the service. Run these commands in an elevated Command Prompt:
net stop wuauserv
net stop bits
del /f /s /q %windir%\SoftwareDistribution\
net start wuauserv
net start bits
After clearing the cache, run UsoClient StartScan again.

RestartDevice command does not restart the PC

If UsoClient RestartDevice does nothing, the Windows Update service may be in a bad state. Restart the service manually from the Services console, then try the command again. If the command still fails, use the standard restart method: click Start, click the Power icon, and select Restart.

Item	UsoClient	Settings App
Interface	Command line	Graphical
Requires admin rights	Yes	No
Bypasses UI errors	Yes	No
Controls individual phases	Scan, download, install, restart separately	Combined Check for updates button
Shows progress	No on-screen feedback	Progress bar and status text

You now know how to trigger a manual scan using UsoClient on Windows 11. The tool gives you granular control over each phase of the update process and works when the Settings app fails. For advanced troubleshooting, combine UsoClient commands with the Windows Update Troubleshooter available in Settings > System > Troubleshoot > Other troubleshooters. The RefreshSettings parameter is especially useful after applying Group Policy changes because it applies them immediately without a reboot.