Working around UAC (User Access Control) without running PowerShell elevated

We’ve all heard it and experienced the problem where you can’t perform tasks such as stopping a service on the local machine with PowerShell unless your running PowerShell elevated. If the title bar doesn’t say “Administrator” then you’ll end up with these types of error messages:


If PowerShell remoting is enabled on the local machine, you can simply remote back into it to perform the task without having to run PowerShell elevated:


This seems to be a great alternate instead of always requiring that PowerShell be run elevated since if you happen to do something like opening a URL in Internet Explorer from an elevated PowerShell session, your asking to Get-Pwned since that would mean that Internet Explorer would be running elevated as an admin and not protected by UAC.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: