How to fix Microsoft Store error 0x80248014

Error 0x80248014 comes from the Windows Update client, which Microsoft lists as WU_E_DS_UNKNOWNSERVICE: an operation did not complete because the service is not in the data store. Microsoft Store, winget and WSL show it because they download through that client. Start by installing pending updates, then let Windows register its update services again.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What error 0x80248014 means

Microsoft's Windows Update error code list gives 0x80248014 the name WU_E_DS_UNKNOWNSERVICE and the description: "An operation didn't complete because the service isn't in the data store." The WU_E_DS part says two things. The code comes from the Windows Update client on your PC, and it comes from its data store, the small database where the client keeps the update services it knows and the updates it has seen.

A "service" here is not a Windows service in services.msc. It is an update source registered with the client: Windows Update, Microsoft Update (for Office and other Microsoft products) or the Store's own source. When a download asks for a source that the data store has no record of, the client stops with 0x80248014. Microsoft Store, winget and the WSL installer all download through this client, so they all pass the same code to you.

Why the update service is missing from the data store

Microsoft documents the meaning of the code but not a list of causes. The causes below follow from that meaning and from the cases reported on Microsoft Q&A, ranked by how often they explain what readers see.

How to fix error 0x80248014

Fix 1 and Fix 2 are quick and solve most Store cases. Fix 3 and Fix 4 rebuild the update client's services and data store, which is where the code comes from. Fix 5 and Fix 6 repair the Store app. Fix 7 and Fix 8 repair or upgrade Windows itself.

Fix 1. Check your Windows version and install pending Windows and Store updates

10 to 20 minutesNo riskAlways first. Above all when the Store, winget or WSL shows the code.

The Store and the update client are updated separately. When the Store is newer than the update components, or the other way round, the Store can ask for a source the client has not registered. Bringing both up to date is the cheapest fix, and the version check tells you early if Windows is too old.

1. Press Win + R, type winver and press Enter. Note the version, for example 25H2 or 22H2.
2. If it says Windows 10 with a version older than 22H2, such as 20H2, go to Fix 8: that version no longer gets updates.
3. Open Settings > Windows Update and select Check for updates. Install everything offered and restart if asked.
4. Open Microsoft Store, select Library in the lower left and select Get updates.
5. Wait until the Store and its components are updated, then select Get or Install on the app again.

Fix 2. Turn on Receive updates for other Microsoft products

5 minutesNo riskThe Store or Windows Update still shows 0x80248014 after Fix 1, or Office and other Microsoft apps do not update either.

This switch registers the Microsoft Update source with the update client, next to Windows Update. The code says a source is missing from the data store, and on Microsoft Q&A users suggested this switch for 0x80248014, though in that thread it did not help on its own. Turning it off and on again makes Windows write the registration anew.

1. Windows 11: open Settings > Windows Update > Advanced options.
2. Windows 10: open Settings > Update & Security > Windows Update > Advanced options.
3. Find Receive updates for other Microsoft products and turn it On. If it is already on, turn it off, restart the PC, then turn it on again.
4. Go back to Windows Update and select Check for updates.
5. Open the Store and try the download again.

Fix 3. Restart the Windows Update, BITS and Microsoft Store Install services

5 minutesLow riskDownloads hang at 0 % or at Pending, or Windows Update shows Download error - 0x80248014.

The data store is opened by the Windows Update service, and Store downloads also pass through the Background Intelligent Transfer Service and the Microsoft Store Install Service. A stuck service can hold an old copy of the data store in memory. Restarting the three makes them load it again.

Open Services, then restart Windows Update, Background Intelligent Transfer Service and Microsoft Store Install Service one by one. Check that none of them is set to Disabled: the usual startup type is Manual.

1. Open Services. Press Windows+R, type the command below and press Enter. You can also type Services in the search box on the taskbar and open the app.

   services.msc

2. Find the service. The list is sorted by Name. Click any row and type the first letter of the service to jump to it. Check the Status column (Running or empty) and the Startup Type column.
3. Restart the service. Right-click the service and select Restart. If the service is not running, select Start instead. Wait until the progress window closes.
4. Open its properties to change the startup type. Only if your guide says so: double-click the service. The General tab shows the Service name (used in commands), the Startup type and the Service status.
5. Set the startup type and apply. Choose the type from the Startup type list (Automatic, Automatic (Delayed Start), Manual or Disabled), select Apply, then Start if the service should run now, and OK.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Check and restart Windows services

Fix 4. Reset the Windows Update components and the data store

15 minutesLow riskWindows Update fails with 0x80248014 for every update, or Fix 3 did not help.

The data store that the code names lives in the C:\Windows\SoftwareDistribution folder, and the update signatures in catroot2. Renaming both folders makes Windows build a new data store and register its update services in it again, which is exactly what is missing.

