Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x80070422

0x80070422: the Windows Update service is disabled or refuses to start

11 min read Updated October 5, 2026 Windows Update & Setup

Fix it now

0x80070422 is ERROR_SERVICE_DISABLED, decimal 1058: the service cannot be started because it is disabled, or because it has no enabled devices associated with it. It is one of the few update errors that means exactly what it says. Nothing is corrupt and no files are missing.

Run these in an elevated Command Prompt. Note the space after each equals sign; without it the command fails

sc.exe query wuauserv
sc.exe config wuauserv start= demand
net start wuauserv
sc.exe config bits start= delayed-auto
net start bits
  1. Open Services and check the startup type for Windows Update. Disabled is what produces this code. Manual and Automatic both allow the service to start, and a stopped service with a Manual startup type is normal, not broken.
  2. Confirm Cryptographic Services is running. Microsoft says reconfiguring it is not recommended and that anything depending on it fails to start if it is disabled.
  3. If the startup type dropdown is greyed out, a policy or a third-party blocker is holding it. Run gpresult /h report.html and read which policy applies and where it comes from.
  4. Run the Windows Update troubleshooter: on Windows 11 that is Start – Settings – System – Troubleshoot – Other troubleshooters, and on Windows 10 Start – Settings – Update and Security – Troubleshoot – Additional troubleshooters.

If your changes keep reverting, look for the policy or the utility putting them back rather than fighting the symptom. Windows also includes a protected repair mechanism that undoes tampering with update components, and it is not something to reconfigure.

If a scan starts and updates install, you are finished. If the service starts and then fails, the next section covers the other four codes and what each of them changes.

Why it happens

Windows Update is not meant to be running all the time. It is trigger-started: the service control manager brings it up when something needs it and stops it again afterwards, which is why a stopped service is a normal state rather than a fault. Disabled is different. That setting tells the service control manager never to start it under any circumstances, and it produces 0x80070422 the moment anything asks.

Most machines that arrive in this state were put there on purpose. Utilities that promise to stop Windows updating set the service to Disabled and often add a policy for good measure. Debloating and privacy scripts do the same. So do administrators who wanted a machine to stop restarting during a project and never turned it back on. Occasionally a security product blocks it as part of a lockdown template.

The other codes in this family are all service control manager errors, and each names a different reason a start request failed. 0x8007043C is ERROR_NOT_SAFEBOOT_SERVICE, decimal 1084: this service cannot be started in Safe Mode. That one is by design and there is nothing to fix. 0x80070433 is ERROR_SERVICE_DEPENDENCY_DELETED, decimal 1075: the dependency service does not exist or has been marked for deletion, which is a genuine missing component rather than a configuration choice.

0x8007041D and 0x8007042A are the ones people misread. 0x8007041D is ERROR_SERVICE_REQUEST_TIMEOUT, decimal 1053, meaning the service did not respond to the start or control request in a timely fashion, so the service control manager gave up waiting. 0x8007042A is ERROR_SERVICE_SPECIFIC_ERROR, decimal 1066: the service started far enough to return a failure code of its own. That distinction matters, because with 1066 the useful detail is in the service’s own event, not the service control manager’s.

The service is set to Disabled

You have this one if The startup type for Windows Update reads Disabled in the services console.

  1. Change the startup type to Manual, apply, and start it.
  2. From an elevated Command Prompt the equivalent is sc.exe config wuauserv start= demand followed by net start wuauserv.
  3. Do the same for Background Intelligent Transfer Service, which Microsoft documents as being what Windows Update depends on to download in the background.
  4. Check for updates and confirm a scan actually begins.

sc.exe config requires a space between the option and its value. start=demand fails; start= demand works.

The machine is running in Safe Mode

You have this one if 0x8007043C, and the desktop shows the Safe Mode markings.

  1. Restart into a normal Windows session. Windows Update is deliberately not available in Safe Mode.
  2. If the machine keeps booting into Safe Mode, run msconfig, open the Boot tab and clear the Safe boot option.
  3. Retry the update once you are in a normal session.
  4. Do not try to force the service to start in Safe Mode. This is not a fault to work around.

Group Policy is blocking updates

You have this one if Settings shows a note that some settings are managed by your organisation, and the service startup type cannot be changed.

  1. Run gpresult /h report.html and open the report to see which policy applies and where it comes from.
  2. On a domain member, ask the owner of that policy to change it. A local change will be overwritten at the next refresh.
  3. On a standalone machine, review the Windows Update settings under Computer Configuration – Administrative Templates – Windows Components in the Local Group Policy Editor.
  4. Run gpupdate /force, then check for updates again.

A dependency does not exist any more

You have this one if 0x80070433, and the Dependencies tab of the service lists something that is not installed.

  1. Open the service’s properties and read the Dependencies tab to identify what is missing.
  2. Confirm whether that service exists at all in the services console.
  3. Restart first. A service marked for deletion is removed at restart and can often be reinstalled afterwards.
  4. If it is genuinely gone, repair the system with DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow.

The service starts and then fails or times out

You have this one if 0x8007041D or 0x8007042A rather than 0x80070422: the code changes from disabled to a timeout or a service-specific failure.

  1. For 0x8007042A, read the service’s own event rather than the service control manager’s. The code exists to say the failure detail is elsewhere.
  2. Check Event Viewer under Windows Logs – System, filtered on Service Control Manager, for the exact failure.
  3. Reset the update cache: stop the update services, rename SoftwareDistribution and catroot2, then start them again.
  4. Repair system files with DISM and sfc if the failure persists, and restart before retrying a scan.

Full reference

The five codes and what each one asserts

