New
#21
The line-break from the forum produced a spurious space in there - please try again, now that I've corrected for it with the code box.
The line-break from the forum produced a spurious space in there - please try again, now that I've corrected for it with the code box.
C:\Windows\system32>REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONEN
TS
The operation completed successfully.
C:\Windows\system32>REG QUERY HKLM\components\CanonicalData\Deployments\prnxx002
.inf_31bf3856ad364e35_6.1.7600.16385_5ad632810fefc3dc
HKEY_LOCAL_MACHINE\components\CanonicalData\Deployments\prnxx002.inf_31bf3856ad3
64e35_6.1.7600.16385_5ad632810fefc3dc
i!CBS_microsoft-windows-printer-drivers-package~31bf3856ad364e35~x_f2c41ba89
870a60e REG_BINARY 5B000000000000004D6963726F736F66742D57696E646F77732D507
2696E7465722D447269766572732D5061636B6167657E333162663338353661643336346533357E7
838367E7E362E312E373630302E31363338352E494E465F70726E7878303032
p!CBS_microsoft-windows-printer-drivers-package~31bf3856ad364e35~x_ba002b068
ece5266 REG_BINARY 5B000000000000004D6963726F736F66742D57696E646F77732D507
2696E7465722D447269766572732D5061636B6167657E333162663338353661643336346533357E7
838367E7E362E312E373630312E31373531342E494E465F70726E7878303032
C:\Windows\system32>REG UNLOAD HKLM COMPONENTS
ERROR: Invalid syntax.
Type "REG UNLOAD /?" for usage.
C:\Windows\system32>
Oops - my fault the last error - but it doesn't matter, as it'll unload naturally when it wants to :)
I've uploaded a file - erwad.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it to your desktop.
Right-click on the saved file and select Extract all...
Save it to the default location
This should create a file prnxx002.reg
right-click on the file, and select Merge
Accept the warnings, - you should then get a 'Success' message.
Close all windows, and reboot.
Then run CheckSUR again and we'll see if it did what it was supposed to do.
I extracted file prnxx002.reg to the desktop and ran it.
CheckSUR result:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 22.0
2013-11-23 19:47
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Missing Component Key 0x00000000 x86_prnxx002.inf_31bf3856ad364e35_6.1.7600.16385_none_5ad632810fefc3dc HKLM\Components\DerivedData\Components
(fix) CSI Missing Component Key CSI Registry Item Repaired Key created. There will be more reports as values are replaced.
(f) CSI Missing C Mark 0x00000000 c!prnxx002.inf_31bf3856ad364e35_6.1.7600.16385_5ad632810fefc3dc x86_prnxx002.inf_31bf3856ad364e35_6.1.7600.16385_none_5ad632810fefc3dc Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!prnxx002.inf_31bf3856ad364e35_6.1.7600.16385_5ad632810fefc3dc successfully added to x86_prnxx002.inf_31bf3856ad364e35_6.1.7600.16385_none_5ad632810fefc3dc
Summary:
Seconds executed: 630
Found 2 errors
Fixed 2 errors
CSI Missing Component Key Total count: 1
Fixed: CSI Missing Component Key. Total count: 1
CSI Missing C Mark Total count: 1
Fixed: CSI Missing C Mark. Total count: 1
The good news is that Error Code 800736B3 is gone. but SP1 failed to install and a new error Code 80073712 is coming up.
Should I close this thread as resolved for Error Code 800736B3 and open a new one for 80073712?
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 22.0
2013-11-23 20:38
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 593
No errors detected
The good news is that Error Code 800736B3 is gone. but SP1 failed to install and a new error Code 80073712 is coming up.
Should I close this thread as resolved for Error Code 800736B3 and open a new one for 80073712?
1. attached Attachment 294721
2. sfc /scannow results below
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
C:\Windows\system32>
OK -- post the new CBS folder complete, as I want to have a look at the SP1install data which has probably been archived.
Did you run the install from Windows Updates, or from the standalone download?
if from WU, try running from the download...
http://download.microsoft.com/downlo...MSP1.1_DVD.iso
(It's a general purpose download, so it's 1.9GB! - and contains every current version of Windows 7 SP1).