Discussion:
"An error occurred while attempting to retrieve the list of applicable updates for your computer. To continue, please close and reopen the Windows Update control panel. (Error code: 80248007)"
(too old to reply)
Ant
2018-06-12 20:32:22 UTC
Permalink
Raw Message
Hello.

Why does my 64-bit W7 HPE SP1 machines say "An error occurred while
attempting to retrieve the list of applicable updates for your computer.
To continue, please close and reopen the Windows Update control panel.
(Error code: 80248007)" after manually checking for new updates for a
while and then start my downloads as shown in my uploaded
Loading Image... screen capture/shot.
It's quite annoying to retry with a long rescan and then hopefully start
a download. This had been happening for months too!

Is there a fix for it?
--
Quote of the Week: "I never kill insects. If I see ants or spiders in
the room, I pick them up and take them outside. Karma is everything."
--Holly Valance
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org
/ /\ /\ \ Please nuke ANT if replying by e-mail privately. If credit-
| |o o| | ing, then please kindly use Ant nickname and URL/link.
\ _ /
( )
Paul
2018-06-12 23:49:11 UTC
Permalink
Raw Message
Post by Ant
Hello.
Why does my 64-bit W7 HPE SP1 machines say "An error occurred while
attempting to retrieve the list of applicable updates for your computer.
To continue, please close and reopen the Windows Update control panel.
(Error code: 80248007)" after manually checking for new updates for a
while and then start my downloads as shown in my uploaded
http://screenshot.cz/7N/7NIGK/checkedw7wuerror.gif screen capture/shot.
It's quite annoying to retry with a long rescan and then hopefully start
a download. This had been happening for months too!
Is there a fix for it?
WU_E_DS_NODATA - 0x80248007 - (32775)
The information requested is not in the data store.

The information here suggests the problem can be
related to the contents of SoftwareDistribution.

https://borncity.com/win/2016/12/07/windows-10-update-error-0x80248007/

There are some scripts you can download and open
in Notepad here, which deal with various
Windows Update issues. The previous article seems
to think cleaning just Downloads is enough in this
case. This will show you all the things a complete
reset would do, for WU.

https://www.sevenforums.com/tutorials/91738-windows-update-reset.html

The Windows 7 Troubleshooting control panel should
have a Windows Update troubleshooter as well.

While fiddling with SoftwareDistribution can affect
the visual contents of Windows Update history,
the OS still knows what packages are installed.
It should still be able to compute what new
packages are needed, and so on.

If the Windows Update software is old enough,
it'll need to update itself. In some cases, you can
find numbered KB updates on the Catalog server - this
can help if you've just installed Windows 7, and need to
bring WU quickly up to scratch.

But if you've been doing WU for months, everything
should already have been dragged into a modern era,
and that probably isn't the problem.

Paul
VanguardLH
2018-06-13 03:28:14 UTC
Permalink
Raw Message
Post by Ant
Why does my 64-bit W7 HPE SP1 machines say "An error occurred while
attempting to retrieve the list of applicable updates for your computer.
To continue, please close and reopen the Windows Update control panel.
(Error code: 80248007)" after manually checking for new updates for a
while and then start my downloads as shown in my uploaded
http://screenshot.cz/7N/7NIGK/checkedw7wuerror.gif screen capture/shot.
It's quite annoying to retry with a long rescan and then hopefully start
a download. This had been happening for months too!
Is there a fix for it?
Quite often deleting the local update cache (aka catalog) solves those
problems. The client then has to query the online manifest and build a
new catalog.

https://www.google.com/search?q=windows%207%20rebuild%20update%20catalog

Sometimes an update that requires a reboot to replace its new files
against the inuse/locked files; however, the update doesn't force a
reboot which leaves it in a limbo state that can screw up other updates
dependent on that update. Despite an update not indicating a reboot is
required, I always reboot after an update. If there are a dozen updates
available, I pick maybe 3 or 4, apply them, reboot, and pick a few more.
Installing a slew of updates too often fails due to dependencies and
files yet pending to get replaced on a reboot.

Loading...