I have some commercial software that is protected by a 3rd party soft license. This week the 3rd party licensing failed and I tracked it down to when it was trying to access this registry key:
When manually checking that key, even as an administrator I don't have permission to view it. From some googling around I believe that I can get access if I ran as a "System" account, and I have seen references to tools that would allow me to do that. (Just ran regedit using Sysinternals' PSExec tool and saw that the
Properties key only grants access to
However I can freely access all the non-
Properties keys under
After a bit of back and forth with tech support from my vendor (and them talking to their licensing vendor), the reply was that the licensing software needs access to the
Properties key, and that I need to change the registry permissions in order to grant access.
My confusion/concern is that for every key that is under the
Class key, the associated
Properties key exhibits the same permissions behavior - IE as an admin I can't access it. Given that my Windows system has been running that way for a long long time without any issues, I do not think that granting access for the sake of one program is the correct thing to be doing.
Now to my questions:
What systems/accounts genuinely need access to this
What issues/problems would I be opening myself up to if I did grant open slather access to this key?
I suspect that the licensing software may have initially been able to access this particular key when it was being installed through elevated permissions. Does that seem reasonable?
Can anyone point me to MS documentation on the subject?