Recommended Free Tools
If Windows or an installer shows 0X800070422, first copy the code again exactly. The extra zero may be a vendor-specific rendering or a transcription error; the Microsoft-documented code is usually 0x80070422. That code normally means the Windows Update service is disabled or stopped. Confirming the code and the installation context prevents you from changing the wrong service or driver.
Work through the manual checks below in order. They cover Windows Update and language-pack failures, Store or MSI installations, and device-driver installers.
As an Amazon Associate I earn from qualifying purchases.
1. Confirm the code and record the installation context
Write down the complete message, including capitalization and every digit. Then record what was being installed, your Windows edition and build, the installer name and version, and whether the failure appeared in Settings, Windows Update, Microsoft Store, an MSI package, or a device-driver wizard.
Why the spelling matters
0X800070422 contains an additional zero compared with 0x80070422. Some vendor pages display a code incorrectly, while another installer may use its own code. Do not assume they are identical until you compare the text shown by Windows with the installer log or message.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Use the context to choose the next branch
| Where the error appears | What to check first |
|---|---|
| Windows Update or a language pack in Settings | Windows Update service, Windows Update troubleshooter, and update-component health |
| Microsoft Store or an MSIX package | Whether Windows Update is available, the account has permission to install apps, and Store or package-specific logs |
| An MSI or traditional desktop installer | Administrator permission, installer logs, free disk space, and security software interference |
| A printer, graphics, audio, Wi-Fi, Bluetooth, USB, or other device driver | Device Manager’s problem code and SetupAPI installation logs |
2. Check the Windows Update service
For the likely 0x80070422 interpretation, Microsoft’s installation-error guidance says to ensure that the Windows Update service is enabled. A stopped or disabled service can prevent an update, language pack, Store dependency, or installer prerequisite from completing.
- Press Windows key+R, type
services.msc, and press Enter. - Find Windows Update in the list. Double-click it.
- In Startup type, remove a Disabled setting. Use the startup mode required by your organization; Windows commonly uses a trigger-start or manual mode, while some managed systems use Automatic.
- If Service status is Stopped, select Start. Select Apply, then OK.
- Also check that Background Intelligent Transfer Service (BITS) is not disabled, because Windows Update uses it to transfer files. Start it if your policy allows and it is stopped.
- Restart Windows and retry the same installation, rather than switching to a different installer while testing.
If a work or school policy immediately disables the service, do not repeatedly override it. Contact the administrator and provide the exact code and the service status.
3. Run the Windows Update troubleshooter
Windows includes a diagnostic for update failures. It can identify a disabled service, a configuration problem, or a damaged update state without deleting your personal files.
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 →- Open Settings.
- Go to System → Troubleshoot → Other troubleshooters.
- Find Windows Update and select Run.
- Apply any recommended correction, restart if requested, and retry the installation.
The exact labels can vary slightly by Windows release. If the troubleshooter reports that it could not repair the problem, keep its findings with the error code for escalation.
4. Reset Windows Update components when downloads are stuck or corrupt
Microsoft’s update guidance also describes resetting the update cache and related components. This is appropriate when updates remain pending, repeatedly download the same package, or fail after the Windows Update service has been enabled.
Before changing folders, close Settings and other installers. Create a restore point or ensure that important data is backed up. In Windows Terminal (Admin) or Command Prompt (Admin), stop the transfer and cryptographic services, rename the caches, and start the services again:
Rank #2
- Emergency Boot USB compatible with Windows 98, 2000, XP, Vista, 7, and 10. It has never ben so easy to repair a hard drive or recover lost files
- Plug and Play type usb - Just boot up the usb and then follow the onscreen instructions for ease of use
- Boots up any PC or Laptop model and brand.
- Virus and Malware Removal made easy for you
- This is your one stop shop for PC Repair of any need!
net stop wuauserv
net stop bits
net stop cryptsvc
ren %systemroot%SoftwareDistribution SoftwareDistribution.old
ren %systemroot%System32catroot2 catroot2.old
net start cryptsvc
net start bits
net start wuauserv
Run each line separately so you can see an error. A message that a service is not running is usually harmless; an access-denied message means the terminal was not opened with administrator rights or a policy is blocking the change. Windows recreates fresh cache folders after the next update check. Restart the computer, open Settings → Windows Update, select Check for updates, and then retry the original installer.
5. Check account permissions, connectivity, and security interference
Use an account that can install
Sign in with an administrator account or provide administrator credentials when the installer requests them. If the package is supplied by an employer or school, the account may be intentionally restricted; ask the administrator to perform the installation instead of weakening policy controls.
Verify the connection and system conditions
- Use a stable connection and temporarily avoid captive portals, metered networks, or VPN routes that block Microsoft update endpoints.
- Check that the system clock, date, and time zone are correct; an incorrect clock can invalidate signed downloads.
- Confirm that the system drive has enough free space for the package and its temporary files.
- Disconnect nonessential USB devices while testing a software installation, but leave the target device connected when diagnosing its driver.
Account for security software safely
Security software, application-control rules, and corporate endpoint policies can block an installer or its child process. Follow your local security policy before changing anything. If permitted, pause a third-party security product only for the installation test, disconnect from untrusted networks, and turn protection back on immediately afterward. A security product warning is not proof that Windows is infected, and disabling protection is not a permanent fix.
6. Repair Windows system files when corruption is indicated
Use system-file repair when the troubleshooter reports component corruption, several Windows features fail at once, or Event Viewer shows servicing errors. Save any logs first and back up important data because repairs can change protected system files.
- Open Windows Terminal (Admin).
- Run
DISM /Online /Cleanup-Image /RestoreHealthand wait for it to finish. Do not close the window even if progress appears to pause. - After DISM completes, run
sfc /scannow. - Restart Windows and test the same installer again.
If either command reports that it could not complete the repair, record the exact result instead of repeatedly rerunning it. A servicing failure may require an in-place Windows repair or support from the system administrator.
7. If the failure is a Microsoft Store, MSIX, or MSI installation
Store and MSIX packages
First complete the Windows Update-service and troubleshooter checks because Store and MSIX deployments can depend on current servicing components. Confirm that you are signed in with the account allowed to install the package and that the package matches your Windows architecture and edition. If the Store displays a separate error number, use that number rather than treating every message as 0x80070422.
Rank #3
- Fresh USB Install With Key code Included
- 24/7 Tech Support from expert Technician
- Top product with Great Reviews
Traditional MSI installers
Run the installer from a local folder, not a removable drive or an unavailable network share. Right-click the package and choose Run as administrator when appropriate. Preserve the MSI log or the installer’s own log, including the failing action and timestamp. If only one application fails while Windows Update works normally, the application’s prerequisites, package, or uninstall remnants are more likely than the Windows Update service to be responsible.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.8. If the installer is for a device or driver
A device installation can display a code that resembles an update error but requires a different diagnosis. Microsoft Learn explains that Device Manager properties show the device’s problem-code value and message, while SetupAPI logging can identify the failing driver package or installation component.
- Right-click Start and open Device Manager.
- Expand the relevant category, right-click the device, and choose Properties.
- Read the Device status message and note the numeric problem code on the General tab.
- Record the device’s hardware identifiers from Details → Hardware Ids and the driver provider, date, and version shown on the Driver tab.
- Review the SetupAPI log, normally located at
%windir%infsetupapi.dev.log, around the timestamp of the failed installation. Look for the package name, matching hardware ID, and the first explicit error. - Use the device manufacturer’s official package for your exact Windows version and hardware model. Do not force a driver intended for a different model.
If Device Manager shows a different problem code, troubleshoot that code directly. The presence of a text string resembling 0X800070422 does not override the device-specific diagnostic.
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 errors9. Decide when to stop and escalate
Escalate when the service is controlled by policy, component reset fails, system-file repair cannot complete, or a device installation repeatedly fails with the same package. Give the software vendor, hardware manufacturer, or Microsoft Support a compact evidence bundle:
- The exact code as displayed, including the disputed extra zero.
- The installer or package name and version, Windows edition and build, and the date and time of each attempt.
- Whether Windows Update, the Store, an MSI package, or a device driver produced the message.
- The Windows Update troubleshooter result, service status, and any Event Viewer entries.
- For devices, the Device Manager problem code, hardware ID, driver version, and relevant SetupAPI lines.
- The manual steps already completed and whether the failure changed after each step.
10. Manual fixes versus outside help
| Approach | Authority | Reversibility and risk | Diagnostic transparency | Best fit |
|---|---|---|---|---|
| Microsoft settings, troubleshooter, and documented reset | Highest for Windows Update components | Generally reversible, but cache resets should be preceded by a backup | Shows service states, troubleshooter findings, and command results | Windows Update, language packs, and servicing failures |
| Generic third-party repair software | Independent of Microsoft | Results vary; review every proposed change before applying it | Depends on the product’s logs and explanations | Broad Windows symptoms after official diagnostics, not a substitute for identifying the installer context |
| Qualified technician or administrator | Depends on the person’s expertise and access | May involve paid labor or invasive repairs; data-loss risk must be discussed first | Can correlate logs and policy restrictions directly | Managed PCs, repeated component corruption, or hardware-specific failures |
The code alone cannot prove that Windows Update is the cause. The service check is the safest first test because it is quick and directly addresses the documented meaning of 0x80070422; the later branches prevent you from applying an update fix to an MSI or driver problem.
Quick Recap
As an optional shortcut after the Microsoft checks, Outbyte PC Repair can look for more than 100 common Windows issues where possible, adjust settings, clean temporary and cache files, and provide tools such as vulnerability checks and an app-crash log. It runs on Windows 11, 10, 8, and 7 and offers a category-based free trial of at least two days before a subscription; it complements antivirus software, does not replace it, results vary, and no tool repairs every crash.
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.

