How to Fix PowerShell Always Running as Admin in Windows

PowerShell opens with admin rights when the launcher is set to force elevation. Fix the shortcut, the Windows Terminal profile, or the parent process that starts it; changing PowerShell itself rarely helps. If the wrong launch path keeps reusing admin rights, every script inherits them, which can hide a bad deployment or trigger avoidable system changes.

The quickest first check is the shortcut or pin you click every day. If that was changed to run with admin rights, the shell will keep opening with a consent prompt or in an admin token until you remove that setting.

Why PowerShell opens as administrator

How to tell admin and normal windows apart

A normal PowerShell window and an admin window are not the same session. The admin one comes from UAC elevation and gets a different token after consent, so the title bar, prompt behavior, and what it can access may differ.

Compare the title bar of a shell launched from a known normal path with one launched from the suspect icon. If the prompt says Administrator, or the window came from a consent prompt, that launch path is the one to fix.

📊 LazyAdmin notes that Open PowerShell window here becomes Open in Windows Terminal on Windows 11. Source: How-to Run a PowerShell Script.

Likely causes, from most common to least common

Most often, the issue is a shortcut or pin set to run with admin rights. In some cases, Windows Terminal may start an elevated profile or inherit admin context from an elevated parent window. If the setting keeps returning after reboot or sign-in, a managed tool or startup process may be putting it back.

How do I make PowerShell open normally

Start with the exact entry point you click most often. A desktop shortcut, Start pin, or taskbar pin can each have its own admin flag, so changing only one may leave the others unchanged.

1. Right-click the desktop shortcut or Start menu item and open Properties.
2. Open the Compatibility tab.
3. Clear Run this program as an administrator.
4. Select OK, then launch that same shortcut once before repinning it.
5. If a taskbar pin or Start pin still opens elevated, remove that pin and pin the freshly tested shortcut again.

That per-shortcut setting can affect pinned and taskbar copies that were created from the earlier shortcut state. Testing the desktop shortcut first keeps you from repinning a stale elevated copy.

How to always run PowerShell as administrator

If the goal is one specific shortcut that always asks for admin rights, set that shortcut directly instead of changing every PowerShell launch. That keeps normal launches normal and limits admin mode to the places that need it.

1. Right-click the shortcut you want to use.
2. Select Properties and open the Compatibility tab.
3. Check Run this program as an administrator.
4. Select Apply, then OK.
5. Launch that shortcut and confirm the consent prompt appears before the shell opens.

Use this only for the one shortcut that needs admin rights. It does not mean every PowerShell entry point on the machine should run that way.

Could the parent window be forcing admin mode

Yes. CMD, Explorer, Windows Terminal, PowerShell ISE, or another app can start PowerShell from an already elevated session, and the new shell may inherit that admin context. In that case, the child window is not the problem.

1. Close the current shell.
2. Open a plain, non-admin Command Prompt or Windows PowerShell from the Start menu.
3. Run the same command or script path again.
4. If the new window is normal here but not when launched from another app, fix the parent launcher instead.
5. Check the shell title bar and whether a consent prompt appeared before launch.

This matters when a task runner, admin CMD window, or elevated Explorer session is silently handing admin rights to every child window.

What setting makes PowerShell run as admin every time

Usually the issue is with the launch setting rather than with PowerShell itself. The common places are shortcut compatibility flags, a Windows Terminal profile launched from an admin context, or a managed shortcut that keeps coming back after sign-in.

1. Check the shortcut’s Compatibility tab first.
2. Check Windows Terminal settings next if you open PowerShell there.
3. Test from a non-admin parent window.
4. If the change returns after reboot or sign-in, collect the exact path that relaunches it and pass that to IT or the tool owner.

Proof asset: the one-page launch-path matrix

Use this matrix during live troubleshooting. It separates the place you clicked from the place where elevation is being forced, which is the fastest way to stop chasing the wrong layer.

How do I stop Windows Terminal from always opening elevated?

Windows Terminal needs two checks: the default terminal app choice in Windows 11, and the profile or parent window used to start it. If Terminal itself is launched from an admin session, every shell inside it can open with the same rights.

