Ok, I run into the same problem and found another working solution.
My unaccessible key, was a Properties Subkey of a ControlSet class; it was impossible to take own of, nor to show the current owner, with lot of popup error boxes from regedit when trying anything on it.
That was the locked key in my case:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\Properties
(Note: it's usually the same while accessing it from CurrentControlSet, but not in that fixing solution, read forth why I'm accessing that way).
I was directed to that key, while getting lot of SysMon logs lines of ACCESS DENIED from SvcHost on the specific class key.
Edit: my situations trying to access that key, and regedit errors, were exactly those depicted by all the screen shots in this MS forum post.
As of 2020, it seems that the RegDACL tool from Heysoft, suggested above by Josh Compley, is being no more available.
Then I've think of another solution.
I've instead used Process Hacker (https://processhacker.sourceforge.io)
using his menu "Hacker - Run As" function to start a Regedit running with username SYSTEM (NTAUTHORITY\SYSTEM).
(That tool is more or less an evolution of well known Process Explorer by SysInternals, with some added/increased functionality. You will notice that, to be able do that, it builds and then deletes a temporary elevated service; it reports diligently this to you by itself, by means of toast messages from his tray icon, about services creation and deletion).
(Note that this is not the only way to do this. There's other tools too. Read at end of my post).
Then, with this SYSTEM elevated Regedit opened, and after moving to ControlSet001 for the reasons told below, and after reading the Caveats also below:
- [SECURITY NOTICE: it could be saviour do to a full registry backup before to do anything; also, before to change anything, from that point you could fully export the whole registry, included the locked keys you cannot previously access!]
- I was then able to see the previously locked Properties key, and even to see its sub-keys and values (that were previously hidden).
- I was able also to change the locked Properties key's permissions, by re-enabling inheritance, that was set off;
- then exited and reentered the permissions dialog for the key (just to be sure that all changes were there for real), and finally removed the superfluous fixed SYSTEM key permission, not inherited, that was there.
- even the owner setting was magically reset to Administrator, after resettling key inheritance to default.
- While there, I've also inspected all the sub-keys and sub-values permissions, to be sure that all were set to inheritance, and all were ok. Only the "Properties" key was having that problem.
ControlSet
Note that, while being in Regedit elevated with the SYSTEM user, CurrentControlSet were not showing the sub-keys expected, and especially the one I was interested into, while at same time, the ControlSet001 showed to have the expected content.
Maybe, Ccs will take a different Current Control Set, depending on the current running user.
Anyway, having noticed this, I used ControlSet001 to make my changes, and all went well.
Caveats
Be careful and extremely cautions anyway: by using this SYSTEM elevated Regedit, you could do practically everything, and this is a big danger.
I could be able to read (and probably modify, I have't tried) any normally secured sections, as the SECURITY hive sub-keys!
This could be a very big danger, but also an opportunity, if you have incurred into a serious problem on these keys.
Benefits
Important, this procedure has consent to me to recover the locked key and its sub-keys and data, instead of trying of deleting it (there are tools on the net to delete locked keys). The sub-keys and values under it were all preserved, and made accessible again to the system.
This seems a more general-purpose solution, and do not depends on a particular tool, provided only that one has a means to launch a Regedit instance with SYSTEM elevated security authorization, and Process Hacker can do that.
Other tools to do this
I've also run into this other solution using PsExec to open the elevated Regedit in another thread, but I had already Process Hacker installed so I've used it instead: PsExec solution by Scott Chamberlain
Another completely different solution involving use of SubInAcl Ms utility is depicted here (Ms community post - seek reply by kitsune0). This will rework all the registry permissions, but IMHO I will not add full access to the simple user as stated, anyway.
Real-time windows access patching
With only this elevated Regedit opened, and an instance of Process Monitor running filtered (telling me of registry ACCESS DENIED messages in real time for users different from normal user), I could fix many different Windows Registry Access problems in "real time" (as the error lines come up on Process Monitor), while at the same time, recovering full key trees that for whatever unknown reason, were made inaccessible even to the system itself, and so, definitely repair a wide bunch of windows malfunctioning in a single, intensive round.
Be careful, while doing this, that not all ACCESS DENIED lines logged by SysMon are errors needing to be solved. Some are part of permission checking logic from the applications and system components, and do not require changing anything. You must concentrate on the repeated consecutive failed tries from components that are involved in some real malfunctioning you are experiencing from your system.
Final notes
Hope that my solution could help other people that is incurring in this very problem.
Always backup your whole system and registry hives before to do intensive registry mining and patching.
Disclaimer: I am not responsible of you destroying your windows system by means of this trick. Be very careful!
Regestry keys, like files, have permissions on them. Right click on the folder for the key you are trying to find out about and see if you can click on permissions.
If you can not even do that there is a hack you can do to run a app as SYSTEM instead of administrator.
Go download PsExec. Open a command prompt as administrator (by right clicking on the command prompt shortcut and clicking run as administrator). Run the following command:
psexec -i -d -s c:\windows\regedit.exe
This will launch regedit with the system account (make sure you do not have any copies open already) and see if you are able to delete those folders.
P.S. Check to see if solidworks created any users or groups on your machine and delete them (delete the corresponding folder in the C:\Users folder too), I had a similar issue when the user SQLServer installed got corrupted, the only sign was a registry key could not be created/deleted during the setup process.
Best Answer
Firstly- if this problem started 1-2 years ago (and it was used for a while before that), then it could have been 3 or more years since the system was last installed. If that was my computer I would do a reinstall anyway. If the toilet's dirty, do you squirt some bleach in there then flush it, or spend many painful hours trying to clean it with a toothbrush? :P I don't get why people think they can easily fix registry problems manually- and I especially don't understand why people trust (and pay money for) a 3rd-party product to go flailing around the registry trying to "optimize" it. Those registry clean-up programs are digital snake oil- they'll never be able to accomplish what a simple reinstall can do, and they also risk introducing new problems.
Seriously though- if you want to keep the existing installation you need to TAKE OWNERSHIP of these registry keys. Forget logging on as administrator. That's the easy answer, and you probably are an administrator anyway.
Right click on the problem keys -> permissions -> advanced -> owner (then add yourself as the owner), then you can give yourself full write access to that key.
The rest is easy- it will work as usual.
I still think you'd be much better off doing a reinstall though! ;)