New
#11
Thanks, Tom! - I'd probably have got there in the end, but...
Code:SFCFix version 2.4.1.0 by niemiro. Start time: 2014-10-27 15:04:02.194 Using .txt script file at C:\Users\administrator.OAPH\Desktop\SFCFixScript.txt [0] RegistryScript:: Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments. WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6cccd8f687e..b5568f5bd2a_31bf3856ad364e35_6.1.7601.17939_53e9257f597e6d18. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6cccd8f687e..b5568f5bd2a_31bf3856ad364e35_6.1.7601.17939_53e9257f597e6d18. WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\eb791c894c4..db9856f58a7_31bf3856ad364e35_6.1.7601.18327_5cfb25e0f4f5b617. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\eb791c894c4..db9856f58a7_31bf3856ad364e35_6.1.7601.18327_5cfb25e0f4f5b617. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6cccd8f687e..b5568f5bd2a_31bf3856ad364e35_6.1.7601.17939_53e9257f597e6d18. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\eb791c894c4..db9856f58a7_31bf3856ad364e35_6.1.7601.18327_5cfb25e0f4f5b617. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments. RegistryScript:: directive completed successfully. Successfully processed all directives. Failed to generate a complete zip file. Upload aborted. SFCFix version 2.4.1.0 by niemiro has completed. Currently storing 3 datablocks. Finish time: 2014-10-27 15:05:02.664 Script hash: 64rwQcGEhp/mqwVFrZyhhGAc4LevIOPmCGB+uahzzn0= ----------------------EOF-----------------------
Can you run the System Update Readiness Tool please? Post the log when complete:
C:\Windows\Logs\CBS\CheckSUR.persist.log
Also, is Windows Update working now?
Tom
attached are the requested logs. Unfortunately no, Windows update still will not run. There errors are at least different in the Checksur.log now - CSI Mismatched Identity.
I'm just wondering if I need to move along to another resource for further help. Thanks.
Sorry - you fell off the cliff-edge that is my Todo list
As you say...
Code:Checking Component Store (f) CSI Mismatched Identity 0x00000000 appid 6cccd8f687e..b5568f5bd2a_31bf3856ad364e35_6.1.7601.17939_53e9257f597e6d18 appid and keyform do not match; appid is wrong. (f) CSI Mismatched Identity 0x00000000 appid eb791c894c4..db9856f58a7_31bf3856ad364e35_6.1.7601.18327_5cfb25e0f4f5b617 appid and keyform do not match; appid is wrong.
I need to have alook at your COMPONENTS registry hive
Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop andthen compress it - upload the compressed file to your favoured fileshare site(preferably Dropbox or OneDrive) and post a link.
Here's the link to the components store - https://onedrive.live.com/redir?resi...int=file%2crar. Thanks.
I've uploaded a file - md3aa.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, andsave to the default destination (which should be a folder on the desktop)
Create a new System Restore point
Open an Elevated Command Prompt, and run the followingcommands.
Code:IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1 REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1 COPY "%userprofile%\desktop\md3aa\COMPONENTS" C:\Windows\System32\config .
If you get an error with either command, STOP THERE -do not reboot! - post for instructions.
Assuming both commands go OK, reboot, and run anotherCheckSUR scan - post the new CheckSUR.log file.
This is a server 2008 R2 box, so creating a system restore point is not an option, we only have our nightly full system backup to depend on for recovery. So before proceeding, I want to know if something goes haywire with this process, would the server still boot and be functional, or would I be left having to try and recover from a previous system state backup just to get the server to boot up?
There is very little chance of things going badly-enough wrong to prevent normal booting.
The worst that's likely to happen is that the COMPONENTS file is not properly copied - and the system rebuilds a default one. This is easily corrected, and doesn't usually cause any major problems.