Windows 10: UAC message when starting Regedit

This is a recent change, with no obvious cause. If I try to run Regedit (via Win 10 Run box) I get this message:




I'm also getting it for a few other programs that never used to be a problem (may post separately about that issue). But it seems particularly absurd that an MS program built into Win 10 Pro should display it.

Anyone know how I might fix it please?

Note: My UAC setting is on the third option, i.e. one above totally OFF.

--
Terry, East Grinstead, UK

:)

 

UAC virtualization of regedit

Hello,

Thank you for the update.

We understand that you have posted the query in TechNet forums and it seems that EckiS has given a solution to your query on Saturday, March 12, 2016 at 2:27 PM.

Please let us know if you require any other assistance.

Thank you.

Have a great day!

 

UAC virtualization of regedit

Hi,



Thank you for posting your query in Microsoft Community.



To do so: Important this section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For
added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft
Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/ )

How to back up and restore the registry in Windows

For further assistance in this regards, I suggest you to please get in touch with our
TechNet team through below link to resolve the issue:



Technet forums - Windows 10 IT Pro

Our TechNet team will assist you better in this regard.

Regards,

Guru Kiran

 

Not really, when you consider the potential damage it can inflict on the system in the wrong hands (not your hands, malware and the like). You get the same UAC if you want to open a 'Command prompt (Admin)'.

Create a scheduled task to run it elevated, and a shortcut to run the task.
https://www.tenforums.com/tutorials/...dows-10-a.html

 

There are some utilities and thingies out on The 'Net that reportedly help one to minimize if not completely eliminate UAC popups, however, I found out -- there are unintended consequences. I set my Windows 7 UAC to the lowest setting and kept on going.

 

Thanks all. I'll try that Task Scheduler method, although I was hoping for something less complicated.
@RolandJS: Is that 'lowest setting' the same as in Win 10, the fourth option, switching off security altogether? That's what I did initially, but subsequently chickened out and moved it back a notch to the third level. Now seriously considering reverting to OFF.

 

I've been getting that message for quite awhile now, not a big thingy.

 

Is clicking on one extra confirmation really that big of a deal when it is there to ensure that the real user is the one that is accessing the most sensitive parts of the OS that can be used by a virus or malware to totally wipe out the system (at a minimum)?

 

Well, I cannot recommend that lowest setting, I only did it for a specific set of purposes; I think one notch up is the minimum we can and ought to do.

 

I agree that the physical effort for each Regedit usage is small. But I think it's an unintelligent and thoughtless design to repeatedly ask me the same question about the same program. I've been the sole user of a PC for 34 years. So, just as I don't need a written warning every single time I cross the road or drive my car, I object to being unable to switch off this tiresome UAC message.

 

Malware don't care! That UAC is there so Malware cannot(of at the very least makes it harder) use it. Optimal setting would be to use a non-admin account where you need to give your password for every system change(but who does this?).

 

Hi Terry,

maybe try this: go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System and in the right pane modify the value of the EnableLUA DWORD value and set it to 0

In theory it's the same as with UAC dialog box but the Registry modifications have the highest priviledges.

 

Thanks, but no change!

I reckon I use regedit no more than 20-30 times a week, so it's no big deal, of course. More a matter of academic curiosity now!

FWIW, I've this morning managed to solve the UAC problem for another of my programs (the search tool Everything) that I use hundreds of times a week, so that was genuinely bugging me. It turned out that I'd checkmarked the option within the program itself to run as administrator.






After removing that, happily I could start Everything with no UAC nonsense, as I've been doing for months on this PC and years on my XP PC.

But I don't see how that helps with the Regedit puzzle...

 

regedit 20-30 times per week?!? On a personal computer that you are the only user on?!? Wow.

 

To close this off, pleased to report that I found a solution, albeit with caveats.

I implemented the neat hack I found here:
windows - Force a program to run *without* administrator privileges or UAC? - Super User

If I now navigate to any file, such as C:\Windows\regedit.exe, and right click it, I get a new context menu entry:





That does not display the UAC message.

The 'caveats' come when using it in practice. I don't know how to make a one-click shortcut that will do it (without writing a macro or script).

So far I've just I placed a shortcut to regedit.exe in Quick Launch and can therefore launch Regedit without obstruction by right clicking that shortcut and choosing 'Run without admin rights'.

But, of course, that's probably slower than my usual method of running regedit from the Run box. And for any other programs that generate the UAC message it's definitely slower, including the extra UAC click.

Anyway, my post was prompted largely by curiosity and to gripe about dumbed-down security. *Wink

BTW, can anyone explain why running a program without admin rights (the solution for Regedit and for Everything as I described earlier) reduces the UAC warnings? Intuitively I'd have expected the opposite.