Disable / Enable Update Orchestrator Service - Windows NEVER Task Manager Processes

Many users Windows 10 have plans excessive consumption of resources (HDD & CPU) consumed by "Update Orchestrator Service"
Before seeing how we can deactivate or escape this processor or processor load, let's see what it is and what the "Update Orchestrator Service" does.

The presence of this service in Windows NEVER Task Manager it should not worry you. There are very few chances like one virus / malware to be present in the Task Manager with this name. Update Orchestrator Service (UsoSvc) is a the basic system of the system operating Windows 10, running in the shared process svchost.exe and is dependent on Remote Procedure Call (RPC), unable to run without the latter. About svchost.exe We have talked before and I said that through it a series of services can be launched Windows. Windows Services. Update Orchestrator Service is one of these services, being run from% WinDir% \ system32 \usocore.dll.

What the Update Orchestrator Service does

As the name suggests, this service manages the updates Windows 10. Without starting this service, it will be impossible to install the latest updateof yours Windows 10. For this reason, we suggest that you never disable this service Windows 10. The period of time that this service pushes the processor (CPU) of a PC up to 100% or overload the hard disk is limited. This usually happens on the period of an update in background or when it is verified integrity an update a Windows 10

How can we deactivate / activate Update Orchestrator Service on Windows 10

Being a service of Windows 10, we'll find this one in control PanelAdministration ToolServices (or search for "services").
In the service list, we run up to "Update Orchestrator Service" and open the service options.

By default, this service starts manually, under "Local System". From the options panel, we can stop it "Stop" - it will start at the next request of Windows Update - or we can disable it altogether. We set “Startup type: Disabled"

We remind you that after you set this service to "disabled", the updates Windows 10 will no longer be able to install on your operating system. You will no longer receive any driver updates, security updates or software updates. Therefore, we recommend that you leave the manual and stop it only if you need all the system resources at one point. Allowing the process to start after the first restart.

Disable / Enable Update Orchestrator Service - Windows NEVER Task Manager Processes

About the author


Passionate about everything that means gadget and IT, I am pleased to write on stealthsettings.com from 2006 and I love to discover new things about computers and macOS, Linux operating systems, Windows, iOS and Android.


  • totally wrong, even if set to disabled, at the next reboot of the PC, this service starts automatically and switches manually ignoring the previous disabled

    • You probably have a process control manager. This has not happened in tests, and more so, it has blocked everything in the management of updates. Update Settings, Updates History and Updates.

  • After setting the service to STOP and DISABLED, select the Recovery Tab and then select “Take No Action” on the First and Second failure choices. Select Apply and OK on the way out. It won't restart again at computer restart. I also do the same (stop and disable) to Background Intelligent Transfer Service, Connected User Experiences and Telemetry Service, and Windows Update Service. I only update manually (once a month or so - sometimes once every few months or so) and these services need to be turned back on (enabled and started) to update manually.

      • stealth
        After a year with no issues with forced downloads from MS, some of my computers are now being hit with them starting about a week ago. It looks like it's GWX all over again. I am still able to maintain 1703 as I do not want to upgrade to 1709 (will wait for later versions). I am still able to defeat the forced downloads, but now you have to spend two or three times a day to prevent them from downloading by using the tips listed above and ending / disabling certain tasks in Task Scheduler and Services daily. Even with these steps, tasks WILL re-enable and services will restart daily, whether or not the computers have been shut down for the day or just put to sleep. I have 15 computers at my business all running 10 Creators and some PRO's. All of them are being hit every day now, even my PRO versions. Fortunately, my employees have been instructed to end the task in Task Manager which gives me time to do the other terminations stated above. Just takes a minute or so per computer. Sorry my tips above do not stop this intrusion permanently. Do not know what's after 10, but we can hope.

        • I'm not sure this will work 100% but I have the tasks re-enabling windows update and now hating me about being pretty far out of date, I have disabled the windows update (all of them) related tasks, and service only to find it on again as well.

          I think I have found a fix at least for now. I have edited the service name under HKLM \ System \ CurrentControlSet \ Services \ I \ 'renamed wuauserv to wuauservx and now the service is incapable of starting (at least currently), and if I can I can always name it back to get some buggy updates.

        • Aqui has been using Symantec (I install it and my tempo) for the use of this software and Internet applications. The tenth form of GWX is a porumen of the internet, and it is about usuário a programma.

  • Some of the words in this article that are supposed to be separated by spaces are squished together to make a broken English, so this article is hard to understand.

    • I'm sorry for the inconvenience. I will try to solve this problem in the future. The article is translated automatically and some elements should not have been translated.

  • I'm using Windows 10 Home 1803. By default, the startup type of this UsoSvc is Manual. When I choose Disabled and hit OK or APPLY, a warning pops up and says Access is Denied. I can stop the service but that's it. If I can't change the startup type to Disabled, this service will start again at the next reboot. Same thing happens with WaaSMedicSvc.

Leave a Comment