Post by Mike S Post by B00ze Post by Debbie
"WindowsUpdate_8024200D" "WindowsUpdate_dt000". Suggestions?
Have a look at "C:\Windows\WindowsUpdate.log" you might find out what
8024200D means. Google might help, but I get 26000 results, find the 1
site that knows that 8024200D means will be difficult, better to check
the log first.
This might help
At one time, somebody posted that the errors were in a header
file (something you might find in Visual Studio), but this
article implies you have to look underneath some rocks to find it.
The update handler did not install the update because
it needs to be downloaded again.
And that, unfortunately, is the equivalent of "Oops! Something went wrong".
The message should not be taken at face value. Updates are verified
by signature or checksum, and really should have been verified during
the BITS stage. To get that message later, implies Windows Update
has discovered the file is the wrong one, isn't needed, or some other
How I would attack this one, is:
1) Look in the Windows Update history tab.
When a KB records a "Success" after a "Failure", that's OK.
So if it said "Failed KB12345678 June10,2017" then
"Succeeded KB12344567 June11,2017", those cancel out and we
know that item was successfully installed and we move on.
It's when the history shows a stackup of Failed, one after
another, you have to look back at the KB numbers involved.
Failed KB4000003 <--- The others are "innocent victims"
Failed KB4000001 <--- Plumbing is jammed here
When this happens, I make a list of all the failed updates,
their KB numbers, and go here and manually download a .msu for
I install the updates, one by one, until I've done all the
failed ones in the stack.
Then I can try Windows Update again if I want.
Say I was just plain lazy, I might install 4000001 manually.
Then reboot the computer, and run Windows Update again. Maybe
it will look like this after Windows Update is finished, and the
plumbing jam is cleared.
Success KB4000003 <--- These installed themselves, because jam-up is gone
Success KB4000001 <--- I installed this manually
2) Sometimes, Windows Update needs to be reset. This isn't technically
as impressive as it sounds. The easiest way to do this, is
rename SoftwareDistribution to Softwaredistribution.bak or similar.
When the folder is renamed, Windows Update will make a fresh one.
By being that "violent", you lose the History listing. That's
why you want to do step (1) first. I usually smack around my
Win10 Insider Edition like that, because the update history in it
is not important. Whereas, for real OSes, you should use that approach
as a last step.
Instead, we look for an article, with scripts to run. Some of these
have "graduated violence". There's a "weaker" reset and a "stronger"
reset. You can try the weakest flavor first.
Maybe Option 2 would be a place to start.
"It will reset Windows Update Components and re-register the
BITS files and the Windows Update files to help fix
Windows Update errors.
This option will not clear the view update history details
list as it does in OPTION ONE above.
To use that, you need to know how to run a batch file in
an Administrator Command Prompt window.
# In Win7, type "cmd" in the start, right-click
# on the top-most item in the returned list, then select "Run As Administrator"
# from the right-click menu. A Command Prompt window opens, where
# the working directory is set to system32. You need to change the
# working directory to a more useful location, using the "cd"
# change directory command.
cd /d C:\path\to\where\you\normally\download\stuff
# My favorite way of getting to my downloads is this way...
# Your mileage may vary of course.
After you've done that, try a reboot. That's to ensure
all the services are in a good state, for your next
Windows Update attempt. The script does actually shut down
and start up the services properly, so you might say a
reboot is overkill, but rebooting is "belt and suspenders".
And it's Windows Update. If it wasn't broken, we wouldn't
be having any fun.