Windows · Windows Server  ·  low  ·  Windows Update & servicing

0x80248007 — the update datastore is damaged

Windows Update's own database has no record where it expects one, usually because the datastore file is corrupt or a licence term was never accepted.

What you see

Scanning for updates fails immediately with 0x80248007. The message sometimes mentions missing licence terms, which is misleading in most cases.

What is actually wrong

DataStore.edb under SoftwareDistribution is corrupt. Occasionally the Windows Installer service is not running, which produces the same code.

Codes and articles

0x8024800780248007WU_E_DS_NODATA

The fix

Rebuild the update datastore
Elevated PowerShell15 minuteslow riskreversible

Scans fail with this code. Rebuilding loses the update history, not the installed updates.

  1. Confirm the Windows Installer service can start — this alone fixes a minority of cases.

    PowerShell
    Set-Service msiserver -StartupType ManualStart-Service msiserverGet-Service msiserver | Format-Table Name, Status, StartType
  2. Stop the update services.

    PowerShell
    Stop-Service wuauserv, bits, cryptsvc -Force
  3. Rename the datastore rather than deleting it.

    PowerShell
    Rename-Item C:\Windows\SoftwareDistribution\DataStore DataStore.old

    Renaming keeps a copy in case the machine is under an audit that needs the update history, and costs nothing.

  4. Start the services and force a fresh scan.

    PowerShell
    Start-Service cryptsvc, bits, wuauservUSOClient.exe StartScan
  5. The first scan rebuilds the database and is noticeably slower than usual.

Confirm it workedA scan completes and updates are listed.
PowerShell
Get-Service wuauserv | Format-Table Name, Status
If you need to undo itStop the services, delete the new DataStore folder and rename DataStore.old back.

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.