Error 0x80070422 is refreshingly literal: “the service cannot be started.” Windows Update needs its background services running, and on your Dell one of them is disabled, blocked, or broken. This is a configuration problem, not a corruption problem — which makes it one of the faster update errors to fix, provided you check the whole service chain instead of just the obvious one.
Dell laptops encounter this after running debloat tools, aggressive “privacy” scripts, or Dell’s own utilities conflicting over service states — and sometimes after malware cleanup that disabled services as collateral damage. The fix sequence re-enables the services properly, repairs their configuration, and verifies the chain end to end.
Services are Windows’ background workforce, and the update services are among the most tampered-with: every debloat guide, privacy script, and optimizer on the internet disables them as step one. The irony is that the people who run those tools are often the same people who then wonder why updates fail. This guide reverses that damage methodically — but take the lesson with you: the next “speed up Windows” script that offers to disable update services is offering to break updates.
Why this happens
- Windows Update service (wuauserv) disabled — by a debloat tool, optimizer, script, or manual change.
- BITS (Background Intelligent Transfer Service) disabled, breaking the download pipeline the update service depends on.
- Cryptographic Services disabled, breaking signature verification for updates.
- DCOM or RPC dependency problems preventing services from initializing.
- Corrupted service registration — the service exists but its configuration is damaged.
- Third-party security software blocking service startup.
- Group Policy disabling updates on Dell machines joined to a work or school domain.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Re-enable the Windows Update service properly
- Press Windows key + R, type
services.msc, and press Enter. - Find Windows Update, double-click it, and set Startup type to Manual (or Automatic).
- Click Start to start it now. If it starts successfully, also verify Background Intelligent Transfer Service is set to Manual/Delayed and running.
- Retry the update. This single fix resolves the majority of 0x80070422 cases — the service was simply turned off.
Fix 2: Check the full dependency chain
- In
services.msc, verify each of these is not Disabled and can start:- Background Intelligent Transfer Service (BITS)
- Cryptographic Services
- DCOM Server Process Launcher (should be Automatic)
- RPC Endpoint Mapper (should be Automatic)
- Set any Disabled ones to Manual and start them.
- DCOM and RPC are system-critical — if they will not start, the problem is deeper than update configuration.
- Retry the update after the chain is green. For service-related update failures generally, see update service not running fixes .
Fix 3: Start the services from the command line
- Open an elevated Command Prompt.
- Run:
net start wuauservnet start bitsnet start cryptSvc - If a service reports it started successfully here but the GUI showed it disabled, the Services console view was stale — trust the command line.
- If one fails to start, note the exact error message — it distinguishes a disabled service from a broken one and guides the next fixes.
Fix 4: Re-register the update service DLLs
- In the elevated Command Prompt, run:
regsvr32.exe /s wuapi.dllregsvr32.exe /s wuaueng.dllregsvr32.exe /s wups.dllregsvr32.exe /s wups2.dllregsvr32.exe /s wuwebv.dll - Then reset the service configuration:
sc config wuauserv start= demandsc config bits start= demand(note the space afterstart=) - Try starting the services again.
- This repairs damaged service registrations that prevent startup even when the configuration looks correct.
Fix 5: Check for group policy blocks (work/school Dells)
- Press Windows key + R, type
gpedit.msc(Pro/Enterprise editions), and navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update. - Look for policies like Configure Automatic Updates set to Disabled — note them but do not override corporate policy on your own.
- If the laptop is employer- or school-managed, contact IT: they may intentionally control updates, and 0x80070422 may be by design.
- On personal Dells with no policies set, continue — the block is local, not administrative.
Fix 6: Repair system files
- In an elevated Command Prompt, run:
DISM /Online /Cleanup-Image /RestoreHealth - Then:
sfc /scannow - Restart and verify the services start on boot.
- System file damage can break the service executables or their dependencies — this pair restores them. Microsoft documents the escalation on the Windows Update support page .
Fix 7: Reset the update components as a final rebuild
- Stop the services:
net stop wuauserv,net stop cryptSvc,net stop bits,net stop msiserver - Rename the caches:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 catroot2.old - Restart the services and reboot.
- This gives the services a completely fresh state to work with — the full procedure is covered in the update components reset guide . If a service still will not start after all of this, a repair install of Windows is the remaining option — but that is rare. Keep Dell drivers current via Dell Support to avoid service conflicts going forward.
Fix 8: Repair-install Windows to restore service registrations
If a service will not start even after re-registration, its underlying binaries or registry configuration are damaged beyond command-line repair.
- Download the Windows 11 ISO from Microsoft’s Windows 11 download page and mount it.
- Run
setup.exe, choose Keep personal files and apps, and complete the repair install. - Afterward, verify in
services.mscthat Windows Update, BITS, and Cryptographic Services are present and set to Manual. - Run Check for updates to confirm the pipeline works. The repair reinstalls every service binary from known-good sources.
Closing
0x80070422 on a Dell is the update engine telling you its services are off — usually by a debloat tool’s hand. Re-enable the chain (Windows Update, BITS, Cryptographic Services), repair registrations if they will not start, and check for corporate policy on managed machines. Configuration errors like this one are quick once you know which services to look at. Once the services are healthy, protect them: uninstall the debloat tool that disabled them, or at least exempt update services from its reach. Services do not disable themselves — something did it, and whatever it was will do it again at the next “optimization” pass.
