Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Windows Update error 0x80070422: the Windows Update service is disabled or not running

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

When a Windows Update scan or install stops with 0x80070422, Microsoft's Windows Update error pages give one meaning: the Windows Update service is not running. In Windows' own system error list, 0x422 is error 1058, ERROR_SERVICE_DISABLED: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it."

The fix is to find out whether the service is disabled or only stopped, set a start type other than Disabled if it was disabled, and start it. Write down the current state first so the change can be reversed, and find out who set it, because a service that is turned off on purpose will be turned off again.

What the error means

Microsoft's "Windows Update error codes by component" page lists 0x80070422 with the description "Windows Update service stopped working or isn't running." The "common errors and mitigation" page lists it as ERROR_SERVICE_DISABLED with the description "This issue occurs when the Windows Update service stops working or isn't running." and the mitigation "Check whether the Windows Update service is running."

The Windows system error code list explains the code behind the name. In it, ERROR_SERVICE_DISABLED is 1058 (0x422), and the message is the one quoted above.

Microsoft's sc.exe pages use the service name wuauserv in their examples; the sc.exe config page gives its display name as "Automatic Updates", and its sc.exe query page uses sc.exe query wuauserv as the example for displaying service information. Microsoft's Windows Update troubleshooting page calls the service Windows Update. Check on your own computer that the two names are the same service: the Get-Service command below prints both.

Two start types matter. Microsoft's Set-Service page describes Disabled as "The service is disabled and cannot be started by a user or application", and Manual as "The service is started only manually, by a user, using the Service Control Manager, or by an application." The error message itself says the service "cannot be started, either because it is disabled or because it has no enabled devices associated with it". For a Windows Update scan, the first half of that sentence is the one that applies: Microsoft's mitigation is to check that the service is running.

Microsoft's Windows Update troubleshooting page adds a second service for the Windows 10 Settings screen. If the Settings screen is stuck at scan, it says to check that two services are running in Services.msc: Update State Orchestrator and Windows Update.

Do not confuse the code with its neighbour. The same page describes a feature-update fault in the Windows Update log that ends in 0x80070426, which it translates as ERROR_SERVICE_NOT_ACTIVE, "The service has not been started." In that case the service in question is the Microsoft Account Sign In Assistant, not Windows Update, and Microsoft's remedy is to reset that service to its default StartType of "manual". It is a different error with a different service, so the steps below do not apply to it.

Likely causes

Cause What you see How to confirm
The Windows Update service has start type Disabled 0x80070422 on every scan or install attempt Get-Service wuauserv shows StartType Disabled
The service is stopped but its start type is not Disabled Microsoft's error list says the service "stopped working or isn't running" Start type shows Manual or Automatic and Status shows Stopped; Microsoft's pages give no further diagnosis
Update State Orchestrator is not running (Windows 10 Settings) Settings frozen at the scan step Services.msc shows Update State Orchestrator stopped
Something keeps setting the service to Disabled The fix works, then the error returns Start type is Disabled again after a restart or policy refresh

Prove the cause before changing anything

All of these only read. Run them in an elevated PowerShell window on the affected computer.

Show the start type and state of the Windows Update service. This is Microsoft's pattern from the Set-Service page, pointed at wuauserv:

Get-Service wuauserv | Select-Object -Property Name, DisplayName, StartType, Status

Show the service information with sc.exe, using Microsoft's own example service:

sc.exe query wuauserv

Write down the start type and status. If StartType reads Disabled, you are looking at error 1058 as Microsoft defines it. If StartType is Manual or Automatic and the service is Stopped, the "disabled" half of the error 1058 message does not apply. Microsoft's mitigation, "Check whether the Windows Update service is running", still does: start the service and look at what stops it.

Example (illustrative): on app01 at contoso.com.au, a hardening script run last month turned off services the server's owner did not recognise. A patch run now ends in 0x80070422. Get-Service wuauserv | Select-Object -Property Name, StartType, Status returns wuauserv, Disabled, Stopped. That matches Microsoft's description, so the start type is the change to make.

Fix

Microsoft's pages do not state the default start type for the Windows Update service, so none is named here as "the default".

Before you change it, make sure you have the output of the Get-Service command above. Its Name, StartType and Status values are the way back.

Risk: the next command changes the Windows Update service from Disabled to Manual, which allows updates to scan, download and install again on this computer. If a patching freeze or a vulnerability-management policy turned the service off on purpose, this changes that decision, so check with the person who owns it before you run it. Run it only if the recorded StartType read Disabled; if it read Automatic or Manual, leave the start type alone and go straight to starting the service.

Set-Service -Name wuauserv -StartupType Manual

Risk: the next command starts the Windows Update service now, so scans and any queued updates can begin on this computer straight away. Run it in a quiet period for the server.

Microsoft's Set-Service page shows -Status Running for starting a service:

Set-Service -Name wuauserv -Status Running

To undo it, put the service back as you recorded it. If the recorded Status was Stopped, stop the service first. Only run this if the recorded Status was Stopped:

Set-Service -Name wuauserv -Status Stopped

Then set the start type back. Only run this if the recorded StartType was Disabled:

Set-Service -Name wuauserv -StartupType Disabled

If you set a start type other than Manual yourself, put the recorded value back with this command, replacing the placeholder with the recorded value. Microsoft's page accepts Automatic, AutomaticDelayedStart, Disabled and Manual:

Set-Service -Name wuauserv -StartupType <recorded start type>

If the Settings screen on a Windows 10 client is stuck at scan, check the Update State Orchestrator service in Services.msc as the troubleshooting page says. Microsoft's page names no command for it.

Confirm the fix

  • Run the Get-Service command again. StartType should read Manual (or Automatic) and Status should read Running.
  • Trigger a scan again. The 0x80070422 error should not appear. If a different code appears, look it up on Microsoft's error list by the new code.

Disruptive step: a restart interrupts everyone using the computer, so do not restart it just for the last check below.

  • After the next planned restart, check the start type again. Microsoft's pages say nothing about what resets a start type, so this check is the proof that nothing sets it back.

What to watch afterwards

  • The start type of wuauserv after the next restart and after the next Group Policy refresh. If it is Disabled again, something changed it. Microsoft's pages do not say what; ask whoever manages the build, hardening script or security product.
  • Other services that a hardening script touched. Microsoft's Windows Update troubleshooting page notes that Update State Orchestrator and Windows Update must both be running for the Settings screen to scan, and it describes a separate case where a stopped Microsoft Account Sign In Assistant service stops feature updates from being found.
  • The next update's result in the Windows Update log, not only the absence of this code.
  • Windows Update policy. Microsoft's troubleshooting page says Windows Update has "a wide range configuration policy" and that "misconfiguration or setting conflicting policies may lead to unexpected behaviors." A policy that conflicts with your patching plan can look like a service fault, so compare the two when the same machine misbehaves again.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's two Windows Update error pages name Windows 10 and Windows 11. The error 1058 definition applies to Windows services in general and its page gives no version restriction. Microsoft's pages do not say which Windows Server versions show 0x80070422 for Windows Update specifically, and they do not state the default start type or what disables the service. Microsoft's pages do not describe how a change to one service's start type affects other roles or agents on the same server, so record the state of every service you change and change one at a time.

The Get-Service and Set-Service examples here follow the syntax Microsoft shows for other services (BITS, WinRM) with the service name replaced by wuauserv. Microsoft's pages show no example that uses wuauserv with those cmdlets, so run the read-only Get-Service command first and confirm that it returns the service you expect before you change anything.

Sources