Solved Windows Update Error code 8024800A

[Indianatone]

Windows update suddenly this month refused to run coming back with the red shield and ERROR CODE 8024800A.
I tried a few things like SCF/Scannow but nothing worked except this:

Click on Start button, navigate to Accessories and Command Prompt
or Type: cmd

Right click on cmd in start menu and select 'Run as Administrator'

Type: net stop wuauserv

Press Enter

Type: ren c:\windows\SoftwareDistribution softwaredistribution.old

Press Enter

Type: net start wuauserv

Press Enter

Type: exit

Press Enter


Now download updates.You have deleted the history of the updates so it may be a while scanning.

 

[mjbolgar]

Thank you so much! I have been struggling with my PC for 48 hours but your thread seems to have solved this problem.
I am really grateful! I am only surprised that the problem never showed up on my Asus Zenbook Ultrabook with exactly the same win7 64bit version, only on my custom built PC. At least, not so far

 

[NoelDP]

According to Windows Update error code list the error is....

Data store errors

0x8024800A WU_E_DS_UNKNOWNHANDLER The update was not processed because its update handler could not be recognized.

So it does look like it was corruption in the SD folder that caused it.

 

[Indianatone]

Noel, Here is the error log from the SD folder. Hope it is some use.

 

[NoelDP]

The only thing that sticks out there is this...

{B1631F0E-63E7-43A8-8012-08F975ED027A} 2013-03-19 15:33:36:154-0400 1 182 101 {1E56BC2A-9E63-41EA-8F55-68AA3564C7EF} 201 80242016 AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80242016: Cumulative Security Update for Internet Explorer 9 for Windows 7 (KB2809289).

for obvious reasons, the report doesn't go back beyond yesterday

 

[Perrorist]

I'm having this problem on a W7 Home Premium x64 laptop.

I followed the instructions in the first post, ran cmd as admin, stopped the service, but when I tried to rename the folder it said that access was denied, even though I didn't have Windows Update open.

What could be preventing the renaming?

 

[NoelDP]

Open a Command Prompt window and run the following command

ICACLS C:\Windows\SoftwareDistribution

post the results.

 

[Perrorist]

Open a Command Prompt window and run the following command

ICACLS C:\Windows\SoftwareDistribution

post the results.

C:\windows\softwaredistribution NT SERVICE\TrustedInstallerI)(F)
NT SERVICE\TrustedInstallerI)(CI)(IO)(F)
NT AUTHORITY\SYSTEMI)(F)
NT AUTHORITY\SYSTEMI)(OI)(CI)(IO)(F)
BUILTIN\AdministratorsI)(F)
BUILTIN\AdministratorsI)(OI)(CI)(IO)(F)
BUILTIN\UsersI)(RX)
BUILTIN\UsersI)(OI)(CI)(IO)(GR,GE)
CREATOR OWNERI)(OI)(CI)(IO)(F)

Successfully processed 1 files; Failed processing 0 files

 

[NoelDP]

That looks normal enough - when you ran NET STOP WUAUSERV did you get the proper 'service stopped' response?

 

[Perrorist]

Yes, it said stopped. I checked the processes when I saw the 'Access denied' message and didn't see it running. I'll give it another go in the morning straight after another reboot.

 

[Perrorist]

Still no joy. To make matters worse, holding down F8 to prevent Windows starting so that I can do the renaming in DOS has no effect. It's an Asus Ultrabook with an always-on style of system installation.

 

[Perrorist]

Finally... I'd been restarting Windows rather than cold booting, but I thought it was worth trying. As soon as I shut down, up came a message saying it was installing 11 updates. Why these weren't being applied before when I restarted, I've no idea.

Booted the PC and checked Windows Update. Two updates: one important and one optional. Selected them both. They were downloaded but failed to install. Message code was 8024402C. Tried again with the same result. Left it for a couple of hours in case it was a Microsoft server error (sometimes happens), then tried once more. This time it all went smoothly.

Why Microsoft couldn't identify the incomplete installs as the initial problem, and why the installs weren't completed during a restart, remains a mystery. However, all is good again.

 

[NoelDP]

Installs are never started during a restart operation - but are 'forced' during a shutdown.

Thanks for the detail - it's something I'd not considered before!