1. Open Windows Terminal, then select the drop-down menu and choose Settings.
2. Open Startup and check Default terminal application in Windows 11.
3. Open the active profile and inspect Starting directory and Launch behavior.
4. Compare the title bar of a normal launch with a shell opened from an admin window.
5. If the whole app starts elevated, open Terminal from a non-admin Start menu entry or reset the pin you launch from.

Do not treat the profile as a generic cause by itself. The key question is whether Terminal was started from an admin context or from a normal one.

What if PowerShell is not elevated, but scripts still fail?

That is a separate issue. Execution policy can block scripts without making the shell open as admin, and the default policy is Restricted, which does not allow scripts to run.

1. Check whether the script is failing with “Running scripts is disabled on this system.”
2. Open Windows PowerShell from the Start menu or Win+X, then run Set-ExecutionPolicy RemoteSigned if that policy matches the script source.
3. If you only need to bypass policy for a controlled run, use Bypass for that session.
4. Remember that RemoteSigned requires a digital signature for downloaded scripts, and Bypass runs scripts without warnings.

Execution policy is about whether a script may run. It is not the usual reason a shell opens as administrator.

How to run PowerShell scripts from different launch methods

Different launch methods can change both script behavior and elevation. Right-click Run with PowerShell, launching from CMD, opening in PowerShell ISE, or using a Start menu entry can each lead to a different context.

1. Right-click the script and choose Run with PowerShell when you want the simplest one-off run.
2. Use PowerShell plus the script path from CMD when you need a command-line launch.
3. Open PowerShell ISE when you want to inspect the script before running it.
4. Remember that some script windows close after completion, so rerun from an interactive shell if you need to read output.
5. On Windows 11, Open PowerShell window here may appear as Open in Windows Terminal.

Still not working?

If the setting returns after reboot or sign-in, it may be worth looking for something else that is restoring it instead of adjusting the shortcut in isolation. That usually points to endpoint management, a logon script, or startup tooling redeploying the same pin, shortcut, or Terminal setting.

1. Record the exact path that opens elevated, the exact menu path you changed, and the exact symptom after sign-in.
2. Test once from a plain non-admin desktop shortcut, once from Start, and once from Terminal.
3. If the behavior comes back, hand the path and symptom to IT or the tool owner and ask which process restores the pin or shortcut.

Prevention: after changing a shortcut, launch that desktop shortcut once before repinning it. That avoids carrying the old admin flag into the taskbar or Start pin.

Frequently asked questions

how to fix powershell always running as administrator

Start with the shortcut or pin you use most. Open its Properties, clear Run this program as an administrator on the Compatibility tab, then test the desktop shortcut before touching any pinned copy. If you open PowerShell through Windows Terminal, check whether Terminal itself was launched from an admin window.

how to set powershell to always run as administrator

Use a single shortcut for that purpose and set it on the Compatibility tab. Check Run this program as an administrator, apply the change, and launch that shortcut directly. Keep a separate normal shortcut for everyday work so you do not force admin mode everywhere.

how to run powershell not as admin

Open it from a plain Start menu entry or a desktop shortcut whose Compatibility tab does not have Run this program as an administrator checked. If Windows Terminal is involved, start Terminal from a non-admin session and confirm the profile is the one you intended to use.

how to always run powershell as administrator

Set the admin flag on one specific shortcut instead of changing the app itself. Right-click the shortcut, open Properties, go to Compatibility, and check Run this program as an administrator. That gives you a predictable admin launch without changing unrelated entries.

why does PowerShell always open as administrator

Most often, the launcher is forcing it. A shortcut flag, a repinned old copy, an admin parent window, or an elevated Windows Terminal session can all make a normal shell look like it is permanently set to admin. The fix is to trace the exact launch path and clear the elevation there.

how do I stop Windows Terminal from always opening elevated

Open Settings in Windows Terminal, check Startup, review Default terminal application in Windows 11, and inspect the active profile’s Starting directory and Launch behavior. If the whole app still opens elevated, launch Terminal from a non-admin session and replace any elevated pin.

what setting makes PowerShell run as admin every time

The usual settings are not inside PowerShell itself. Look first at the shortcut’s Compatibility tab, then the Windows Terminal startup path, and finally the parent window that launched it. If the problem returns after sign-in, a managed tool is likely reapplying the same launch setting.