Windows 7 SP1 update error 800B0100

Well that was stupid of me! Maybe I shouldn't post at 12:15am any more :p I'll have a look at your logs now.
 
Yeah - but it's the changes that are the points of interest now :)
 
Bingo:

Code:
2013-10-10 13:24:35, Info                  CSI    00000008 CSI Store 3556592 (0x00000000003644f0) initialized
2013-10-10 13:24:35, Info                  CBS    Session: 30328293_4181169856 initialized by client SP Coordinater Engine.
2013-10-10 13:25:01, Info                  CBS    Session: 30328293_4181169856 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2013-10-10 13:25:01, Info                  CBS    SPI: Loading sdbapiu.dll found at C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sdbapiu.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sdbapiu.dll.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sdbapiu.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\acres.dll.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\acres.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\Windows\AppPatch\acres.dll.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: SPC CAT verification failed for C:\Windows\AppPatch\acres.dll.  0x800b0100
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_1_for_KB2762895~31bf3856ad364e35~amd64~~6.1.1.0.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\Windows\AppPatch\acres.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Loading AcRes.dll found at C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\acres.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Initializing drvmain database
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\drvmain.sdb.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\drvmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\Windows\AppPatch\drvmain.sdb.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\Windows\AppPatch\drvmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Loading SDB database found at C:\Windows\AppPatch\drvmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Initializing sysmain database
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sysmain.sdb.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sysmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\Windows\AppPatch\sysmain.sdb.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\Windows\AppPatch\sysmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Loading SDB database found at C:\Windows\AppPatch\sysmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Could not find driver sptd.  Continuing without

SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom
 
Bingo:

Code:
2013-10-10 13:24:35, Info                  CSI    00000008 CSI Store 3556592 (0x00000000003644f0) initialized
2013-10-10 13:24:35, Info                  CBS    Session: 30328293_4181169856 initialized by client SP Coordinater Engine.
2013-10-10 13:25:01, Info                  CBS    Session: 30328293_4181169856 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2013-10-10 13:25:01, Info                  CBS    SPI: Loading sdbapiu.dll found at C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sdbapiu.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sdbapiu.dll.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sdbapiu.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\acres.dll.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\acres.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\Windows\AppPatch\acres.dll.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: SPC CAT verification failed for C:\Windows\AppPatch\acres.dll.  0x800b0100
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_1_for_KB2762895~31bf3856ad364e35~amd64~~6.1.1.0.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\Windows\AppPatch\acres.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Loading AcRes.dll found at C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\acres.dll
2013-10-10 13:25:01, Info                  CBS    SPI: Initializing drvmain database
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\drvmain.sdb.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\drvmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\Windows\AppPatch\drvmain.sdb.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\Windows\AppPatch\drvmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Loading SDB database found at C:\Windows\AppPatch\drvmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Initializing sysmain database
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sysmain.sdb.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\sysmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Self trust verification failed for C:\Windows\AppPatch\sysmain.sdb.  0x57
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\fe73f0f07e5bda4f04e297d5e23382\b8c3e7fbb8f59d0398\spc.cat
2013-10-10 13:25:01, Info                  CBS    SPI: Succeeded verifying trust on C:\Windows\AppPatch\sysmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Loading SDB database found at C:\Windows\AppPatch\sysmain.sdb
2013-10-10 13:25:01, Info                  CBS    SPI: Could not find driver sptd.  Continuing without

SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

Okay. Done. Here's the file!

View attachment cbs.txt
 
Hi RiverBoa99,

Okay, let's go deeper! This looks like a registry problem:

