[SOLVED] Windows Vista SP1 Won't Install - Error 800B0100

[stu3796]

Hi! I realize I'm living on an older Windows system, but I'm hoping you can help out anyways. I have been trying to install Vista SP 1 for several years now. Every once in awhile I'll try and it errors out and I decide oh well, I don't really need it and go on with life. Well, my wireless router crapped out and the new one I bought needs SP1 to run... blah! So I've been screwing with it all weekend to no avail. I have tried everything I can find online and still not lucking out. The following highlight the major points, but certainly not everything I've tried:

1. Clean boot
2. rename software distribution folder
3. system update readiness tool
4. install SP1 via update tool (says installed after about 30 seconds, but not really there)
5. install SP1 directly (runs for about 15 minutes and then 800B0100 error)
6. stopped firewall
7. stopped antivirus
8. and it seems like about 16 other things but I can't remember them all right now.

I've attached my log files and am really hoping that someone can help me out. I can buy Windows 7 fairly inexpensively via my employer but it seems like I need SP1 installed to upgrade to that.

Thank you!

Charlie

 

[tom982]

Hello Charlie, welcome to Sysnative!

Your CheckSUR log is showing a few corrupt files:

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22574
Package Version 18.0
2013-04-28 18:08

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_9_for_KB948610~31bf3856ad364e35~x86~~6.0.6001.2123.mum        Line 1: 
(f)    CBS MUM Corrupt    0x800F0900    servicing\Packages\Package_for_KB948610~31bf3856ad364e35~x86~~6.0.6001.2123.mum        Line 1: 

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_7a31de9142efb79b54102880d56e593c_b03f5f7f11d50a3a_6.0.6000.16708_none_a5cc90a4cfc17969.manifest    x86_7a31de9142efb79b54102880d56e593c_b03f5f7f11d50a3a_6.0.6000.16708_none_a5cc90a4cfc17969    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_faf93044e08b8c20a1bf3e4441d0f004_b77a5c561934e089_6.0.6000.20864_none_46ab66f1f7180db5.manifest    x86_faf93044e08b8c20a1bf3e4441d0f004_b77a5c561934e089_6.0.6000.20864_none_46ab66f1f7180db5    
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\x86_5a96a562df1012984e62ecff5ed80dd3_b77a5c561934e089_6.0.6000.16708_none_f1a94c2b2157dfc1.manifest    x86_5a96a562df1012984e62ecff5ed80dd3_b77a5c561934e089_6.0.6000.16708_none_f1a94c2b2157dfc1    
(f)    CSI Manifest Bad XML    0xC0150006    winsxs\Manifests\msil_system.io.log.resources_b03f5f7f11d50a3a_6.0.6000.16708_en-us_a58bb785a5252cdb.manifest    msil_system.io.log.resources_b03f5f7f11d50a3a_6.0.6000.16708_en-us_a58bb785a5252cdb    
(f)    CSI Manifest Bad XML    0xC0150006    winsxs\Manifests\msil_system.identitymodel.selectors.resources_b77a5c561934e089_6.0.6000.20864_en-us_7814136668210d94.manifest    msil_system.identitymodel.selectors.resources_b77a5c561934e089_6.0.6000.20864_en-us_7814136668210d94    

Summary:
Seconds executed: 1829
 Found 7 errors
  CSI Manifest Bad XML Total count: 2
  CSI Manifest Failed Catalog Check Total count: 3
  CBS MUM Corrupt Total count: 2

