UsoClient.exe
Also called usoclient, update session orchestrator, uso client
Update Session Orchestrator client. Scheduled tasks call it to scan, download, or install through the Windows Update stack.
What you need to know
This is the Update Orchestrator command line, not a third-party updater.
UsoClient.exe is how scheduled tasks talk to the Update Session Orchestrator. Commands like StartScan come from Microsoft tasks. It is not Chrome's updater.
- Safe?
- Yes, in System32
- Why did it start?
- A scheduled Update task
- Should I delete it?
- No
What is UsoClient.exe?
UsoClient.exe is the client executable for the Update Session Orchestrator. Task Scheduler launches it with verbs such as StartScan, StartDownload, and RestartDevice.
What does it do?
It signals UsoSvc. It is not the service that holds the download, and it is not TiWorker applying the package. The process often exits after the command is handed off.
Why is it running?
A Microsoft scheduled task ran, or you clicked Check for updates. A forever-running UsoClient with a weird command line is the case to inspect.
Is it safe?
Usually safe
The legitimate client is in System32 and signed by Microsoft. An UsoClient.exe in AppData is not the orchestrator client.
A legitimate copy normally runs from:
C:\Windows\System32\UsoClient.exe
- Expected publisher: Microsoft Corporation
- Started by Update Orchestrator tasks
- Related service: UsoSvc
Can I end it?
Usually unnecessary
Ending a short-lived UsoClient does not stop Windows Update. If you need to pause updates, use Settings, not Task Manager.
Can I remove it?
No
Do not delete UsoClient.exe. Scheduled update tasks will fail open or error in Task Scheduler.
Should it start with Windows?
Task Scheduler starts it. Disabling those Microsoft tasks is a policy decision, not a Startup Apps cleanup.
Normal resource behavior
These are contextual labels, not universal averages.
- CPU
- Short spike when a verb runs
- Memory
- Small
- Disk
- Low. Downloads belong to the Update stack
- Network
- Low here
File information
| Executable name | UsoClient.exe |
|---|---|
| Common legitimate path | C:\Windows\System32\UsoClient.exe |
| Publisher | Microsoft Corporation |
| Signature expectation | Signed by Microsoft Windows |
Common problems
Command window flash
Some tasks run UsoClient and close. That flash is the orchestrator, not a hidden Command Prompt virus by itself.
People disable every Uso task
That blocks quality updates. Use Pause updates if you need time, then turn them back on.
Troubleshooting
Diagnose before you change anything destructive.
Read the task name in Task Scheduler
Look under Microsoft / Windows / UpdateOrchestrator. The action line should point at System32\UsoClient.exe.
Do not replace the file from a forum zip
The client is a signed system binary.
Technical details
Technical details
| Image name | UsoClient.exe |
|---|---|
| Related service | UsoSvc |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Microsoft Learn: Update Session Orchestrator · How Windows Update orchestration works
- Microsoft Support: Windows · Public support naming
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.