0x80240022 update fails - how I fixed it

[Guest]

Just downloaded the xp64 version and tried it. It failed on updates with the
usual 0x80240022 "wrong diskette" error.

Tried the MSI / Bits / WinInstaller fixes, all with no dice. Tried the
Windows Update via browser, no dice.

I'm behind an ISA2004 firewall, if that's any use. Anyway, I checked out the
%WINDIR%\WindowsUpdate.log and saw this line in it:

2006-06-07 17:43:55 136 54c DnldMgr * Downloading from
http://www.download.windowsupdate.c..._c1dd49a32850fbf5a57ed0010463fa7ae975ab31.exe
to
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\e4b60bcfb42763b5961f316a02a7d96e\c1dd49a32850fbf5a57ed0010463fa7ae975ab31 (full file).

So, via my browser I downlaoded the mpas-xxxxx.exe file manually, and ran
it. It updated my definitions. Automatic checking of updates now works.

Hope this helps someone out.

AW

 

[Bill Sanderson MVP]

Thanks - Do you know whether your firewall is set to require authentication
for clients using it? If it is, my understanding is that updates within
Windows Defender won't work---this means that AutoUpdate is probably also
not working on your system.

However, manually going to Windows Update should work--as will doing the
trick you tried. This is because those mechanisms work through the HTTP
proxy in your firewall.

There is a workaround which your system admin can implement: Allow
connections without authentication only to the Windows Update servers.

 

[Larry Gardner]

It sounds like your SoftwareDistribution log files are out of wack. There
is a Datastore.edb file in the DataStore directory that maintains what has
been downloaded and installed on your system.

If you remove the SoftwareDistribution tree, Windows will re-create
everything at next download.

HOWEVER ***************************

This will also remove your Microsoft Update History information, so the next
time you try to review you Update History on the Microsoft Update site,
there will not be anything there except for downloads AFTER you reset the
SoftwareDistribution folder under C:\Windows.

To re-sync:

1. You must Stop the Automatic Update Service and BITS services in
Administrative | Services
2. Remove the C:\Windows\SoftwareDistribution folder (or rename it and
remove later)
3. Start Automatic Updates and BITS Services in Administrative | Services
4. Click on Windows Update or Microsoft Update and select Custom

Do whatever you need to do.

 

[Guest]

Hi Bill

We are using built in domain authentication for clients. The option for
unauthenticated clients to windows update servers sounds interesting however,
and I'll look that up.

While running Windows Update didnt' work and my 'trick' did, ever since I
applied that update manually the update (when selected through the
application) is working. I've tested this again and verified it to be the
case. As you say, auto-update (as per the Automatic Updates service, or
Windows Defender service?) don't appear to be happening. This has always been
the case.

As you say, an exception in the firewall may be worth investigating.

Thanks

AW

 

[Bill Sanderson MVP]

Rereading the thread, I do wonder whether AutoUpdate and Windows Update are
restricted on your network to an in house update mechanism--SMS, SUS, WSUS,
or a third-party solution?

One way to see that would be to attempt an update (help, about, check for
updates), note the time and then:

start, run,

notepad %windir%\windowsupdate.log

scroll to the end of the log and then highlight back up to the beginning of
that attempted update, and cut and paste to this thread. One detail to look
for are lines with the word "server" in them showing what server is being
connected to.

--