Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x80248007

0x80248007 and 0x80248014: the Windows Update datastore is damaged

12 min read Updated October 5, 2026 Windows Update & Setup

Fix it now

0x80248007 is WU_E_DS_NODATA: the information requested is not in the data store. 0x80248014 is WU_E_DS_UNKNOWNSERVICE: an operation did not complete because the service is not in the data store. Both come from the agent’s own local database, not from Microsoft’s servers and not from the update you are installing.

Run these in an elevated Command Prompt, in order. All three services must be stopped before the renames

net stop wuauserv
net stop bits
net stop cryptsvc
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start cryptsvc
net start bits
net start wuauserv
  1. Check for updates. The first scan is slow because the database is being rebuilt from nothing; let it finish.
  2. If a rename is refused, restart the machine and do it before anything else has started.
  3. If 0x80248014 comes back, the client is being told to use an update service it has no record of. Read WUServer and WUStatusServer under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate and check the server named there still exists.
  4. Correct or remove that policy through Group Policy rather than the registry, run gpupdate /force, restart the update service and rescan.

Renaming SoftwareDistribution discards the update history shown in Settings. It uninstalls nothing: installed packages live in the component store.

If a scan completes and lists updates, you are finished. If the same codes return, the next section separates a damaged database from a missing service registration.

Why it happens

The Windows Update agent does not go back to the service for everything it knows. It caches metadata locally in an Extensible Storage Engine database, DataStore.edb, which lives under C:\Windows\SoftwareDistribution\DataStore alongside its transaction logs. Every scan writes into it: update identities, applicability results, download state, and the identity of each update service the client is registered against. It is an ordinary database file with ordinary database failure modes.

0x80248007 is the agent asking the store for something and being told the information is not there. That happens when the database was truncated, when a cleanup tool deleted files underneath a running service, or when a scan wrote a partial result and never committed it. 0x80248014 is narrower and more useful: the agent was handed a service identifier, went to look it up, and found the service is not in the data store. That is what you get after a WSUS server is decommissioned while its registration is still referenced, or after a management tool adds an update service and removes it badly.

The 0x8024D0xx codes sit one layer up, in the agent’s own setup. Before scanning, the agent checks whether it needs to update itself. 0x8024D007 is WU_E_SETUP_REGISTRATION_FAILED: the agent could not be updated because regsvr32.exe returned an error. 0x8024D009 is WU_E_SETUP_SKIP_UPDATE, an update to the agent skipped because of a directive in the wuident.cab file, which is a normal outcome rather than a fault. They tend to appear immediately before the data store errors, because a half-updated agent and a damaged store usually arrive together.

0x80248011 is WU_E_DS_UNABLETOSTART, and its published wording is precise: could not create a data store object in another process. That is not the same as the requesting process being unable to open the store, which is how it is usually paraphrased. 0x8024D008 is not in Microsoft’s Windows Update Agent setup table at all; that table runs from 0x8024D001 to 0x8024D013 and omits this value. Treat it as an agent setup failure and diagnose from the codes around it.

DataStore.edb is damaged or truncated

You have this one if 0x80248007 on every scan, and the failure happens too fast for any network request to have been made.

  1. Stop wuauserv, bits and cryptsvc from an elevated prompt.
  2. Rename C:\Windows\SoftwareDistribution rather than deleting it, so you can put it back if something else was relying on a cached download.
  3. Rename C:\Windows\System32\catroot2 as well; the catalogue store and the update store go wrong together often enough to be worth doing both.
  4. Start the three services, run a scan, and let it finish even if it takes several minutes.

Renaming the folder discards your update history in Settings. It does not uninstall anything and it does not affect activation.

The client references an update service it has no record of

You have this one if 0x80248014, usually on a managed machine, and often after a WSUS server was retired or a co-management tool was removed.

  1. Read WUServer and WUStatusServer under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate and check whether that server still exists.
  2. Correct the ‘Specify intranet Microsoft update service location’ policy under Computer Configuration – Administrative Templates – Windows Components – Windows Update, or remove it if the machine should no longer be managed.
  3. Run gpupdate /force, restart wuauserv and rescan.
  4. Reset the local store afterwards so the stale registration is not carried forward.

The agent could not refresh its own components

You have this one if 0x8024D007 or 0x8024D009 in the log before the data store error, and the failure repeats identically after a restart.

  1. Run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, and restart before retrying. A damaged component store stops the agent registering its own binaries.
  2. Reset the agent’s stored state by renaming SoftwareDistribution as above.
  3. Generate a readable log with Get-WindowsUpdateLog and confirm the setup entries have stopped failing.
  4. Remember 0x8024D009 on its own is a skip directed by wuident.cab, not a failure to fix.

The store cannot be created or opened at all

You have this one if 0x80248011, or errors that clear temporarily after a restart and return within a day.

  1. Check free space on the system volume. The database needs room for its transaction logs, and a volume with almost nothing left produces exactly this behaviour.
  2. Confirm no backup or endpoint protection product is holding files under SoftwareDistribution open, and exclude the folder from real-time scanning if the product supports it.
  3. Check the permissions on the folder. If a hardening baseline has tightened them, the safest repair is to rename it and let Windows recreate it with correct permissions.
  4. Run chkdsk C: /scan and read the result before assuming the file is at fault rather than the disk.

The same corruption returns every few weeks

You have this one if Resetting the store works, and the machine is back in the same state a fortnight later.

  1. Look at what runs on a schedule: disk cleanup scripts, third-party optimiser tools, backup agents.
  2. Exclude the SoftwareDistribution folder from anything that prunes files by age or size.
  3. Check the disk’s own health reporting before resetting the store a third time.
  4. If the machine is a virtual desktop rebuilt from an image, fix the image rather than the instance.

Full reference

Reading the symptom to find the layer

What you see Where the fault is
The scan fails within seconds, with no network traffic at all The local store cannot be read
The scan fails only against WSUS and works against Microsoft Update A service registration the store has no record of
The DataStore folder is empty after a disk cleanup The database was deleted while the service held it open
Get-WindowsUpdateLog shows agent setup entries before the failure The agent could not refresh its own components
Errors clear after a restart and return within a day Free space, permissions, or something holding the folder open

The six codes, with their published wording

Code Published name Reading
0x80248007 WU_E_DS_NODATA The information requested is not in the data store
0x80248014 WU_E_DS_UNKNOWNSERVICE An operation did not complete because the service is not in the data store
0x8024D007 WU_E_SETUP_REGISTRATION_FAILED The agent could not be updated because regsvr32.exe returned an error
0x8024D009 WU_E_SETUP_SKIP_UPDATE An agent update was skipped due to a directive in the wuident.cab file
0x80248011 WU_E_DS_UNABLETOSTART Could not create a data store object in another process
0x8024D008 Not published Absent from Microsoft’s agent setup table, which runs 0x8024D001 to 0x8024D013

The commands this article uses

Command What it does
net stop wuauserv Stops the update service so the data store can be renamed
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old Forces Windows to rebuild the update database and download cache
Get-WindowsUpdateLog Merges the agent’s .etl trace files into a single readable log, written to the current user’s Desktop by default
DISM /Online /Cleanup-Image /RestoreHealth Repairs the component store the update agent depends on
chkdsk C: /scan Runs an online scan on an NTFS volume, without a dismount
gpupdate /force Reapplies policy after correcting an update server setting

Repointing a client at the right update service

When 0x80248014 keeps returning, the machine is being told to use a service it cannot find. Fix that through policy rather than through the agent’s COM interfaces. The ‘Specify intranet Microsoft update service location’ policy writes WUServer and WUStatusServer under the Policies branch, and UseWUServer under its AU subkey decides whether Automatic Updates honours them. Remove the policy to return a machine to Microsoft’s own update service, correct it to point at a server that exists, and reset the local store afterwards so the stale registration is not carried forward.

