New
#71
I was afraid of that - I'll create the correct Key and see if adding that removes the error, or whether we have to go surgical.
back in a bit
I was afraid of that - I'll create the correct Key and see if adding that removes the error, or whether we have to go surgical.
back in a bit
... on second thoughts, lets see if we can delete the whole subkey first, in case we end up with a domino effect...
Open an Elevated Command Prompt and run the following command
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-windowsco$ecext_31bf3856ad364e35_none_cf36130aacffe558"
accept the warning
does it give a success or error message?
If a success message, then try running SFC /SCANNOW again, and post the new CBS.log
If it fails, I'll have to try another route.
this is going to be fun - NOT!
Let's see if adding the legitimate key removes/changes the problem...
I've uploaded a file - cdoaa.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 cdoaa.reg
right-click on the file, and select Merge
Accept the warnings, - you should then get a 'Success' message (if we're lucky!).
Close all windows, and reboot.
Run another SFC /SCANNOW and post the new CBS.log
Oh.... rats
This will end up being a little risky - so once we get the first bit done (see below), please do the following..
1) Create System Restore point
2) back up your data
Now I need a copy of your Software hive in its 'rest' state.
Print these instructions or have the page open in another PC if you can!
Please Shut down the computer completely, then reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt, type the following commands
DIR C:\Windows\System32
DIR D:\Windows\System32
DIR E:\Windows\System32
DIR F:\Windows\System32
With any luck only one of then will actually work - the others will return "Cannot find..." errors
Make a note of the successful drive letter (most commonly D )
Substitute that letter into the following commands for the <drive>
XCOPY <drive>:\Windows\system32\config\SOFTWARE <drive>:\nptemp\SOFTHIVE.txt /V /H /Y
DIR <drive>:\nptemp\SOFTHIVE.txt
That should copy the hive to the new folder nptemp and check that it's there.
Now type EXIT and reboot to Normal windows
now compress the C:\nptemp\SOFTHIVE.txt file, and upload it to your reply, or to your favourite fileshare site (preferably either SkyDrive or Dropbox)
I use XCOPY all the time in these forums for copying stuff around in the RE like that - it saves a lot of aggro :)
Let's see what I can find and do with it...
This is going to take a while to download - and even longer to upload - on my 3G connection, and it's getting late here now.
I hope to be able to sort it in the morning, and post it sometime during the day
back tomorrow!
Now for the risky bit....
Create another System Restore point (yes, I do mean it! :) )
Run the following command
DEL C:\nptemp\*.*
download the cdoab.zip file from
Noel's SkyDrive
and save it to your desktop
Extract the file to the C:\nptemp folder
DIR C:\nptemp should now show the new SOFTWARE file.
Go back into the repair environment and run the following commands....
REN <drive>:\Windows\System32\config\SOFTWARE SOFTHIVE.OLD
XCOPY <drive>:\nptemp\SOFTWARE <drive>:\Windows\system32\config /V /H /Y
ICACLS <drive>:\Windows\system32\config\SOFTWARE /grant "NT AUTHORITY\SYSTEM":(F) Administrators:(F)
Cross your fingers and reboot to normal Windows :)
Wait 10 minutes before doing anything else - Windows may have some housekeeping to do.
Then reboot again, and try running an SFC /SCANNOW again - post the new CBS.log file