New
#61
YAY! all clear :)
Now please run another SFC /SCANNOW, and post the new CBS.log - just in case it's been affected by our tinkering in the registry.
YAY! all clear :)
Now please run another SFC /SCANNOW, and post the new CBS.log - just in case it's been affected by our tinkering in the registry.
So. I get this...
No point in posting the CBS.log at this stage, I believe. I ran it administrator and from safe mode after, to be sure.Windows Resource Protection could not perform the requested operation.
Thought it might have been my fault, so I checked the permissions and owners of the manipulated keys in the Registry again, but all seem to be OK. Ran another attempt at SFC in safe mode; same message in the CL, so...
Here's the log.
There's another registry key that happens to be a critical one, that has a bitflip in it.
The trick is to work out which one...
It's pointing the system to the registry key
HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-windowsco$ecext_31bf3856ad364e35_none_cf36130aacffe558
(note the highlighted character).
I'm not sure (yet) where to look for the bad entry - I'll do some research and get back to you.
Please run the following commands in an elevated Command Prompt, and post the results...
(Note: I expect at least one of the results to throw an error.)Code:REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-windowscodecext_31bf3856ad364e35_none_cf36130aacffe558" /S REG QUERY "HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-windowsco$ecext_31bf3856ad364e35_none_cf36130aacffe558" REG QUERY "HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\x86_microsoft-windows-windowscodecext_31bf3856ad364e35_none_cf36130aacffe558" /S .
Last edited by NoelDP; 05 Jan 2014 at 11:41. Reason: add reg load command
[ranting_wonderment_comment]
Now, if that "$" symbol is not supposed to be there, I expect this is the same sort of corruption that occasionally occurs on items inside the update status file of some "experimental" distros of Linux? I would know what to do about that, but I fully believe this is another ball game. Just trying to begin to equate my understanding, that's all...
[/ranting_wonderment_comment]
There was some similar corruption on one of the previously deleted packages in the Registry. I took note of it then; it is this one...
Perhaps I should have mentioned it?Package_75_for_ºB2813430~31bf3856ad364e35~amd64~~6.1.1.4.Trigger_1
Anyway, the results of running those commands in an elevated CL...
Code:REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS The operation completed successfully. REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-windowscodecext_31bf3856ad364e35_none_cf36130aacffe558" /S ERROR: The system was unable to find the specified registry key or value. REG QUERY "HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-windowsco$ecext_31bf3856ad364e35_none_cf36130aacffe558" ERROR: The system was unable to find the specified registry key or value. REG QUERY "HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\x86_microsoft-windows-windowscodecext_31bf3856ad364e35_none_cf36130aacffe558" /S ERROR: The system was unable to find the specified registry key or value.
Hmmm - this is not good news, as it could mean major corruption
Let's have a look at the master Key.
Please open Regedit and navigate to the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
key
right-click on it and select Export
Change the 'Save as type' to 'Registry Hive Files', add a name, and save it - close Regedit and upload the saved file to your reply.
Here it is.
After-thought...
You know, SFC /SCANNOW did work correctly before. Could this be some issue with the Registry due to some permission or what-not that was manipulated? Far as I know I set them all back to their original ownerships and permissions.
OK - I found the key exactly where it should be, and that appears to be the only error in that subkey
Now let's see if we can correct the error on your machine
Open Regedit, and navigate to the
HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\
key
In there, look for the
x86_microsoft-windows-windowsco$ecext_31bf3856ad364e35_none_cf36130aacffe558
subkey - highlight it and hit F2 to allow a rename
(You may need to take ownership)
change the '$' to a 'd'
hit the Enter key to save it
(return Ownership if necessary afterwards)
Close Regedit, and reboot
Now try running SFC /SCANNOW again - what happens?
Codecext, hmm? Anything to do with Shark007 Codecs, perhaps? I do have them installed.
The subkey does not even have a list expand "+" before it, and clicking on it produces the following information in an "Error Opening Key" message box;
There is no way to take ownership of the subkey.x86_microsoft-windows-windowsco$ecext_31bf3856ad364e35_none_cf36130aacffe558 cannot be opened.
An error is preventing this key from being opened.
Details: The system cannot find the file specified.