Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Error 0x80070422 on Windows Server 2016 usually means the Windows Update service is disabled or stopped. Microsoft identifies the condition as ERROR_SERVICE_DISABLED. Set the Windows Update service to Automatic, start it, and retry the operation before attempting broader repairs. The title’s 0X080070422 contains an extra zero compared with Microsoft’s documented 0x80070422, so verify the exact value in the original message or log first. If starting the service does not help, inspect dependencies and policy controls, reset Windows Update components, and then use Microsoft’s supported DISM image-repair procedure for Windows Server 2016 or later.
What does error 0x80070422 mean on Windows Server 2016?
Microsoft’s Windows Update troubleshooting table defines 0x80070422 as a Windows Update service that is disabled or stopped. Microsoft Learn maps it to ERROR_SERVICE_DISABLED and explains: “This issue occurs when the Windows Update service stops working or isn’t running.” See Microsoft’s Windows Update troubleshooting guidance and the common Windows Update error reference.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →The hexadecimal spelling matters. 0X080070422 in a title or copied note may be a transcription error; the Microsoft-documented value has one leading zero after the x: 0x80070422. Do not change a production server until you have checked the original dialog, Event Viewer entry, Windows Update log, or installation log.
The code identifies a service-state condition, not necessarily the complete cause of every failed task. Confirm whether it appeared while checking for updates, installing an MSU package, servicing a role or feature, or running another workflow. The associated event and CBS.log entries can identify which service the failed operation actually requested.
Popular on Amazon
What should I record before changing the server?
Capture enough evidence to make the change reversible and to distinguish a Windows Update problem from a different servicing failure.
- Write down the exact error text and hexadecimal value, including capitalization and leading digits.
- Record the operation that failed, such as an update scan, an individual MSU installation, or role and feature servicing.
- Note the timestamp, server name, signed-in account, and any event ID shown with the failure.
- Save relevant Service Control Manager and Windows Update events. For servicing failures, preserve the related CBS.log entries.
- Check your change-control requirements and verify that a current backup or recovery plan exists before component reset or image servicing.
This record gives you a before-and-after comparison and prevents an unrelated service from being enabled merely because its name looks plausible.
Recommended Free Tools
How do I start the Windows Update service?
For the documented 0x80070422 condition, check the Windows Update service first. This is the smallest, most reversible change and normally requires only a service restart rather than a server reboot.
- Sign in with an account allowed to manage services on the server.
- Open the Run dialog, enter
services.msc, and press Enter. - In the Services console, locate Windows Update.
- Open its properties and check Startup type. Set it to Automatic, then select Apply.
- If Service status shows Stopped, select Start. Wait for the status to change to Running, then select OK.
- Retry the exact operation that produced the error. Keep the original timestamp and record whether the retry succeeds or produces a new event.
Do not change every service set to Disabled. Server roles, security baselines, and maintenance policies often intentionally disable services that a particular host does not need. Change only the service required by the failed operation and document the previous startup setting.
What if Windows Update will not start?
A failed start means the startup setting alone was not the whole problem. Use the service’s diagnostic information and the server’s policy records instead of repeatedly clicking Start.
Check the Dependencies tab
Open Windows Update properties and select Dependencies. A dependency that is stopped, disabled, or failing can prevent Windows Update from starting. Investigate that specific service and its events; do not enable unrelated dependencies without confirming that the original operation requires them.
Also popular on Amazon
- Server 2022 Standard 16 Core
Read Service Control Manager events
In Event Viewer, review Windows Logs and the entries from Service Control Manager around the failure time. The event may identify an account, permission, dependency, timeout, or service-name problem that the short error dialog does not show.
Check Group Policy and hardening controls
A domain or local Group Policy setting, security baseline, or hardening product can force Windows Update back to Disabled or block a start request. Compare the effective policy with your organization’s patching design and ask the policy owner to make the supported change. If the service returns to Disabled after a policy refresh, changing it manually is only temporary.
Verify permissions and service configuration
Confirm that the service configuration has not been altered by an administrator, deployment script, or security product. Preserve the relevant event data before repairing configuration; it can be needed to explain why the change occurred and to avoid reintroducing it during the next deployment.
How do I reset Windows Update components?
If Windows Update is set to Automatic and starts successfully but the same installation or scan still returns 0x80070422, Microsoft’s installation-error guidance recommends resetting Windows Update components. Use the procedure in Microsoft’s Windows upgrade and installation error guidance, following the commands and order for the installed Server 2016 build.
Free tools Windows power users keep installed
One-click scans. No signup required.
A component reset is broader than changing one startup setting. It can remove or rebuild update working data and reinitialize update components, so schedule it under your normal maintenance and change-control process. Before running it:
- Confirm that the error is still reproducible and that the service state has been recorded.
- Close update and servicing consoles and stop any planned deployment that could compete with the reset.
- Keep a copy of the relevant event entries and CBS.log data.
- Ensure you have a verified recovery path if the server is a critical production system.
After the reset procedure completes, restart the affected service if the Microsoft procedure calls for it, retry the original operation, and compare the new log entries with the ones captured before the reset. A successful component reset should be judged by the original task completing, not merely by the service showing Running.
Also popular on Amazon
When should I use DISM to repair the Windows image?
Use DISM after service configuration and the supported component reset have not resolved the failure, or when CBS.log and servicing events indicate image corruption. Microsoft documents DISM as a tool for servicing and repairing Windows images and states that its Windows Server update-corruption procedure applies to Windows Server 2016 or later. Follow the version-appropriate procedure in Microsoft’s Windows Server update-corruption article.
DISM is an image-wide repair path, not a simple Windows Update restart. Run it from an elevated shell, use the supported options and repair source for your installed build, and preserve the DISM log. The available repair source and servicing configuration can vary by environment, so do not assume that a random installation image or an image from another build is suitable.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Plan the work as a controlled maintenance change. Image servicing can take longer than a service restart and may require a reboot or a maintenance window depending on the operation and the server’s state. Record the command line, start and finish times, return status, and any new CBS or DISM errors so that a failed repair can be escalated with useful evidence.
Which fix should I try first?
The choices differ in scope and rollback risk. Start with the narrowest action that tests the documented cause, then move outward only when the evidence supports it.
| Remedy | Scope | Typical downtime | Reversibility | Best evidence | Rollback readiness |
|---|---|---|---|---|---|
| Set Windows Update to Automatic and start it | One service | Usually a service interruption; no reboot is normally needed | High: restore the previous startup setting if policy permits | Services console status and Service Control Manager events | Record the original startup type and change time |
| Investigate dependencies, policy, hardening, and permissions | The specific blocker affecting the service | Depends on the controlling policy or service | Depends on the owner of the setting | Dependencies tab, effective policy, security records, and events | Coordinate with the policy or security administrator |
| Reset Windows Update components | Update working components and related data | Maintenance window recommended | Lower than a single-service change; preserve data and follow Microsoft’s sequence | Pre- and post-reset Windows Update and CBS.log entries | Verified backup and documented change plan |
| DISM image repair | Windows image and servicing store | Potentially longer maintenance; reboot requirements depend on the repair | Lowest of these options because it changes the image | DISM log, CBS.log, and servicing events | Verified recovery path and build-appropriate repair source |
How do I verify that the repair worked?
Verification must use the same operation that originally failed. A service that starts is only an intermediate result.
- Retry the original update scan, MSU installation, or role and feature action.
- Check whether the task completes and whether it reports a different error.
- Review new Service Control Manager, Windows Update, CBS, and DISM entries at the retry time.
- Confirm that Group Policy or a scheduled configuration task has not reverted the startup setting.
- Document the successful change, the exact server build, and any maintenance-window impact.
If the retry produces a different code, stop applying 0x80070422-specific fixes and investigate the new code on its own terms. If it still fails with the same value after DISM, retain the logs and escalate through your Windows Server support process rather than repeatedly rerunning repairs.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Also popular on Amazon
Why can the error appear during an operation other than Windows Update?
The code is most commonly associated with Windows Update, but the failed workflow determines which service request triggered it. An MSU installation, role or feature servicing, or an orchestration tool can surface the same service-disabled condition while reporting its own short message.
Use the operation timestamp to correlate Event Viewer entries with CBS.log and Windows Update records. The service named in those records is more reliable than an assumption based on the screen that displayed the error. This is especially important on Server 2016 systems managed by domain policy, WSUS, scheduled maintenance, or configuration automation.
What should I avoid when troubleshooting 0x80070422?
- Do not treat the extra-zero spelling in the title as a second, different Microsoft error until the original value is verified.
- Do not enable every Disabled service on a production server; that can violate a security baseline and obscure the actual dependency.
- Do not jump to image repair before checking the Windows Update service and its policy controls.
- Do not run a component reset or DISM operation without preserving logs and confirming your recovery plan.
- Do not declare success because the Services console says Running; always repeat the failed operation and inspect its new events.
As an optional shortcut on its supported Windows editions (Windows 11, 10, 8, and 7), Outbyte PC Repair can address more than 100 common Windows issues, adjust settings, clean temporary and cache files, provide privacy and vulnerability checks, and include a real-time boost, file shredder, and app-crash log. It complements antivirus software rather than replacing it; results vary, it cannot repair every crash, and its free trial is by category for at least two days before a paid subscription.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently asked questions
Can a policy re-disable Windows Update after I start it?
Yes. A domain or local policy, security baseline, or management script can reapply a Disabled setting after a manual change. If the service changes back, capture the time and coordinate with the administrator who owns the effective policy instead of repeatedly changing the service locally.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Does 0x80070422 prove that the server is infected?
No such conclusion follows from this code alone. Microsoft documents it as a service-disabled or service-stopped condition; use your normal security monitoring process separately if other evidence raises a security concern.
Can the service be Running while the operation still fails with this code?
It can happen when the operation references a different required service, when a policy changes the state between checks, or when the displayed code came from an earlier attempt. Correlate the exact failure timestamp with Service Control Manager and CBS.log entries before changing additional services.
Will DISM always need an internet connection?
Not necessarily. The usable repair source depends on the installed build and how the server is serviced. Follow the Server 2016 procedure’s source requirements and confirm that the selected source matches the image before starting the repair.
Also popular on Amazon
Is a reboot required after changing the Windows Update startup type?
Usually the immediate test is a service start followed by a retry, not an automatic reboot. A reboot may still be required by the update or image-servicing operation itself, so follow the result and any restart request shown in the servicing logs.
Frequently Asked Questions
Can a policy re-disable Windows Update after I start it?
Yes. A domain or local policy, security baseline, or management script can reapply a Disabled setting after a manual change. If the service changes back, capture the time and coordinate with the administrator who owns the effective policy instead of repeatedly changing the service locally.
Does 0x80070422 prove that the server is infected?
No such conclusion follows from this code alone. Microsoft documents it as a service-disabled or service-stopped condition; use your normal security monitoring process separately if other evidence raises a security concern.
Can the service be Running while the operation still fails with this code?
It can happen when the operation references a different required service, when a policy changes the state between checks, or when the displayed code came from an earlier attempt. Correlate the exact failure timestamp with Service Control Manager and CBS.log entries before changing additional services.
Will DISM always need an internet connection?
Not necessarily. The usable repair source depends on the installed build and how the server is serviced. Follow the Server 2016 procedure’s source requirements and confirm that the selected source matches the image before starting the repair.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsIs a reboot required after changing the Windows Update startup type?
Usually the immediate test is a service start followed by a retry, not an automatic reboot. A reboot may still be required by the update or image-servicing operation itself, so follow the result and any restart request shown in the servicing logs.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
