usoclient popup

Hi, everyone!  This worked perfectly for me and the "usoclient" issue has not returned.

Microsoft Update error check fixed it, here are the steps:

1) Go to Control Panel

2) Under "System and Security" click on the last option "Find and fix problems"

3) Again under "System and Security" click on "fix problems with Windows update"

4) Click "Next" and let Windows Update find and fix the problem.

On my system, Windows Update fix notified me that it found a problem with one of the update.  It did not ask me to re-boot after it fixed the error but I rebooted anyway to see if it had fixed the 'USOCLIENT" DOS Prompt issue....it has not returned since!

Good luck and best to all!

Seems you're not the only one. Many users have complained about observing a CMD command prompt windows briefly snapping open and then closing immediately on every Windows 10 OS boot. I agree this may be a bit annoying and not the best user experience.  It seems though, that normally you should not even see the popup on screen. I assume there could be many reasons such a laptop lagging behind on startup, though I won't go too deep on that...

First, USO stands for Update Session Orchestrator and it's the mechanism which replaced the Windows Update Agent. As a part of the Windows Update service, usoclient.exe main role is basically a command to run tasks to either scan for updates, install or resume updates.

You can no longer use the old (wuauclt.exe /detectnow) commands to schedule a Windows Update scan via the command.

Windows Update settings has been moved away from the legacy Windows Control Panel to the new modern System Settings app in Windows 10.

Therefore, you won't find any reference to usoclient.exe file listed under Control Panel > Uninstall or Change Program list.

The usoclient.exe program is located in the C:/Windows/System32/ folder. Some may have claimed it was okay to delete the usoclient.exe file manually.  I personally wouldn't recommend it but rather simply let it do its job. Deleting the usoclient.exe file may cause unwanted behaviours...

If you open Task Scheduler and scroll down the scheduled tasks at Microsoft > Windows > UpdateOrchestrator, you will find options of the usoclient.exe [Command process and arguments].

If you take Schedule Scan task[to perform a scheduled Windows Update scan...], the Triggers for this task to run could be   

   -One Time [At system startup] 
   -Custom Trigger
   -On an event.

If you click on Action Panel, you'll find the usoclient.exe associated Action: Command and Argument Details

%systemroot%\System32\usoclient.exe StartScan

Last but not least, the task Status options:
  -Ready
  -Run

  -End

  -Disable

  -Export

  -Delete

So you could simply try disabling it and see what happens...

Hello,

Thank you for your input.

I hope that your suggestions may help other community members to resolve similar issues.

I appreciate it.

Thank you

not helpful, the pop-up showed again when i logged in this evening (09 September 2016) and it lasted for about 15 seconds. i don't mind if Microsoft spies on us or monitor what we do, but i get concerned when i can see it happen. please fix the issue. it should run/launch in the background 

it just popped up after a short update on a Surface Pro - my guess is that Win 10 is displaying an update command that probably should not be displayed but is not harmful. I would like to see MS confirm this.

This is not a virus !, you can find it in in task scheduler ,dont afraid ,it is checking only the system updates.

If you open Task Scheduler and check the scheduled tasks at Microsoft > Windows > UpdateOrchestrator, you will find mention of this process.

Update Session Orchestrator Client.

It's the component that orchestrates the Windows Updates.

Nothing to worry about, there are literarily hundreds of components that kick in at regular time, be it scheduled or simply initiated by the system.

I can't see why any internal operating system process would be executed as a command or batch program in a terminal window (this isn't a Unix or Linux system). So my only thoughts are that something from outside the operating system is setting this off -- so that's why I see this as a possible problem, by agents outside my system. I have run several full scans, but nothing's been found. The other possibility is that it has something to do with the system trying to contact Microsoft. A few times I have gotten alerts that there was an error in the login process with Microsoft. But when I click the alert it just brings me to the Accounts Settings window. Also this only happens rarely, while the usoclient window always happens!

Strange as it may seem/sound, Windows' origin, so called DOS, was a Xenix derivative.  The command prompt has stayed with the various versions of Windows, including Win10.  The command prompt (power shell, too) is a quick and convenient way to get at various system features.  It also is powerful, more so in many ways than Windows 10, to learn about the innards of the Win OS.  It has many unix (linux/fedora/debian/etc.) like actions mostly because the Xenix derivative of unix preceeded these other unix variations/derivatives.

So, if you are thinking Win10 is is not, think again.  Many of the large vendors use the batch/terminal features to complement the Win10 OS to get around the limitations of Win10 to do some of the heavy-loading, so to speak, that has been set aside in the windows environment because most folks are simply not interested.

I think we have established that the file is not a virus and it is part of the Windows update services.

The issue now is not that we don't know what it is, but it is a poor user experience to have a command prompt window pop up on every login.

What the community is now asking Microsoft is why they can't make this process run without having an annoying pop up on every login. I think this is a reasonable request that has not been answered yet. Imagine if there was a pop up for every background process that Windows ran. Now there may be a valid reason that Microsoft absolutely requires a command pop up for usoclient.exe, but I really doubt it.