[SOLVED] Security Update (KB2984972) Failed--Error Code 800B0100 - Encountered unknown error

Cowboyjake

Contributor
Joined
Oct 15, 2014
Posts
100
I'm running a laptop with Windows 7 Home Premium, Service Pack 1, 64 bit operating system. This morning received notice of 17 Microsoft update. I proceeded to install them. All but one installed. I have restarted my computer at least 2 or 3 time since the initial failure.

I have tried three times to install Security Update for Windows 7 for x64-based Systems (KB2984972) and each time it has failed. Microsoft has identified this as an important update.

I ran SFCFix version 2.4.1.0 and it said that it found no errors. Gif of text file attached.

I am also attaching the CBS.zip log (to come-must be large file) in an effort that someone can give me advice on how to proceed with getting this security fix installed. Any advice will be greatly appreciated. This is the first time I have had an update fail. Thank you.

View attachment SFCFix.txt
 

Attachments

  • SFCFix.txt.gif
    SFCFix.txt.gif
    17.7 KB · Views: 2
Last edited:
Hello and welcome to the forum.

Please follow the instructions Here to run the System Update Readiness Tool. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
C:\Windows\Logs\CBS\CheckSUR.log
C:\Windows\Logs\CBS\CheckSUR.persist.log
 
Hello and welcome to the forum.

Please follow the instructions Here to run the System Update Readiness Tool. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
C:\Windows\Logs\CBS\CheckSUR.log
C:\Windows\Logs\CBS\CheckSUR.persist.log
Tried doing that tonight. After an hour I noticed that it had reached about 85% complete but wasn't gaining any ground from there. An hour later it had not moved and appeared to be stuck, I tried to cancel the operation. I finally had to use the Task Manager to stop it. I'm tired so I'll try it again tomorrow and hopefully be able to post results. Thanks for the help.
 
No worries. If it fails again can you please check to see if the above logs were created. If they were please post the contents back here.

Alex
 
Worked fine today. Here are the results. Thanks.

CheckSUR.log:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-10-17 12:19

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 2547
No errors detected


CheckSUR.persist.log:


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-10-16 19:44

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Payload File Missing 0x00000000 Microsoft-Windows-IE-HTMLRendering.ptxml amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18170_none_8bde6032afff6529
(fix) CSI Payload File Missing CSI File Replaced File: Microsoft-Windows-IE-HTMLRendering.ptxml From: C:\Windows\winsxs\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7600.16385_none_89f24b7ab2dc7a40\Microsoft-Windows-IE-HTMLRendering.ptxml
(f) CSI Payload File Missing 0x00000000 wow64_Microsoft-Windows-IE-HTMLRendering.ptxml wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18170_none_96330a84e4602724
(fix) CSI Payload File Missing CSI File Replaced File: wow64_Microsoft-Windows-IE-HTMLRendering.ptxml From: C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7600.16385_none_9446f5cce73d3c3b\wow64_Microsoft-Windows-IE-HTMLRendering.ptxml

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-10-17 12:19

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 2547
No errors detected
 
Results from 2014-10-17 12:19 (Most recent scan) are not showing any more corruptions, the scan from the day before 2014-10-16 19:44 fixed 2 corruptions. How are Windows updates behaving now?
 
Results from 2014-10-17 12:19 (Most recent scan) are not showing any more corruptions, the scan from the day before 2014-10-16 19:44 fixed 2 corruptions. How are Windows updates behaving now?
After I received your message I tried to install the remaining update and it failed again giving me the same error message.
 
That's normal from time to time, this should fix it.

Software Distribution rename

  • Click Start -> Type in CMD in the search -> Right click on cmd.exe and choose Run as Administrator
  • Entre in the following commands:
    net stop wuauserv
    ren %SystemRoot%\SoftwareDistribution\Download DL.bak
    ren %SystemRoot%\SoftwareDistribution\DataStore DS.bak
    net start wuauserv

Once completed please try and run windows update again.
 
Followed instructions by doing a copy and paste of the commands to make sure it was correct and got a syntax error. I've attached a copy of the screen.
 

Attachments

  • CMD Message.jpg
    CMD Message.jpg
    17.6 KB · Views: 6
Duh! I should have realized that. Guess I wasn't thinking.

Did it and I was able to install the update. Thanks for the help. Can you explain to me what running that code did to fix the problem? I'm nosey that way. I learn from doing so I would like to know what I just did. Thanks.
 
Did it and I was able to install the update. Thanks for the help. Can you explain to me what running that code did to fix the problem? I'm nosey that way. I learn from doing so I would like to know what I just did. Thanks.

Sure.

Just a little background first...

When you open up Windows Update and there is a message that new updates are available the first thing that needs to be done is for Windows to download the files, once the files have been downloaded WU needs to extract the updates in order to install them. Now when WU is performing these tasks the download and the extracts of the downloads get stored inside %SystemRoot%\SoftwareDistribution\ (C:\Windows\SoftwareDistribution). The error message that was being detected was 0x800B0100 means a corrupt file is present and that is stopping WU from installing any updates. What we did before was repair all the corrupt Windows update files inside the location of where the Windows Update packages are stored (C:\Windows\Servicing\Packages) once installed successfully, we did this when running SURT. Now that we know all packages are fixed that live inside C:\Windows\Servicing\Packages we know that the corruption is not with these files.

When SURT does a scan for corrupt WU files it doesn't look inside C:\Windows\SoftwareDistribution as the directory is pretty much a Temporary file location before the WU is installed. This means that the error detected by WU must be inside the temporary location (C:\Windows\SoftwareDistribution) as the Windows update store (C:\Windows\Servicing\Packages) is no longer showing any corrupt files.

What the first command did net stop wuauserv was stop the Windows Update service from running, if the service is still in use it will block the other commands from being executed.

The following commands,
ren %SystemRoot%\SoftwareDistribution\Download DL.bak
ren %SystemRoot%\SoftwareDistribution\DataStore DS.bak

Renamed two of the temporary locations WU uses to install its updates, what this does is it will force WU to download and installed the files again, hopefully they won't get corrupt again. Remember how I said before that the wuauserv had to be stopped otherwise the further commands will not work? If wuauserv was not stopped this service would of stopped the rename of both these files, because the service would of 'locked' both of the folders from being renamed as it was currently using these folders. Here is what the command line was doing in a bit more detail:
ren %SystemRoot%\SoftwareDistribution\Download DL.bak
ren {Location of original file/folder} {What you want to call the file/folder}

ren is the command to rename a file or folder.
%SystemRoot%\SoftwareDistribution\Download is the path of where the folder is located originally.
DL.bak is what I want to call the folder once the rename has been done.

The Last command net start wuauserv was just starting the service again.

hope this helps.

Alex
 
Alex:

Very understandable. I appreciate your help very much. I made a very small donation as I am on a fixed income and due to health reasons, cannot work anymore. It blows me away that you were able to help me work thru the issue. Now if tech support for a new backup program I'm dealing with would be as helpful...sigh. Thanks again.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top