Unavailable repair files:
    winsxs\manifests\x86_7a31de9142efb79b54102880d56e593c_b03f5f7f11d50a3a_6.0.6000.16708_none_a5cc90a4cfc17969.manifest
    winsxs\manifests\x86_faf93044e08b8c20a1bf3e4441d0f004_b77a5c561934e089_6.0.6000.20864_none_46ab66f1f7180db5.manifest
    winsxs\manifests\x86_5a96a562df1012984e62ecff5ed80dd3_b77a5c561934e089_6.0.6000.16708_none_f1a94c2b2157dfc1.manifest
    winsxs\manifests\msil_system.io.log.resources_b03f5f7f11d50a3a_6.0.6000.16708_en-us_a58bb785a5252cdb.manifest
    winsxs\manifests\msil_system.identitymodel.selectors.resources_b77a5c561934e089_6.0.6000.20864_en-us_7814136668210d94.manifest
    servicing\packages\Package_9_for_KB948610~31bf3856ad364e35~x86~~6.0.6001.2123.mum
    servicing\packages\Package_for_KB948610~31bf3856ad364e35~x86~~6.0.6001.2123.mum
    servicing\packages\Package_9_for_KB948610~31bf3856ad364e35~x86~~6.0.6001.2123.cat
    servicing\packages\Package_for_KB948610~31bf3856ad364e35~x86~~6.0.6001.2123.cat

Can you zip up and attach this file to your next post please? I've never seen a Bad XML error before and I'm curious what's actually wrong with the file :)

C:\Windows\winsxs\Manifests\msil_system.identitymodel.selectors.resources_b77a5c561934e089_6.0.6000.20864_en-us_7814136668210d94.manifest

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Please download the attached file, Packs.zip and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing two folders, Manifests and Packages
5. Open the Manifests folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Winsxs\Manifests
   
   
6. Open the Packages folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Servicing\Packages
   
   
7. Run the System Update Readiness Tool (SURT) again
8. 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.persist.log

Tom

 

[stu3796]

Tom,

Thanks! I did as you said and the 2 files should be attached that you requested. I appreciate the help and let me know what else to try. Thanks!

Charlie

 

[tom982]

Hi Charlie,

Thanks for uploading the files. Your CheckSUR log is showing that all of the problems have been resolved so can you try updating and let me know how it goes please?

The corrupt manifest (that we have since repaired) is really messed up!

Before:

U p d a t e s \ M i c r o s o f t   . N E T   F r a m e w o r k   3 . 5   S P 1 \ S P 1 \ K B 9 5 8 4 8 4   0ae2Ðÿÿÿvk   €Y   
   
 ï ThisVersionInstalled0ð øÿÿÿèMð Øÿÿÿvk :   ÐJð 
   
   URLInfoAbout   Àÿÿÿh t t p : / / s u p p o r t . m i c r o s o f t . c o m   ÿÿèÿÿÿ5 / 2 5 / 2 0 1 0      ¨Mð     b 
@b 
�è
Øÿÿÿ$
ü¡º|J¹k6ˬìH*¯‰v¸« VbT®®Í¥«{kP¦Øÿÿÿvk     Mð    
  oLastModTime  V exÿÿÿd l P = k N ' k [ 5 n u [ y @ 0 g y q n N e t F X _ C o r e _ x 8 6 _ e n u _ D D F > 5 g M p s ( q s ` @ h k N - S 1 8 A q T      oÈÿÿÿp”í ¸„í @rí È�í êí Ðâí ßí Xáí Xäí ¸î èì Èçí     ¨ÿÿÿnk  j»s¢ÚûÊ
    pÏï 
       ˜Mð ÿÿÿÿ   ˜

After:

<?xml version="1.0" encoding="UTF-8"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" description="Windows Communication Foundation component" displayName="Windows Communication Foundation System.IdentityModel.Selectors.Resources" company="Microsoft" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved." creationTimeStamp="2006-07-21T00:00:00" lastUpdateTimeStamp="2006-07-21T00:00:00" isolated="false">
  <assemblyIdentity name="System.IdentityModel.Selectors.Resources" version="6.0.6000.20864" processorArchitecture="msil" language="en-us" publicKeyToken="b77a5c561934e089" />
</assembly>

Tom

 

[stu3796]

Tom,
You, sir, are my hero. You have no idea how many hours I have screwed with this stupid thing over the years and in 5 minutes I was able to do what you fixed and get the SP1 update running. It is installed and running as needed. Thank you!!

Charlie

 

[tom982]

Hi Charlie,

That's great news! Thanks for posting back the results.

You're most welcome, it was a pleasure to work with you! :)

Tom