Windows 10: Update Orchestrator Service (USOsvc) affecting auto SLEEP mode function

Greetings All,


Just recently, I noticed that my PC was had stopped going to sleep automatically. It was working fine for several days, just after I performed a clean install of v1909, and KB4524570 Cumulative Update. I found the culprit by running the PowerShell command: powercfg -requests.

The reflected result was that the USOsvc was demanding power. So I went into Windows "SERVICES", and STOPPED the USOsvc service.

Then I placed it into "MANUAL" startup mode. I restarted the PC and VOILA, sleep mode was working again.


I guess at this point, my question is, what price am I going to have to pay for this modification down the road?

So, I ran a little test, since this has all to do with Windows Updates, I went into Windows update settings area and requested an update search. This action immediately restarted the USOsvc, but was now, not reflected in the powercfg -requests results. It also remained in "MANUAL" mode in "SERVICES".


Would anyone know of any workarounds, other than the method(s) that I used, as explained above.

Your comments and suggestions are welcomed.


The best,

indyiceman




:)

 

Windows 10 Update Orchestrator Service

found similar error in the 'System' log, during the restart after installing the update, is this normal for windows 10? Does everyone faced such thing? The update seems to have settled, in the status I've see 'Success', there seem to be no other errors.

The "Update Orchestrator Service" service is turned off due to an error
The return from the operation was due to the timeout.

code 7023 source of Service Control Manager

EventData

param1 Update Orchestrator Service
param2 %% 2147549471
550073006F005300760063000000

Keywords 0x8080000000000000

after 20 seconds
The C: \ Windows \ system32 \ MusNotificationUX.exe process initiated the "Restart" action for the DESKTOP computer on behalf of the user due to: Operating system: Service pack installation Scheduled

The update was installed
KB4103727 OS Build 16299.431

Thanks.

 

Windows 10 Update Orchestrator Service

That desktop PC, and with windows 10 1709 Enterprise on it, nothing serious have been tweaked about updates (some tweaks to not install updates automatically in Group Policy) , no Network Domain/AD used. So this is normal? As far I know that Update orchestrator does not used in common editions.

 

Can't Access Windows 10 Update Orchestrator Service

I'm on build 1803 of Windows 10 Home. I need to disable Update Orchestrator Service aka. UsoSvc because I am running several scientific analysis programs (Biochemistry) that are required for work but may be broken with future Windows updates. I need complete control over when and how I update in order to ensure each patch is compatible.

I find that even using an elevated administrator account (activated through the command line) and running command line through the "Run As: Admin" with sc config UsoSvc start= disabled. I am denied access to the service through system error 5. Accessing through the Services manager shows a grayed out box where start-up properties are. See this screenshot:





The computer is not on a domain, it's my home system. Is there any way to either a) access the UsoSvc and change access the start-up property to disabled and eliminate the scheduled tasks, or b) access my computer with the LocalSystem account? Upon boot there is no option to click "other users..." at the start up screen to type in the computer name\localsystem.

I am looking for a way that does not include permanent deletion of the service. I have already disabled start-up of wuauserv and the trustedinstaller. Can anyone help?