Solved Errorcode 800B0100 when trying to install SP1 for Win 7

[GudrunSchyman]

Yesterday I made a fresh installation of Win 7 Ultimate because of previous errors and bluescreens. After updating Windows Updates for a while i started to get errors again. I can't install anymore updates since they are all giving me errors when trying to download. These are the windows updates that i can't download. I have also attached my CBS logs if it helps. I have done SURT and SFC scan. I am getting errorcode 800B0100 and 8007065E.

Thanks in advance

Cumulative Security Update for Internet Explorer 8 for Windows 7 for x64-based Systems (KB2817183)

Security Update for Windows 7 for x64-based Systems (KB2483614)

Security Update for Windows 7 for x64-based Systems (KB2659262)

Security Update for Windows 7 for x64-based Systems (KB2705219)

Security Update for Windows 7 for x64-based Systems (KB974571)

Update for Internet Explorer 8 Compatibility View List for Windows 7 for x64-based Systems (KB2598845)

Update for Windows 7 for x64-based Systems (KB2506928)

Update for Windows 7 for x64-based Systems (KB2761217)

Update for Windows 7 for x64-based Systems (KB2762895)

Windows 7 Service Pack 1 for x64-based Systems (KB976932)

Windows Internet Explorer 9 for Windows 7 for x64-based Systems

 

[NoelDP]

Here's the list of problem files from the CheckSUR...

Unavailable repair files:
 winsxs\manifests\x86_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7600.21028_none_bc4d84a2222a1af5.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7600.21028_none_186c2025da878c2b.manifest
 winsxs\manifests\x86_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7600.16865_none_bb95cf27092f6ba8.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7600.16865_none_17b46aaac18cdcde.manifest
 winsxs\manifests\x86_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7601.17667_none_bd7e2cc106540a42.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7601.17667_none_199cc844beb17b78.manifest
 winsxs\manifests\x86_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7601.21789_none_bdf42a481f80149c.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-iecompat_31bf3856ad364e35_8.0.7601.21789_none_1a12c5cbd7dd85d2.manifest
 servicing\packages\Package_1_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_3_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_3_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2598845_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2598845_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2598845_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2598845_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2598845~31bf3856ad364e35~amd64~~6.1.1.0.cat

There's also a different problem showing in the SFC results...

 Line 13111: 2013-09-16 21:01:18, Info                  CSI    000002fb [SR] Repairing 1 components
 Line 13112: 2013-09-16 21:01:18, Info                  CSI    000002fc [SR] Beginning Verify and Repair transaction
 Line 13115: 2013-09-16 21:01:18, Info                  CSI    000002fe [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

We'll start by using the CheckSUR data, and repairing that - I'll post a fix protocol a bit later.

 

[NoelDP]

I've uploaded afile - gsnaa.zip - to my SkyDrive at Noel's SkyDrive

Please downloadand save it.

Right-click onthe downloaded file, and select Extract all…

Extract to thedefault location - which will create a new folder gsnaain the same place.

Open this folder- there should be two folders inside it (Manifests,and Packages)



Copy the content of the Packages folder to thefolder

C:\Windows\Temp\CheckSur\Servicing\Packages



Andthe content of the manifestsfolder (.manifest files) into this folder:



C:\Windows\Temp\CheckSur\Winsxs\Manifests



Nowrun the CheckSUR tool again (it may take a while)



Postthe new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[GudrunSchyman]

Here is the new log. Thank you for helping me fix this.

 

[NoelDP]

Great - CheckSUR is now happy

Please run another SFC /SCANNOW and post the new CBS.log file, then we'll fix any errors it still finds.

 

[GudrunSchyman]

CBSlog.

 

[NoelDP]

Just the one error there - I'll post a fix for it later.

Line 3426: 2013-09-17 18:31:08, Info                  CSI    000002fb [SR] Repairing 1 components
 Line 3427: 2013-09-17 18:31:08, Info                  CSI    000002fc [SR] Beginning Verify and Repair transaction
 Line 3430: 2013-09-17 18:31:08, Info                  CSI    000002fe [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

 

[GudrunSchyman]

Thanks so much for the help. You made my week.

 

[GudrunSchyman]

Tried to update windows again. Might not have been a good idea, got errors again. Which log should i post?

 

[NoelDP]

Nothing yet - I'll post the fix protocol for that file error on a few minutes (got sidetracked last night)

 

[NoelDP]

I've uploaded a file - gsnab.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print theseinstructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, starttapping F8 - this should bring up the Advanced Boot Menu, at the top of whichshould be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\gsnab
hit the enter key - if you get a 'NotFound' error try
DIR D:\gsnab
or
DIR E:\gsnab



The drive letter in use when you find the folder willneed to be substituted (for<drive>) into the followingcommand...



XCOPY<drive>:\gsnab <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time)andwhen the prompt returns, type
EXIT
and hit the Enter key to exit CommandPrompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in anElevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[GudrunSchyman]

Apperently you got sidetracked again ^^

 

[NoelDP]

Yeah - comes of having three jobs and a hobby

 

[GudrunSchyman]

Take your time

 

[NoelDP]

The file should be up??

 

[GudrunSchyman]

Oh, saw it now. Will do this and get back to you.

 

[GudrunSchyman]

The CBSlog.

 

[NoelDP]

Hmmm- there's now a different error in the SFC....

 Line 68892: 2013-09-18 23:01:56, Info                  CSI    0000043f [SR] Repairing 1 components
 Line 68893: 2013-09-18 23:01:56, Info                  CSI    00000440 [SR] Beginning Verify and Repair transaction
 Line 68896: 2013-09-18 23:01:56, Info                  CSI    00000442 [SR] Cannot repair member file [l:36{18}]"Pretty_Peacock.jpg" of Microsoft-Windows-TabletPC-Journal, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

- although that shouldn't affect the ability to update, I'll post a fix for it in a few minutes, while you do a new manual Check for Updates, and see what WU has to say.

 

[NoelDP]

I've uploaded a file - gsnac.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\gsnac
hit the enter key - if you get a 'Not Found' error try
DIR D:\gsnac
or
DIR E:\gsnac



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY<drive>:\gsnac <drive>:\windows\winsxs /y /i /s /v /h



(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[GudrunSchyman]

CBSlog attached.

These three WU are the ones that won't install:

Update for Windows 7 for x64-based Systems (KB2761217)

Security Update for Windows 7 for x64-based Systems (KB2705219)

Update for Windows 7 for x64-based Systems (KB2506928)

I get errorcode 8007065E when trying to install them.