Solved Error 800B0100 for Windows 7 Update

[benepperson]

I've been unsuccessful in trying to update KB2249857 on a Windows 7 Home Premium 32bit laptop. I keep getting error 800B0100 through Windows Update.

I've tried turning off my Windows Firewall and updating again, with no change. I am not running McAfee or any other firewall program.

I have downloaded KB2249857 and tried to manually install but that fails too.

I downloaded and ran the Windows System Update and Readiness tool, so I'll attach CheckSUR.log to this post.

I also ran cmd.exe and ran sfc /scannow, and attempted to copy the log to my desktop using:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log>%userprofile%\Desktop\sfcdetails.txt

but I get the following error in cmd.exe:
"FINDSTR: Cannot open Epperson\Desktop\sfcdetails.txt"

I've tried manually opening CBS.log that is in Windows\Logs\CBS, but it tells me that "Access in denied."

Any help would be appreciated!

 

[yowanvista]

Try this http://www.sevenforums.com/tutorials/91738-windows-update-reset.html

 

[Flavius]

Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-diskdump_31bf3856ad364e35_6.1.7600.20753_none_673c9ddd11a0d70c.manifest
winsxs\manifests\x86_microsoft-windows-diskdump_31bf3856ad364e35_6.1.7600.16634_none_66c9a133f87218b7.manifest
servicing\packages\Package_1_for_KB2249857~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_1_for_KB2249857~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2249857_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2249857_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2249857~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2249857~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_1_for_KB2249857~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_1_for_KB2249857~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2249857_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2249857_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2249857~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2249857~31bf3856ad364e35~x86~~6.1.1.0.cat

These files are corrupted and you need to replace them>Before start to fix make sure you have in Control Panel>>Folder Options and make sure you have unchecked "Hide extensions for known file type" or better use any good file manager e.g Total Commander to have able to see everything independly from system settings

1.Download attached zip file to post and unapck it anywhere e.g on your desktop

this will create on your desktop Packs folder which contain two subfolders:

Packages and Manifests

2.Copy all files from Packs\Packages folder to C:\Windows\Temp\CheckSur\Servicing\Packages and all files from Packs\Manifests to C:\Windows\Temp\CheckSur\WinSxS\Manifests

3.Run Readiness Tool again
4.Install problematic update from Microsoft Download Center Microsoft Download Center(not from Windows Update)

I also ran cmd.exe and ran sfc /scannow, and attempted to copy the log to my desktop using:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log>%userprofile%\Desktop\sfcdetails.txt

but I get the following error in cmd.exe:
"FINDSTR: Cannot open Epperson\Desktop\sfcdetails.txt"

I've tried manually opening CBS.log that is in Windows\Logs\CBS, but it tells me that "Access in denied."

Many times it happen.Try to use Lock Hunter to delete CBS.log if it doesn't work too try it safe mode with command prompt (not in normal safe mode) http://www.sevenforums.com/tutorials/666-advanced-boot-options.html

and type there following command

del C:\Windows\Logs\CBS\CBS.log

if it doesn't work try it from WinRE or use any livecd e.g Ubuntu to delete CBS.log

Try this http://www.sevenforums.com/tutorials/91738-windows-update-reset.html

Out of chance here

 

[benepperson]

Thank you, Flavius! Your zip file + Readiness Tool worked great, the update successfully installed. I appreciate your help!

 

[rbtorrws]

Thank you, Flavius! Your zip file + Readiness Tool worked great, the update successfully installed. I appreciate your help!

Hi Flavius,
new forum user here with the same issue. Where can I find the attached Zip file?
Thanks a lot.

 

[Flavius]

Thank you, Flavius! Your zip file + Readiness Tool worked great, the update successfully installed. I appreciate your help!

Hi Flavius,
new forum user here with the same issue. Where can I find the attached Zip file?
Thanks a lot.

You may dispense with the pleasantries .I really bored to repeat such persons like you each case is individual an you cannot apply solution for other persons!Please run Readiness Tool,this will create CheckSur.log file in C:\Windows\Logs\CBS,attache this file to post then I'll diagnose and prepare solution special for you.

 

[bart2906]

Checksur error

Hi Flavius,

I've been trying to fix the errors I found in my checksur.log file, but without luck. I've seen your name pop up on a number of forums where you seem to correct the problem! Please could you take a look at my log file(below) and let me know if you can resolve it. Seems to be caused by MS09-34/KB972260 but I'm not sure what needs to be done to fix it.

Thanks in advance!

=================================
Checking System Update Readiness.
Binary Version 6.0.6001.22375
Package Version 5.0
2010-11-30 14:07

Checking Deployment Packages

Checking Package Manifests and catalogs.

Checking package watchlist.

Checking component watchlist.

Checking packages.

Checking component store
(f) CSI Manifest and S256H Do Not Match 0x00000000 WinSxS\Manifests\x86_4e876b781d95e0a3e16c7e6b16a473c7_31bf3856ad364e35_6.0.6002.22180_none_5548c11a70d4d272.manifest x86_4e876b781d95e0a3e16c7e6b16a473c7_31bf3856ad364e35_6.0.6002.22180_none_5548c11a70d4d272
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_e80f7e2d46b14afa9cf05655d7d0c6e4_31bf3856ad364e35_6.0.6001.22475_none_83441e46b9424efa.manifest x86_e80f7e2d46b14afa9cf05655d7d0c6e4_31bf3856ad364e35_6.0.6001.22475_none_83441e46b9424efa
Summary:
Seconds executed: 3854
Found 2 errors
CSI Manifest All Zeros Total Count: 1
CSI Manifest and S256H Do Not Match Total Count: 1

 

[niemiro]

Hi Flavius,

I've been trying to fix the errors I found in my checksur.log file, but without luck. I've seen your name pop up on a number of forums where you seem to correct the problem! Please could you take a look at my log file(below) and let me know if you can resolve it. Seems to be caused by MS09-34/KB972260 but I'm not sure what needs to be done to fix it.

Thanks in advance!

=================================
Checking System Update Readiness.
Binary Version 6.0.6001.22375
Package Version 5.0
2010-11-30 14:07

Checking Deployment Packages

Checking Package Manifests and catalogs.

Checking package watchlist.

Checking component watchlist.

Checking packages.

Checking component store
(f) CSI Manifest and S256H Do Not Match 0x00000000 WinSxS\Manifests\x86_4e876b781d95e0a3e16c7e6b16a473c7_31bf3856ad364e35_6.0.6002.22180_none_5548c11a70d4d272.manifest x86_4e876b781d95e0a3e16c7e6b16a473c7_31bf3856ad364e35_6.0.6002.22180_none_5548c11a70d4d272
(f) CSI Manifest All Zeros 0x00000000 WinSxS\Manifests\x86_e80f7e2d46b14afa9cf05655d7d0c6e4_31bf3856ad364e35_6.0.6001.22475_none_83441e46b9424efa.manifest x86_e80f7e2d46b14afa9cf05655d7d0c6e4_31bf3856ad364e35_6.0.6001.22475_none_83441e46b9424efa
Summary:
Seconds executed: 3854
Found 2 errors
CSI Manifest All Zeros Total Count: 1
CSI Manifest and S256H Do Not Match Total Count: 1

Hello!

Sorry about the delay! You now have me instead! Can I please ask you to create a new thread, to keep the forum tidy? Thanks so much!