Moving Green Screen-Of-Death (AKA “Searching for Updates”
) - For those who recall the long popular MS-BSOD.

Foolishly this morning thought that I should update WinXP. I thought it
might not go well when was greeted with the “We have improved Win Updater”
msg. This foreboding proved correct. It is now two and a half hours later and
have not succeeded.

The first error was 7000B. The suggested manual download solved that.

Then kept getting stuck on the MGSOD (Express OR custom). Found a way around
that by running the Automatic Update WinXP service – which seems to bypass
that and finds the updates. Sadly, trying to download the found updates this
brought me to error 8024001D.

I then ran the batch file to register the dlls: wuapi.dll, wuaueng.dll,
wucltui.dll, wups.dll, msxml3.dll and NOW find myself getting error 80072EE2.

Yes, use ZoneAlert. No, it is not running.

Here is the last bit of Install’s log culminating in the MOST RECENT failure:
++++
951A-99EE9C246A94}.101 has no local extended metadata. Not returning it.
2005-11-25 07:16:20 1660 36c Agent Update
{E0A7FC7E-FF6E-4559-990B-4B4A01F0AD39}.100 has no local extended metadata.
Not returning it.
2005-11-25 07:16:20 1660 36c Agent Update
{B00FE76D-8C87-48A2-9D5D-FD2D1336698C}.100 has no local extended metadata.
Not returning it.
2005-11-25 07:16:20 1660 36c Agent Update
{B5503E2C-ADAF-494B-B3F7-15E893F84273}.100 has no local extended metadata.
Not returning it.
2005-11-25 07:16:20 1660 36c Agent Update
{6E9B9E79-E08A-44C5-8D3F-250C33A48967}.100 has no local extended metadata.
Not returning it.
2005-11-25 07:16:20 1660 36c Agent Update
{6D5B814E-201C-4F9B-965A-6672F85CEB9A}.101 has no local extended metadata.
Not returning it.
2005-11-25 07:16:20 1660 36c Agent Update
{56A3ECF6-DFFC-43E1-A17A-F37BA2D52474}.101 has no local extended metadata.
Not returning it.
2005-11-25 07:16:20 1660 36c Agent * Found 0 updates and 0 categories in
search
2005-11-25 07:16:20 1660 36c Agent *********
2005-11-25 07:16:20 1660 36c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-11-25 07:16:20 1660 36c Agent *************
2005-11-25 07:16:20 1660 36c AU >>## RESUMED ## AU: Search for updates
[CallId = {9AF91367-64F0-479D-AF63-C5FD57CE885B}]
2005-11-25 07:16:20 1660 36c AU # 0 updates detected
2005-11-25 07:16:20 1660 36c AU #########
2005-11-25 07:16:20 1660 36c AU ## END ## AU: Search for updates [CallId
= {9AF91367-64F0-479D-AF63-C5FD57CE885B}]
2005-11-25 07:16:20 1660 36c AU #############
2005-11-25 07:16:25 1660 36c Report REPORT EVENT:
{9EBDFB9C-152E-4F53-B41B-36EAE4C22F17} 2005-11-25
07:16:20-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2 WindowsUpdate Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80072ee2

Trying to "UpDate" by creating a new admin account gives YET ANOTHER Error:
8024001D

This all reminds me of a few years ago when was unable to update W2K for
about a year as could not download the updated updater.

Of course, it is especially irritating as most of the 'updates' are to fix
exploit holes in WinX ...

UNIX wrote:

> Trying to "UpDate" by creating a new admin account gives YET ANOTHER Error:
> 8024001D
>
> This all reminds me of a few years ago when was unable to update W2K for
> about a year as could not download the updated updater.
>
> Of course, it is especially irritating as most of the 'updates' are to fix
> exploit holes in WinX ...
Hi,

Rename (or just delete) the SoftwareDistribution folder and
see if it helps.

You can use the procedure described here:

http://v5.windowsupdate.microsoft.co...cleid=21&ln=en

Note that a side effect of renaming or deleting the
SoftwareDistribution folder is that you lose your Windows Update
History listing (not critical).

(later on, you can just delete the renamed SoftwareDistribution
folder)




--
torgeir, Microsoft MVP Scripting, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx