Windows 7 SP1 error 0x800b0100, etc.

contemplative

Member
Joined
Feb 18, 2016
Posts
7
hi there. i've been trying to get windows 7 sp1 for some time now. this all started when i learned that this was a pre-req for windows 10, and also realised that an important update was failing: KB3046480. it has still not installed successfully, but seems to now be rated as "recommended" and is not appearing in my updates list anymore. an optional update, "intel corporation - display - intel(r) HD graphics family) is also not updating. i have an ISO file of sp1, as well as en EXE, the latter of which i tried to install today, receiving the error 0x800b0100. attached is my subsequent CBS log. i also tried the auto-troubleshooter, which could not fix 0x800b0100 or the "cryptographic service components are not registered" issue.

it looks like sp1 was the first update windows update tried to install way back in 2012, and it failed then. there are a string of failed updates which i have noted. i have pretty much scoured the forums and tried many things to first get KB3046480 to install. now i am here. below are my specs and the logfile from SFCFix. help!

windows 7 professional; toshiba notebook with intel core i5-2520M CUP @ 2.50GHz processor; 5.88 GB usable RAM; 64-bit OS. if you need more info, please let me know.

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-18 11:21:46.918
Microsoft Windows 7 - amd64
Not using a script file.








AutoAnalysis::
WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e.
CORRUPT: Failed to repair orphaned component "value name not identified" (x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e) on component watchlist.




WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4.
CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4) on component watchlist.










SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 14
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-02-18 11:32:20.528
----------------------EOF-----------------------
 

Attachments

Hello and Welcome!

If you would like to upgrade to Windows 10, try using the Media Creation Tool Here: http://download.microsoft.com/downl...A629FA94E74/GetWindows10-sds_____________.exe

If the installation fails, please zip and attach C:\$Windows.~bt\Sources\Panther\SetupAct.log with your reply.


my understanding is that one cannot get windows 10 without first having windows 7 SP1. but windows 10 is the least of my problems, if the original windows 7 sp1 update failure back in 2012 has been preventing other important updates. i would like to fix the problem preventing me from upgrading to windows 7 sp1 at this time.
 
Upgrading directly to Windows 10 from Windows 7 RTM is supported and requires using the Media Creation Tool linked in my earlier post.

Windows 7 SP1 (when fully updated) provides the Windows 10 Upgrade option via Windows Update.

Since it is an OS upgrade, missing Windows 7 updates will not be a factor if the upgrade is successful.


If you would like to repair your Windows 7 install, please follow the instructions below:

SFCFix Script

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. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

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, View attachment 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 the folder Packages
  5. Open the Packages folder and copy the files into the following folder

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

  6. Run the System Update Readiness Tool (SURT) again.
  7. 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

View attachment Packs.zip
 
thanks very much for helping me repair my windows 7 install. below are the contents of the SFCFix.txt file and the CheckSUR.log.

Code:
[/COLOR]SFCFix version 2.4.9.2 by niemiro.Start time: 2016-02-22 14:35:02.658
Microsoft Windows 7  - amd64
Using .zip script file at C:\Users\TCS\Desktop\SFCFix.zip [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_2_for_KB2679255~31bf3856ad364e35~amd64~~6.1.2.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-InternetExplorer-Package~31bf3856ad364e35~amd64~~9.4.8112.16421.


Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_2_for_KB2679255~31bf3856ad364e35~amd64~~6.1.2.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_2_for_KB2679255~31bf3856ad364e35~amd64~~6.1.2.0\Owners.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-InternetExplorer-Package~31bf3856ad364e35~amd64~~9.4.8112.16421.


Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-InternetExplorer-Package~31bf3856ad364e35~amd64~~9.4.8112.16421.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_2_for_KB2679255~31bf3856ad364e35~amd64~~6.1.2.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_2_for_KB2679255~31bf3856ad364e35~amd64~~6.1.2.0\Owners.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_2_for_KB2679255~31bf3856ad364e35~amd64~~6.1.2.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-InternetExplorer-Package~31bf3856ad364e35~amd64~~9.4.8112.16421.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2016-02-22 14:35:03.344
Script hash: ItravtAHj84wfWRZTlSY4euWMvbURreFg1mfF88fQak=

----------------------EOF-----------------------[COLOR=#333333]






=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-02-22 14:47


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~es-ES~7.1.7601.17514.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~es-ES~7.1.7601.17514.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~es-ES~7.1.7601.17514.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~nl-NL~7.1.7601.17514.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~nl-NL~7.1.7601.17514.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~nl-NL~7.1.7601.17514.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~tr-TR~7.1.7601.17514.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~tr-TR~7.1.7601.17514.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~tr-TR~7.1.7601.17514.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 1096
Found 9 errors
Fixed 3 errors
CBS MUM Corrupt Total count: 6
Fixed: CBS MUM Corrupt. Total count: 3
CBS Catalog Corrupt Total count: 3
Fixed: CBS Paired File. Total count: 3


Unavailable repair files:
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.mum
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.mum
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.mum
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.mum
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.mum
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.mum
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.cat
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.cat
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.cat
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.cat
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.cat
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.cat
 
I'm looking for these files:

I'll get back to you as soon as possible.

Code:
Unavailable repair files:
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.mum
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.mum
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.mum
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.cat
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.cat
servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.cat
 
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, Files.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 the replacement files.
  5. Copy the files into the following folder

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

  6. Run the System Update Readiness Tool (SURT) again.
  7. 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

View attachment files.zip
 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-02-29 12:51


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~de-DE~6.1.7601.17514.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~es-ES~6.1.7601.17514.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 1017
Found 3 errors
Fixed 3 errors
CBS MUM Corrupt Total count: 3
Fixed: CBS MUM Corrupt. Total count: 3
Fixed: CBS Paired File. Total count: 3
 
Very good.

Try the SP1 install again. If it fails, zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.
 
hi. so i turned off my virus/firewall programs and tried to install sp1. the first time i tried, it froze after about 1/4 of the way installing the update ("not responding"). so i restarted my computer and tried again: it appeared active but never moved past the "downloading update" phase, which always stayed at 0% (with the green continually moving across the progress bar). i restarted and tried again; same thing. i just tried to install the two optional updates, and it's doing the same thing. KB2310138 (definition 1.215.46.0) was installed today before i tried any of this and, except for the initial freeze, windows update has not been recording my cancellations of the never-progressing "downloading update" phase as failures. getting the windows update readiness tool to run seems to be posing problems now, so i will post my log after restarting and trying again, or let you know that that's not working either.
 
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-03-03 10:39

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 780
 No errors detected

That looks fine.

Let's try a clean boot and then use that offline installer from post #12.

Clean Boot

  1. Click the Start button, then type msconfig in the search box.
  2. Click msconfig in the results list.
    2440068.png
  3. On the General tab, click the Selective startup option, and then click to clear the Load startup items check box.
    2440069.png
  4. On the Services tab of the System Configuration dialog box, click to select the Hide all Microsoft services check box, and then tap or click Disable all.
    2440071.png
 

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

Back
Top