Code Decimal Published name and meaning
0x80070422 1058 ERROR_SERVICE_DISABLED: the service cannot be started, either because it is disabled or because it has no enabled devices associated with it
0x8007043C 1084 ERROR_NOT_SAFEBOOT_SERVICE: this service cannot be started in Safe Mode
0x8007041D 1053 ERROR_SERVICE_REQUEST_TIMEOUT: the service did not respond to the start or control request in a timely fashion
0x8007042A 1066 ERROR_SERVICE_SPECIFIC_ERROR: the service has returned a service-specific error code
0x80070433 1075 ERROR_SERVICE_DEPENDENCY_DELETED: the dependency service does not exist or has been marked for deletion

Setting startup types from the command line

Value for start= What it means
boot A device driver loaded by the boot loader
system A device driver started during kernel initialisation
auto The service starts automatically each time the computer restarts
demand The service must be started manually. This is the default if start= is not specified
disabled The service cannot be started. This is the state that produces 0x80070422
delayed-auto The service starts automatically after other automatic services have started
sc.exe query wuauserv
sc.exe config wuauserv start= demand
sc.exe config bits start= delayed-auto
sc.exe config cryptsvc start= auto
net start wuauserv

Editing service Start values directly in the registry can leave the machine unbootable if you change the wrong key. Export the branch first, and prefer the services console or sc.exe config, which validate what you give them.

The services this depends on

Windows Update does not work alone. Background Intelligent Transfer Service transfers files in the background using idle network bandwidth, and Microsoft’s own description notes that anything depending on BITS, Windows Update included, cannot automatically download when it is disabled. Cryptographic Services supports confirmation of file signatures and the retrieval of root certificates from Windows Update; Microsoft says reconfiguring it is not recommended and that services explicitly depending on it fail to start if it is disabled. Windows Installer handles the packages that arrive.

No Microsoft page states a required startup type for any of these on current Windows. What matters is that none of them is Disabled and that each can start when asked. Anyone telling you a specific value is mandatory is repeating folklore.

When the change will not stick

  • Run gpresult /h report.html and read the report. A policy reapplying on its schedule is the most common reason a local change reverts.
  • Look for a third-party update blocker still installed. Removing the policy it added is not the same as removing the product.
  • Windows includes a protected mechanism that reverts tampering with update components. You cannot reconfigure it through the services console and you should not try; find the thing that keeps putting the machine into a blocked state instead.
  • Check the machine is not being managed by a device management platform that reapplies configuration silently.
  • Confirm you are actually an administrator on the machine. Changing service configuration requires it, and on a managed machine you may need the policy changed centrally as well.

Confirming it is really fixed rather than temporarily working

A service that starts once proves very little on a machine that has been deliberately blocked. Restart it, run a scan, then restart the machine and run a second scan. Policy refreshes and scheduled tasks run on their own clocks, and a change that survives a restart and a policy cycle is a change that held.

Every code this article covers

Code What it points at Source
0x80070422 ERROR_SERVICE_DISABLED, decimal 1058: the service cannot be started, either because it is disabled or because it has no enabled devices associated with it Microsoft Learn
0x8007043C ERROR_NOT_SAFEBOOT_SERVICE, decimal 1084: this service cannot be started in Safe Mode Microsoft Learn
0x8007041D ERROR_SERVICE_REQUEST_TIMEOUT, decimal 1053: the service did not respond to the start or control request in a timely fashion Microsoft Learn
0x8007042A ERROR_SERVICE_SPECIFIC_ERROR, decimal 1066: the service has returned a service-specific error code of its own, so read that service’s event rather than the service control manager’s Microsoft Learn
0x80070433 ERROR_SERVICE_DEPENDENCY_DELETED, decimal 1075: the dependency service does not exist or has been marked for deletion Microsoft Learn

Confirm the fix worked

  1. Confirm Windows Update is not set to Disabled and can be started without an error.
  2. Run a check for updates and confirm a scan actually runs rather than failing immediately.
  3. Confirm Background Intelligent Transfer Service and Cryptographic Services are both able to start.
  4. Restart the machine, wait for a policy refresh, and check for updates once more to be sure nothing is reverting your change.
  5. Run gpresult /h report.html and confirm no policy is still blocking the service.

Questions people ask about this

Does this cost anything to fix?

No. This is a service configuration problem and every step is free. It has nothing to do with activation, licensing or genuineness, whatever a search result may suggest.

Should Windows Update be set to Automatic or Manual?

Either works. What produces this code is Disabled. No Microsoft page states a required default startup type for wuauserv on current Windows, and a stopped service with a Manual startup type is a healthy machine because the service is trigger-started when it is needed.

My changes keep reverting. What is doing that?

Either a Group Policy reapplying on its schedule, a third-party update blocker still installed, or the built-in repair mechanism restoring a component you altered. Find and remove the blocker, and check gpresult for a policy, rather than fighting the symptom.

Why do I get a different code once the service is enabled?

Because you have moved past the disabled state to a different failure. 0x8007041D means the service did not respond to the start request in time; 0x8007042A means it started and returned an error of its own, in which case the detail is in that service’s event rather than in the service control manager’s.

Can I fix this without administrator rights?

No. Changing service configuration requires local administrator rights, and on a managed machine you may also need the policy changed centrally before a local change will stick.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0x800F0923: a driver or binary is not compatible with the new build License Error 0xC1900130 and 0x80190001: the feature update download never finishes Free Fix 0x80D01001: Delivery Optimization cannot provide the download service Free Fix 0x800F0831 CBS_E_STORE_CORRUPTION: the component store itself is damaged
โ† Back to Knowledge Base