This means Windows Update looked in its local data store for information, often license terms, and it was not there. It points at a corrupt update store or a wrong clock. Jump to your situation below or work through the methods in order.
0x80248007 (WU_E_DS_NODATA) means Windows Update asked its local data store for some information, frequently the license terms for an update, and that information was not there. The usual cause is a corrupt or incomplete data store, which lives in the SoftwareDistribution folder, or a wrong system clock that breaks the license validation. Less often it follows a previous update that left the store inconsistent. The fix is to run the troubleshooter, correct the date and time, then rebuild the store by stopping the update services and clearing SoftwareDistribution and catroot2 so Windows recreates them. Running SFC and DISM afterwards repairs any deeper corruption, and the update can then read what it needs.
Windows Update keeps a local database, the data store, in the SoftwareDistribution folder. It records available updates and details like license terms. 0x80248007 means the agent asked that store for something and got nothing back, so it cannot proceed with the update.
That empty result usually means the store is corrupt or incomplete, which rebuilding fixes. It can also mean the license terms failed to validate because the system clock is wrong, since the validation is time-sensitive. So the two things to fix are the clock and the store.
“WU_E_DS_NODATA is the update reaching into its own database for the license terms and coming back empty-handed. Two things cause that in the real world: a corrupt store, or a wrong clock that makes the license check fail. So I set the time correctly, then rebuild the store by clearing SoftwareDistribution, and the agent re-downloads the catalogue and the terms it was missing. SFC and DISM afterwards just make sure nothing deeper is rotten.”
net stop wuauserv net stop bits net stop cryptsvc
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old ren %systemroot%\System32\catroot2 catroot2.old
net start wuauserv & net start bits & net start cryptsvc.DISM /Online /Cleanup-Image /RestoreHealth then SFC /scannow.0x80248007 is the update finding nothing in its own data store, so the fixes are to correct the clock, which the license check depends on, and to rebuild the store by clearing SoftwareDistribution. Run the troubleshooter first since it automates the rebuild, and use SFC and DISM to clear any deeper corruption.
If rebuilding the store and fixing the clock do not help, the data store database itself may be damaged on disk. Run chkdsk /f on the system drive to clear file-system errors, then rebuild the store again. You can also submit your error to us for a tailored fix.