Closed David-Maisonave closed 1 year ago
I will remove the error message as I have disabled the driver for now. If you're an admin on your machine, RegEdit requires you to elevate, which is why you have access to those keys. I will add support for the Powershell format (good point). Thanks for the feedback!
If you're an admin on your machine, RegEdit requires you to elevate, which is why you have access to those keys.
I have Windows 11 Pro on my desktop computer. When I start RegEdit, I don't get an elevated prompt, but RegEdit still has access to all the users under HKEY_USERS.
On my Windows 11 laptop, when RegEdit starts, I get the following prompt:
In either case I have access to all the users under HKEY_USERS. It seems RegEdit automatically elevates without prompting the user. I'm not sure how RegEdit does that, but it would be more consistent if TotalRegistry could behaves similar.
RegEdit uses the manifest entry called "highestAvailable" to ask for elevation if the user is a true admin. My goal is not to mimic Regedit. I think this Regedit behavior is not good, because it forces you to run it elevated, even if you don't want to.
Version: 0.96 I tried running the program in normal mode, but certain users under the HKEY_USERS keys were inaccessible.
So I tried running the program with the "Run as Admin" option, but I got an error message "Failed to Load Kernel Driver".
After pressing OK, I was able to view the user's registry key.
When I run RegEdit in normal mode, all the HKEY_USERS keys are accessible.
When using the Powershell registry key format, the key is inaccessible. HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\SessionData
If I enter it with the standard format it works. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\SessionData
FYI: Thank you for adding the Book Mark feature! I'm testing a script that runs as another user, and it changes registries at user level and HKEY_LOCAL_MACHINE. With the book marks, it's so easy to move around.