How to Fix Windows Update Error 0x80248014
What error 0x80248014 means
Windows Update keeps its own private database on your PC — a data store of every update the system knows about, which services handle them, and what has been downloaded. Error 0x80248014, officially named WU_E_DS_UNKNOWNSERVICE, means Windows went to that data store looking for its own update service registration and came back empty: an operation did not complete because the service is not in the data store. Without a trusted service registration, Windows has no safe way to know which updates apply to your machine or how to verify them, so it halts the entire update process with the message "There were problems installing some updates, but we'll try again later."
The key detail is where it breaks: unlike most update errors that fail during download or installation, this one fails during detection — the very first phase, before a single byte is fetched. That is why the same fix attempts keep failing and why retrying tomorrow changes nothing: the local metadata is the problem, not the connection. Rebuilding that metadata is the whole game here, and the steps below attack it from the lightest touch to a full rebuild of the update stack.
Common causes
- Corrupted SoftwareDistribution folder: the cache holding update metadata gets damaged by an interrupted download or a crash mid-update, leaving the data store unreadable.
- Corrupted Catroot2 folder: this folder stores update signatures — if it is out of sync, Windows cannot verify anything and treats the service as unknown.
- Windows Update services not running: the Windows Update (wuauserv), BITS, or Cryptographic Services fail to start or get stuck, so the data store is never loaded.
- Missing or damaged system files: the update engine's own files got corrupted, so the service registration it should find no longer exists.
- Antivirus or security software interference: a scan locks or quarantines files inside the update cache mid-download, silently corrupting the data store.
How to fix error 0x80248014 — step by step
Work through these fixes in order. Step 1 takes two minutes and catches the easy cases, steps 2–4 rebuild the damaged parts, and the last two cover stubborn cases including Store downloads.
- Run the Windows Update troubleshooter first. Open Settings, go to System, then Troubleshoot, then Other troubleshooters, and click Run next to Windows Update. Let the troubleshooter scan the update components, apply whatever repairs it suggests, and reboot. It fixes simple registration glitches quickly, so this quick run can save you from the manual steps below. Check for updates again after the reboot to see whether the error is gone.
- Clear the corrupted update cache (SoftwareDistribution and Catroot2). Open Command Prompt as administrator and stop the update services with
net stop wuauserv,net stop cryptSvc,net stop bits, andnet stop msiserver, pressing Enter after each line. Then rename the two cache folders withren C:\Windows\SoftwareDistribution SoftwareDistribution.oldandren C:\Windows\System32\catroot2 catroot2.old, so Windows builds fresh copies instead of reusing the damaged ones. Restart the services withnet start wuauserv,net start cryptSvc,net start bits, andnet start msiserver, then reboot and check for updates again. - Reset the Windows Update components. Open Command Prompt as administrator and run
net stop wuauserv,net stop cryptSvc,net stop bits, andnet stop msiserver, then runnetsh winsock resetandnetsh winhttp reset proxyto clear any network configuration interfering with the update servers. Next delete the corrupted download queue by runningrd /s /q C:\Windows\SoftwareDistributionandrd /s /q C:\Windows\System32\catroot2, restart the four services withnet start, and reboot. This deeper reset fixes broken service registrations that the basic cache rename misses. - Repair system files with DISM and SFC. Open Command Prompt as administrator and run
DISM /Online /Cleanup-Image /RestoreHealth, which downloads clean replacement files for anything the update engine depends on, and wait for it to reach 100 percent. When it finishes, runsfc /scannowand reboot when it is done. These two commands repair missing or damaged Windows files that can silently corrupt the update data store and trigger 0x80248014 on every scan. - Reset the Microsoft Store cache if Store downloads fail too. Press Win plus R, type
wsreset.exe, and press Enter — a blank Command Prompt window will appear, reset the Store cache, and close by itself, then launch the Store. Because 0x80248014 can block Microsoft Store downloads with the same unknown-service complaint, this clears the shared download cache. If Store apps still refuse to download, open PowerShell as administrator and re-register the Store withGet-AppxPackage -allusers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}, then reboot. - Reinstall Windows in place if nothing else works. Download the Windows 11 (or 10) Media Creation Tool from Microsoft's site, run it, and choose Upgrade this PC now. On the options screen pick Keep personal files and apps so nothing you own is removed, and let the reinstall finish — it rebuilds the entire Windows Update stack, including its data store and service registrations, from scratch. After setup completes, open Settings and check for updates; the repair install resolves even deeply rooted 0x80248014 cases.
Did this fix it? Quick checklist
- Windows Update troubleshooter ran and its repairs were applied
- SoftwareDistribution and Catroot2 folders renamed or deleted, services restarted
- Windows Update components reset, DISM and SFC finished clean
- Microsoft Store cache reset (wsreset.exe) if Store downloads also failed
If 0x80248014 still appears after all six steps, open Event Viewer (Win + X > Event Viewer), go to Windows Logs > System, and filter for WUAUHandler or Windows Update errors around each check — the details can confirm which component keeps failing to register. Check C:\Windows\WindowsUpdate.log too if you enabled verbose logging. Errors that survive a full component reset, clean system files, and an in-place reinstall are rare — but they usually point at a failing system drive, so run a full disk health check and back up your data.
Frequently asked questions
What does Windows Update error 0x80248014 mean?
It is Windows telling you that it went looking for its own update service in the local data store and found nothing usable. The official name is WU_E_DS_UNKNOWNSERVICE: an operation did not complete because the service is not in the data store. In practice, the update database on your PC is missing, corrupted, or out of sync, so Windows Update has no trustworthy list of what to download and refuses to continue.
What causes error 0x80248014?
The most common cause is a corrupted SoftwareDistribution or Catroot2 folder — the local caches where Windows keeps update metadata and signatures. It can also come from the Windows Update or BITS services failing to start, missing or damaged system files after an interrupted update, or the Microsoft Update service being unregistered after a botched upgrade. Antivirus software locking the cache folders mid-download is another frequent trigger.
Will resetting Windows Update components delete my files?
No. Resetting the update components only clears Windows' own update cache and download queue — SoftwareDistribution, Catroot2, and temporary update files. Your documents, photos, programs, and settings are untouched. The only thing lost is the history of which updates were downloaded, which Windows rebuilds automatically on the next update check.
Can error 0x80248014 block the Microsoft Store too?
Yes. The Microsoft Store relies on the same download and data-store machinery as Windows Update, so the same unknown-service problem can stop app downloads and updates with the same code. If Store downloads fail alongside Windows Update, run wsreset.exe to clear the Store cache and re-register the Store package — step 5 in this guide covers both.