Avoid recipes that re-register the update service by calling AddService2 with a hard-coded service identifier, or that re-register agent DLLs with regsvr32. Microsoft does not publish that identifier, and the DLL set differs between builds. Component store repair followed by a store rebuild covers the same ground with documented commands.

Where to look when the reset does not hold

  • Get-WindowsUpdateLog produces WindowsUpdate.log on your Desktop. Read the newest entries for the stage that failed rather than guessing from the code.
  • Event Viewer under Applications and Services Logs – Microsoft – Windows – WindowsUpdateClient – Operational records scan outcomes.
  • Check free space on the system volume, because the data store needs room for transaction logs.
  • Check whether the folder’s permissions were changed by a hardening baseline. Renaming and letting Windows recreate it restores the correct ones.
  • If the machine is one of many built from the same image, expect the same fault on all of them, and fix the image.

Every code this article covers

Code What it points at Source
0x80248007 WU_E_DS_NODATA: the information requested is not in the data store Microsoft Learn
0x80248014 WU_E_DS_UNKNOWNSERVICE: an operation did not complete because the service is not in the data store Microsoft Learn
0x8024D007 WU_E_SETUP_REGISTRATION_FAILED: the Windows Update Agent could not be updated because regsvr32.exe returned an error Microsoft Learn
0x8024D009 WU_E_SETUP_SKIP_UPDATE: an update to the Windows Update Agent was skipped due to a directive in the wuident.cab file Microsoft Learn
0x80248011 WU_E_DS_UNABLETOSTART: could not create a data store object in another process Microsoft Learn
0x8024D008 Seen in the agent’s setup stage alongside the codes above. Microsoft’s Windows Update Agent setup table runs from 0x8024D001 to 0x8024D013 and omits this value, so diagnose from the surrounding codes and the update log not published by the vendor

Confirm the fix worked

  1. Run a scan from Settings and confirm it completes and lists updates rather than failing with a code.
  2. Confirm C:\Windows\SoftwareDistribution\DataStore exists again with a freshly dated DataStore.edb.
  3. Run Get-WindowsUpdateLog and check the newest entries show a completed scan with no data store errors.
  4. Check Applications and Services Logs – Microsoft – Windows – WindowsUpdateClient – Operational for a successful scan event.
  5. On a managed client, confirm it reports into the update server with a current last-contact time.

Questions people ask about this

Does fixing this cost anything?

No. This is a local database repair and every step uses tools already in Windows. There is no licence, product or subscription that fixes a damaged update data store.

Is it safe to delete SoftwareDistribution instead of renaming it?

It works, but rename it. If the machine had a large feature update part-downloaded, renaming lets you recover it, and if something unrelated turns out to have been the problem you can put the folder back.

Will I lose my update history?

The list in Settings, yes. The updates themselves stay installed, because installed packages live in the component store, not in the data store. Get-HotFix and Installed Updates in Control Panel still show what is on the machine.

What does 0x8024D008 mean?

Microsoft does not publish a meaning for it. The Windows Update Agent setup table runs from 0x8024D001 to 0x8024D013 and this value is not in it. Treat it as a failure in the agent’s own setup stage and diagnose from the codes and log entries around it rather than from this one.

Why does this keep coming back on the same machine?

Recurring corruption usually means something is writing into the folder or holding it open. Look at disk cleanup scripts, third-party optimiser tools, backup agents and endpoint protection before you reset the store a third time.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix 0x80072EE2 and 0x80072EFD: Windows Update times out reaching Microsoft Free Fix 0x80D01001: Delivery Optimization cannot provide the download service Free Fix 0x80242006 and 0x80240022: update handler and post-reboot install failures Free Fix 0x80245001 and 0x80245003: the update redirector cab cannot be used
โ† Back to Knowledge Base