New
#11
CheckSUR and SFC are already clean - apart from this problem in the registry.
I've asked him to have a go at deleting the errant entry from an RE boot, but I don't hold out much hope.
CheckSUR and SFC are already clean - apart from this problem in the registry.
I've asked him to have a go at deleting the errant entry from an RE boot, but I don't hold out much hope.
Hello NoelDP,
I did as you told and was able to delete the entry without any error messages.
Whats next?
Okay, i have run "sfc /scannow" and afterwards the System Update Readiness Tool (Windows6.1-KB947821-v25-x64.msu). Here is the new CBS-Folder!
Oh dear....
Please see if you still see the key in the registry - if you do, then we'll have to go for the repair install (It's obviously being rebuilt in a corrupted fashion by something else)Code:Checking Packages (f) CBS Registry Error 0x00000002 Package_2_for_KB2567680~31bf3856ad364e35~amd64~~6.1.1.2 Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\ Failed to open store sub key
Please open Regedit (in normal Windows)
Navigate to the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
key
Then navigate to the
Package_2_for_KB2567680~31bf3856ad364e35~amd64~~6.1.1.2
subkey
What happens when you click on it now? (does it even exist?)
It's in the registry and on clicking on it produces the same error:
"Error while opening Package_2_for_KB2567680~31bf3856ad364e35~amd64~~6.1.1.2; The key can not be opened due to an error. Details: The System cannot find the given file."
In that case, all I can suggest is a repair install - make sure that you back up your data to external media first, as I'm by no means certain that it will complete without incident.
Follow the instructions here - Repair Install
I could probably have a crack at repairing the binary for the registry hive, I bet something has bitflipped to a termination character on the permissions of that value.
But there's only one problem, this is working on the SOFTWARE hive, which is where the product key is encoded for retail licenses so it's unlikely that you would trust me enough to do this. If your license is OEM it's a whole different matter.
Do you know if you have an OEM license, or a retail license? If you don't know, just tell me whether your computer has a COA sticker on it, and for which version it is valid for please.
Tom
Oh yeah Thanks.
Follow the instructions here please:
Windows Genuine and Activation Issue Posting Instructions
Tom