Recent content by StephenCWLL

Also, just read that there was a tweet from Gabriel Aul ‏admitting a bug: Gabriel Aul ‏GabeAul TheJoeFin They're installed. The Update History UX has a bug that shows a restart required for some users.

I think the updates saying they still need a restart are probably installed. If I look under uninstall in control panel they are all there ... So I think Installed Updates in Windows Update in the new settings app gives incorrect return codes which is why it says they still need a restart...

It pops up and closes instantly because it needs a command parameter. i.e. a command after it's filename is called. There seems to be several commands possible for the USOClient, which you can see in several of the scheduled tasks that call it ...

There's possibly some information in the areas I mentioned to what's causing that. In my days on Windows 7 it used to be due to wrong exit codes being returned by the updates but don't know if that's the case in Windows 10. I've got several updates like that from yesterday's group of updates...

Results of the last Windows Update attempt seem to be stored here C:\ProgramData\USOPrivate\UpdateStore as there's one xml storing data related to a failing update I get. C:\ProgramData\USOShared\Logs contains as it suggests, individual logs of USO components. Probably these might be combined...

USO stands for Update Session Orchestrator and it's the mechanism that's replaced the Windows Update Agent (i believe)

After I type that I bring up scheduled tasks and thus I realise that all those files are the settings for Orchestrator to do different windows update actions.

usoclient.exe looks to be the new windows update mechanism file. I've been doing some digging trying to understand updates in Windows 10 and I tracked down the use of this file. If you open up command prompt and type usoclient.exe StarttInstall and keep the Windows Update settings window up at...