Code:
2013-10-10 13:25:09, Error                 CBS    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
2013-10-10 13:25:09, Info                  CBS    SPI: vssMetaDataOverhead (1500 MB 1536000 KB)
2013-10-10 13:25:09, Error                 CBS    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
2013-10-10 13:25:09, Info                  CBS    SPI: copyWriteMultiplier 1.500000L
2013-10-10 13:25:09, Error                 CBS    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
2013-10-10 13:25:09, Info                  CBS    SPI: peakDiskNeutral (894 MB 915456 KB)
2013-10-10 13:25:09, Error                 CBS    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
2013-10-10 13:25:09, Info                  CBS    SPI: peakDiskMaxLP (521 MB 533504 KB)
2013-10-10 13:25:09, Error                 CBS    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
2013-10-10 13:25:09, Info                  CBS    SPI: writtenBlocksNeutral (3129 MB 3204096 KB)
2013-10-10 13:25:09, Error                 CBS    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
2013-10-10 13:25:09, Info                  CBS    SPI: writtenBlocksMaxLP (1824 MB 1867776 KB)
2013-10-10 13:25:09, Error                 CBS    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
2013-10-10 13:25:09, Info                  CBS    SPI: percentPeakDiskUsageBuffer 0.050000L
2013-10-10 13:25:09, Error                 CBS    SPI: (SPIRegQueryQWORDValue:341)Failed to open the registry root: n/a, key: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1. er=0x2
2013-10-10 13:25:09, Info                  CBS    SPI: percentWrittenBlocksBuffer 0.050000L
2013-10-10 13:25:09, Info                  CBS    SPI: Peak Disk Usage (938 MB 961228 KB)
2013-10-10 13:25:09, Info                  CBS    SPI: Blocks Written (3285 MB 3364300 KB)
2013-10-10 13:25:09, Info                  CBS    SPI: Upper bound check for SRPreserveMin
2013-10-10 13:25:09, Info                  CBS    SPI: copyWriteMultiplier(1.5L) * writtenBlocksTotal(3285 MB 3364300 KB) < freeDiffArea(3365 MB 3446127 KB)
2013-10-10 13:25:09, Info                  CBS    SPI: copyWriteMultiplier(1.5L) * writtenBlocksTotal(3285 MB 3364300 KB) < copyFreeSpace(38241 MB 39159392 KB)
2013-10-10 13:25:09, Info                  CBS    SPI: copyWriteMultiplier(1.5L) * writtenBlocksTotal(3285 MB 3364300 KB) + peakDiskUsage(938 MB 961228 KB) < systemFreeSpace(38697 MB 39626060 KB)
2013-10-10 13:25:09, Info                  CBS    SPI: SRPreserveMin(5866 MB 6007679 KB)
2013-10-10 13:25:09, Info                  CBS    SPI: Lower bound check for SRCleanMin
2013-10-10 13:25:09, Info                  CBS    SPI: peakDiskUsage(938 MB 961228 KB) + vssMetaDataOverhead(1500 MB 1536000 KB) < systemFreeSpace(38697 MB 39626060 KB) + allocatedDiffArea(576 MB 589824 KB)
2013-10-10 13:25:09, Info                  CBS    SPI: SRCleanMin(1862 MB 1907404 KB)
2013-10-10 13:25:09, Info                  CBS    SPI: System falls between the SRCleanMin and SRPreserveMin bounds.  All VSS snapshots will be deleted
2013-10-10 13:25:09, Info                  CBS    SPI: Nested system restore point ended
2013-10-10 13:25:09, Info                  CBS    SPI: Deleting snapshots for volume: \\?\C:

2013-10-10 13:25:09, Info                  CBS    SPI: Deleting VSS snapshot
2013-10-10 13:25:09, Info                  CBS    SPI: Deleting VSS snapshot
2013-10-10 13:25:09, Info                  CBS    SPI: Completed deleting VSS snapshots
2013-10-10 13:25:16, Info                  CBS    SPI: Nested system restore point Windows 7 Service Pack 1 created
2013-10-10 13:25:18, Info                  CBS    SPI: Successfully setup Registry keys for SpReviewEnabler  hr 0x0
2013-10-10 13:25:18, Info                  CBS    SPI: Reporting Succeeded event
2013-10-10 13:25:18, Info                  CBS    SPI: SPInstall terminating, return code 0x0
2013-10-10 13:25:18, Error                 CBS    SPI: (SPIRegQueryStringValue:700)Failed to query registry value: MiscString2 er=0x2
2013-10-10 13:25:18, Error                 CBS    SPI: (CSystem::GetMachineName:395)Failed to query machine name from RAC hr=0x80070002

Command Prompt

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. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePack\SP1" /s > %SYSTEMDRIVE%\tom982.txt

  4. This will create a text file called tom982.txt in the root folder of your main drive (e.g. C:\tom982.txt). Please copy and paste the contents of this into your next post.

Tom
 
I tried the command, all I got was
ERROR: The system was unable to find the specified registry key or value.
 
Well that's not a good sign!

Can you boot into the recovery environment, and launch command prompt please: How to use the Windows 7 System Recovery Environment Command Prompt

When command prompt is launched, type in the following command and press enter:

DISM /image:C:\ /cleanup-image /revertpendingactions

Note: Your drive may be D: or E:. If C: fails, try D: then E:

Then reboot your computer, booting into Windows normally. Run this FixIt in aggressive mode: You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services

Then try updating and post your CBS log please :)

Tom
 
Well that's not a good sign!

Can you boot into the recovery environment, and launch command prompt please: How to use the Windows 7 System Recovery Environment Command Prompt

When command prompt is launched, type in the following command and press enter:

DISM /image:C:\ /cleanup-image /revertpendingactions

Note: Your drive may be D: or E:. If C: fails, try D: then E:

Then reboot your computer, booting into Windows normally. Run this FixIt in aggressive mode: You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services

Then try updating and post your CBS log please :)


Tom

I'm going to have to hunt down my Windows 7 Install Disk. I don't know where it is to boot into the system recovery items. Can I just run the FixIt Tool?
 
Well that's not a good sign!

Can you boot into the recovery environment, and launch command prompt please: How to use the Windows 7 System Recovery Environment Command Prompt

When command prompt is launched, type in the following command and press enter:

DISM /image:C:\ /cleanup-image /revertpendingactions

Note: Your drive may be D: or E:. If C: fails, try D: then E:

Then reboot your computer, booting into Windows normally. Run this FixIt in aggressive mode: You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services

Then try updating and post your CBS log please :)


Tom

I'm going to have to hunt down my Windows 7 Install Disk. I don't know where it is to boot into the system recovery items. Can I just run the FixIt Tool?

Okay, I ran all that. Still won't update. I now have a Windows 7 Install disk. Am I just better doing an upgrade install and getting back to step 1 on this?
 

Attachments

So I had my fill of trying to fix this, and I just did a repair install. Once that was done, I was able to update to SP1, so I'm good to go. Thanks for all the help!
 
Sometimes, that's the only way to go!

Good luck with the 'new' install :)
 

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

Back
Top