1. Open Command Prompt as administrator. Type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Stop the update services. Type the commands below and press Enter after each one. If Windows says that other services depend on Cryptographic Services, it stops them too. A message that a service is not started is fine.

   net stop wuauserv
   net stop bits
   net stop cryptsvc

3. Delete the download queue files. This clears the list of downloads that the Background Intelligent Transfer Service keeps. If Windows says it cannot find the files, continue.

   del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

4. Rename the update cache folders. Renaming keeps a copy in case you need it; Windows creates new, empty folders when the services start again. If you get Access is denied, a service is still running: repeat the previous step.

   ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
   ren %systemroot%\System32\catroot2 catroot2.old

5. Start the services again. Type the commands below and press Enter after each one. The requested service has already been started is fine: Windows started it on its own.

   net start cryptsvc
   net start bits
   net start wuauserv

6. Restart and check for updates. Restart the PC. Then select Start > Settings > Windows Update > Check for updates. The first check can take longer than usual because everything is downloaded again.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Reset Windows Update components

Fix 5. Clear the Store cache, then repair or reset Microsoft Store

5 minutesLow riskWindows Update works but the Store still fails, or the Store shows other errors too.

A damaged Store cache can keep the Store asking for the same failed source. wsreset clears the cache. Repair fixes the Store app and keeps its data. Reset deletes its data on this PC, but your purchases stay in your Microsoft account.

1. Clear the Store cache. Press Windows + R, type wsreset.exe and select OK. A blank Command Prompt window opens; after a short while it closes and Microsoft Store opens by itself.
2. Open System components. If the problem stays, select Start > Settings > System > System components. Next to Microsoft Store, select the three dots and Advanced options. If Microsoft Store is not listed there, look for it in Settings > Apps > Installed apps.
3. Repair first. Scroll to Reset and select Repair. Repair keeps the app's data. Open the Store and check whether it works.
4. Reset if Repair did not help. Select Reset and confirm. This deletes the Store app's data on this PC; your purchases stay in your Microsoft account. Open the Store and sign in again.

These steps were written for Windows 11 26H2 (build 26300). The full page with the other versions and what each result means: Reset the Microsoft Store

Fix 6. Register Microsoft Store again for your account

5 minutesLow riskThe Store opens but every download fails, or Reset in Fix 5 was not available.

Registering the Store package again rebuilds its link to your account and to the update components it calls. It fixes a Store whose registration was damaged by a failed update, without touching your other apps.

Close Microsoft Store first. Then run this command in PowerShell as administrator. It registers only the Store package, which is safer than the command for all apps.

Get-AppxPackage *Microsoft.WindowsStore* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

1. Open PowerShell. Select Start, type PowerShell and select Windows PowerShell. Open it the normal way, not as administrator: in an administrator window the app is registered to the administrator account instead of yours.
2. Find the app's package. Type the command below with a part of the app's name between the asterisks and press Enter. If the app is installed, PowerShell prints its details, including Name and InstallLocation. If nothing is printed, the app is not installed for your account: see the section below.

   Get-AppxPackage -Name '*WindowsCalculator*'

3. Re-register the app. Paste the three commands below, with the same name between the asterisks, and press Enter. They read the folder the app is installed in and register its manifest again. If no red text appears, it worked.

   $InstallLocation = Get-AppxPackage -Name '*WindowsCalculator*' |
       Select-Object -ExpandProperty InstallLocation
   $ManifestPath = $InstallLocation + '\Appxmanifest.xml'
   Add-AppxPackage -Path $ManifestPath -Register -DisableDevelopmentMode

4. Open the app. Close PowerShell and start the app from Start. If it still fails, restart the PC and try once more.

These steps were written for Windows 11 25H2 and 26H2, Windows 10 22H2. The full page with the other versions and what each result means: How to re-register Microsoft Store apps with PowerShell

Fix 7. Repair system files with SFC and DISM

20 to 30 minutesLow riskSeveral updates fail, also with other codes, or Fixes 1 to 6 did not help.

DISM repairs the component store that the update client and the Store rely on, and SFC repairs protected system files. When the files of the update client itself are damaged, a new data store alone does not help.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Fix 8. Repair-install or upgrade Windows and keep your files and apps

45 to 90 minutesRead the warningWindows 10 older than 22H2, or nothing above worked.

On Microsoft Q&A, a reader on Windows 10 20H2 had 0x80248014 in the Store after wsreset, Repair, Reset and restarting the Store services. The moderator's answer was an in-place upgrade with the Media Creation Tool and Upgrade this PC now, which keeps apps, settings and files. A repair install replaces the whole update client at once.

1. Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.
2. Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
3. Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.
4. If that did not help: Reset PC. Back in Settings > System > Recovery, next to Reset this PC, select Reset PC. This keeps your personal files but removes installed apps and settings.
5. Choose Keep my files. Select Keep my files. Do not select Remove everything.
6. Choose where Windows comes from. Select Cloud download to download a fresh copy of Windows, or Local reinstall to use the files already on the PC (faster, but may not include the latest updates).
7. Reset. Review the summary and select Reset. The PC restarts several times.

These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files

If error 0x80248014 is still there

When every fix fails, the update log shows which source the client could not find. Open PowerShell and run the command below. It builds a readable WindowsUpdate.log on your desktop from the trace files.

Get-WindowsUpdateLog

If you ask Microsoft Support or your administrator for help, send your Windows version from winver, the code 0x80248014, where you saw it (Store, Settings, winget or WSL) and the log lines around it. The code is not a hardware fault: it is about a missing record in a database, not a broken part.

How to keep error 0x80248014 from coming back

Other Store codes have their own causes. If you see 0x80240037 instead, the update client says an operation is not supported: error 0x80240037.

Frequently asked questions

What does error 0x80248014 mean?

It means the Windows Update client could not finish an operation because the update service it was asked to use is not in its data store. Microsoft's Windows Update error code list names it WU_E_DS_UNKNOWNSERVICE. The data store is the client's own database of update sources and updates. Microsoft Store, winget and WSL download through this client, so they show the same code. The fixes register the sources again and rebuild the data store.

Why does Microsoft Store show a Windows Update error code?

Microsoft Store uses parts of the Windows update system to download and install apps and its own components. When that step fails, the Store shows the code the update client returned, here 0x80248014, sometimes as Code: 0x80248014. That is why the fixes cover both sides: install pending Windows and Store updates, register Microsoft Update, reset the update cache, and only then repair the Store app itself.

How do I fix Download error - 0x80248014 in Windows Update?

Restart the Windows Update, BITS and Microsoft Store Install services (Fix 3), then reset the update components so Windows builds a new data store (Fix 4). After the reset, turn on Receive updates for other Microsoft products again (Fix 2) and select Check for updates. If one update keeps failing, repair the system files with SFC and DISM (Fix 7), then try an in-place repair install (Fix 8).

What is "Failed to install or upgrade Microsoft Store package. Error code: 0x80248014"?

That is how winget reports the error when you install an app from the msstore source in Terminal or PowerShell. winget hands the download to the Store, and the Store hands it to the update client, which fails with 0x80248014. Fix the Store first: install pending updates (Fix 1) and reset the update components (Fix 4). Then run the same winget command again.

How do I fix 0x80248014 when WSL installs Ubuntu?

The message "An error occurred during installation. Distribution name: 'Ubuntu' Error code: 0x80248014" means WSL tried to download Ubuntu from Microsoft Store and the Store download failed. Fix the Store with Fix 1 and Fix 4, then run wsl --install again. If the Store keeps failing, check whether you can install another free app from it, because WSL will not succeed until the Store does.

Does 0x80248014 mean my Windows 10 is too old?

It can. On Microsoft Q&A a reader with Windows 10 20H2 had 0x80248014 in the Store after cache clearing, Repair and Reset, and the moderator advised an in-place upgrade. Versions older than 22H2 get no updates, and the Store and the update client drift apart. Check with winver. Windows 10 itself left support on 14 October 2025, so Windows 11 or Windows 10 22H2 with Extended Security Updates is the safe target.

Will resetting Microsoft Store delete my apps or purchases?

No. Reset deletes the Store app's own data on this PC, such as its cache and sign-in, and you sign in again afterwards. Your installed apps stay installed, and your purchases and subscriptions stay in your Microsoft account. Try Repair first, because it keeps the Store's data. Clearing the cache with wsreset does not remove apps either.

Will a network reset or another Wi-Fi network fix 0x80248014?

Rarely. The code does not report a connection problem: it says the update client has no record of the source it was asked to use. A network reset also removes VPN adapters and saved Wi-Fi settings. Try it only if the Store shows connection errors too, after Fix 1 to Fix 4.

Is error 0x80248014 a virus or a hardware fault?

No. The code is about a missing record in the Windows Update data store, not about malware or a broken part. If you want to be sure the PC is clean, run a full Microsoft Defender scan with How to scan for malware with Microsoft Defender, but no source ties this code to malware. If the PC also freezes or shows disk errors, check the drive with Check a disk for errors (chkdsk), because that is a separate problem.

I searched in another language. Is this the right page?

Yes, if your screen shows 0x80248014. Searches such as cara perbaiki, como resolver or kenapa tidak bisa update that led here ask how to fix this code. The answer is the same in every language: install pending Windows and Store updates, turn on updates for other Microsoft products, then reset the update services and their data store. The chooser table above shows where to start.