Personalization Add "Open in Terminal (Admin)" context menu in Windows 11

rseiler · Nov 10, 2024

I'm not absolutely sure, but "Add_Open_in_Windows_Terminal_as_administrator.reg" seems to not work when freshly tried on either of the most recent Windows Dev releases. Nothing at all happens when tried. To be clear, it installs fine but doesn't actually do the job.

Brink · Nov 10, 2024

rseiler said:
I'm not absolutely sure, but "Add_Open_in_Windows_Terminal_as_administrator.reg" seems to not work when freshly tried on either of the most recent Windows Dev releases. Nothing at all happens when tried. To be clear, it installs fine but doesn't actually do the job.

Hello mate,

I just tested on my system for changes, but it still works for me.

Do note, you will need to click/tap on "Show more options" in the context menu before seeing "Open in Windows Terminal as administrator" like in the example at the top of the tutorial.

When you click on "Open in Windows Terminal as administrator", you should see a command prompt flash, and then get a UAC prompt to approve opening Terminal as admin.

rseiler · Nov 10, 2024

Brink said:
Hello mate,

I just tested on my system for changes, but it still works for me.

Do note, you will need to click/tap on "Show more options" in the context menu before seeing "Open in Windows Terminal as administrator" like in the example at the top of the tutorial.

When you click on "Open in Windows Terminal as administrator", you should see a command prompt flash, and then get a UAC prompt to approve opening Terminal as admin.

OK, that's fine, it's just something interfering here then. I do see it on the subordinate context menu, but it doesn't trigger UAC or anything else. I have an ancient one (also from here way back) for admin cmd that I put on instead.

Brink · Nov 10, 2024

rseiler said:
OK, that's fine, it's just something interfering here then. I do see it on the subordinate context menu, but it doesn't trigger UAC or anything else. I have an ancient one (also from here way back) for admin cmd that I put on instead.

Did you make any changes to UAC settings that could be causing no prompt?

rseiler · Nov 10, 2024

Brink said:
Did you make any changes to UAC settings that could be causing no prompt?

No, but I did find the problem: I was concentrating on opening from the top of a given drive, and that doesn't work. It does from directories.

Brink · Nov 10, 2024

rseiler said:
No, but I did find the problem: I was concentrating on opening from the top of a given drive, and that doesn't work. It does from directories.

JohnGray · May 22, 2025

Shawn: please could you advise what I should run simply to get "Open Command Prompt (Admin) here" [at this folder] to appear in the context menu? That's the only option I want, avoiding PowerShell and Windows Terminal!
Perhaps your version for Windows 10 would still apply in Windows 11?
And will this also give the desired result for the non-Windows Exploter Xplorer2?
Thanks very much!

antspants · May 22, 2025

JohnGray said:
Shaun: please could you advise what I should run simply to get "Open Command Prompt (Admin) here" [at this folder] to appear in the context menu? That's the only option I want, avoiding PowerShell and Windows Terminal!
Perhaps your version for Windows 10 would still apply in Windows 11?
And will this also give the desired result for the non-Windows Exploter Xplorer2?
Thanks very much!

Hi, John & welcome.

One way to find out, try it. May be an issue due to the new “Show More Options” in Windows 11 (Which you can remove)

Disable "Show more options" context menu in Windows 11

This tutorial will show you how to enable or disable having to click on "Show more options" to see the full context menu for your account or all users in Windows 11. When you right click on an item in Windows 11, you will see a new modern condensed context menu with Show more options...

www.elevenforum.com

Winaero tweaker can apparently add it to the context menu. Scroll all the way down to “Add the elevated Command Prompt context menu with Winaero Tweaker” (I believe it is what I used)

How to Open Command Prompt as Administrator in Windows 11

You can use multiple methods to open Command Prompt as Administrator in Windows 11. This can be useful when you need to allow some console tool to finish

winaero.com

But, I am sure our local Alien (Shawn) probably has a fix.

Brink · May 22, 2025

JohnGray said:
Shawn: please could you advise what I should run simply to get "Open Command Prompt (Admin) here" [at this folder] to appear in the context menu? That's the only option I want, avoiding PowerShell and Windows Terminal!
Perhaps your version for Windows 10 would still apply in Windows 11?
And will this also give the desired result for the non-Windows Exploter Xplorer2?
Thanks very much!

Hello John, and welcome to the forum.

Yes, you can still use the W10 version in that tutorial in W11.

JohnGray · May 22, 2025

Thanks to you both! I'll use the Windows 10 variant.
I must confess that I've managed to annoy you several times over the years beginning with Windows 7, so I don't know why my post count got reset to zero!

Brink · May 22, 2025

JohnGray said:
Thanks to you both! I'll use the Windows 10 variant.
I must confess that I've managed to annoy you several times over the years beginning with Windows 7, so I don't know why my post count got reset to zero!

Not sure. I don't show any other posts by you here other than these.

boktai1000 · Sep 4, 2026

Windows Defender has started flagging when you actually attempt to say open PowerShell as Admin from the Context Menu (after adding the .reg mind you) as a threat, and blocking it from working.

Perhaps the manner that this is executed is used in such a way that is perceived as malicious behavior.

This has me wondering if there is a more elegant or preferred way to perform the same action that will not trigger such a block from Defender.

Name: Trojan:Win32/Commando.A!ml
Detected Items:

Code:

CmdLine: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -WindowStyle Hidden Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','"Windows PowerShell"','-d','"C:\Users\<YOURNAMEHERE>\."'

Brink · Sep 4, 2026

boktai1000 said:
Windows Defender has started flagging when you actually attempt to say open PowerShell as Admin from the Context Menu (after adding the .reg mind you) as a threat, and blocking it from working.

Perhaps the manner that this is executed is used in such a way that is perceived as malicious behavior.

This has me wondering if there is a more elegant or preferred way to perform the same action that will not trigger such a block from Defender.

Name: Trojan:Win32/Commando.A!ml
Detected Items:

Code:

CmdLine: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -WindowStyle Hidden Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','"Windows PowerShell"','-d','"C:\Users\<YOURNAMEHERE>\."'

Hmm, I'm seeing the same thing.

It still works if selecting the default profile. I'll look into this more later today to see what the issue could be.

UPDATE: It appears to be caused from the more strict security updates for W11. It's a false positive since it appears any elevated context‑menu command that launches another process is now blocked. Defender flags PowerShell/RunAs elevation from shell extensions. Now to just find a workaround so you don't have to "Allow" this "blocked threat" in Windows Security when triggered for it to work.

Expandable context menu option removed for now.

boktai1000 · Friday at 11:38 AM

I just wanted to follow up that I had tried the basic version of just "Open in Terminal (Admin)" and did a little bit of testing the day of but never reported back, I believe I did see the same or similar AV warning and removed it.

Code:

Detected: Trojan:Win32/Commando.A!ml

CmdLine: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -WindowStyle Hidden Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-d','"C:\Open in Windows Terminal (Admin)\."')

But, I just decided to give it a test again and did not receive any issues. I think I may have also had an issue opening it in a folder that was located in a directory closer to C:\ (such as C:\Test) compared to something like my Downloads folder for my user account.

Anyways, it has me curious if perhaps the AV detection was resolved, or perhaps that still persists - not sure. Just thought I would check in, I unfortunately don't have the original .reg file of that to give it a test and was curious if you had any other findings.

Brink · Friday at 11:45 AM

boktai1000 said:
I just wanted to follow up that I had tried the basic version of just "Open in Terminal (Admin)" and did a little bit of testing the day of but never reported back, I believe I did see the same or similar AV warning and removed it.

But, I just decided to give it a test again and did not receive any issues. I think I may have also had an issue opening it in a folder that was located in a directory closer to C:\ (such as C:\Test) compared to something like my Downloads folder for my user account.

Anyways, it has me curious if perhaps the AV detection was resolved, or perhaps that still persists - not sure. Just thought I would check in, I unfortunately don't have the original .reg file of that to give it a test and was curious if you had any other findings.

Directly opening an elevated context menu works fine as now in the tutorial. So far, it appears to just be an issue with the AV when any elevated context‑menu command launches another process.

TrebleTA · 2026-09-12T08:56:06-0400

So I used a Reg file I copied then edited and made, from here.

Code:

Windows Registry Editor Version 5.00

; Created by: Shawn Brink Moddied By Treble TA to remove sub menus
; Created on: May 2, 2021 (07/01/2026)
; Updated on: (07/01/2026 by TrebleTA)
; Tutorial: https://www.elevenforum.com/t/add-open-in-windows-terminal-as-administrator-context-menu-in-windows-11.581/

[HKEY_CLASSES_ROOT\Directory\Shell\001flyout]
"MUIVerb"="Command Prompt"
"Icon"="imageres.dll,-5324"

[HKEY_CLASSES_ROOT\Directory\Shell\001flyout\command]
@="powershell.exe -WindowStyle Hidden \"Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','\"\"\"Command Prompt\"\"\"','-d','\"\"\"%V\\.\"\"\"')\""

[HKEY_CLASSES_ROOT\Directory\Shell\002flyout]
"MUIVerb"="PowerShell"
"HasLUAShield"=""
"Icon"="powershell.exe"

[HKEY_CLASSES_ROOT\Directory\Shell\002flyout\command]
@="powershell.exe -WindowStyle Hidden \"Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','\"\"\"Windows PowerShell\"\"\"','-d','\"\"\"%1\\.\"\"\"')\""

[HKEY_CLASSES_ROOT\Directory\Background\Shell\001flyout]
"MUIVerb"="Command Prompt"
"Icon"="imageres.dll,-5324"

[HKEY_CLASSES_ROOT\Directory\Background\Shell\001flyout\command]
@="powershell.exe -WindowStyle Hidden \"Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','\"\"\"Command Prompt\"\"\"','-d','\"\"\"%V\\.\"\"\"')\""

[HKEY_CLASSES_ROOT\Directory\Background\Shell\002flyout]
"MUIVerb"="PowerShell"
"HasLUAShield"=""
"Icon"="powershell.exe"

[HKEY_CLASSES_ROOT\Directory\Background\Shell\002flyout\command]
@="powershell.exe -WindowStyle Hidden \"Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','\"\"\"Windows PowerShell\"\"\"','-d','\"\"\"%V\\.\"\"\"')\""

Now Once I have it entered in to the reg i click the option and get a Trojan waring.

Anyone with a idea what windows is up to?

Brink · 2026-09-12T09:05:57-0400

TrebleTA said:

So I used a Reg file I copied then edited and made, from here.

Code:

Windows Registry Editor Version 5.00

; Created by: Shawn Brink Moddied By Treble TA to remove sub menus
; Created on: May 2, 2021 (07/01/2026)
; Updated on: (07/01/2026 by TrebleTA)
; Tutorial: https://www.elevenforum.com/t/add-open-in-windows-terminal-as-administrator-context-menu-in-windows-11.581/

[HKEY_CLASSES_ROOT\Directory\Shell\001flyout]
"MUIVerb"="Command Prompt"
"Icon"="imageres.dll,-5324"

[HKEY_CLASSES_ROOT\Directory\Shell\001flyout\command]
@="powershell.exe -WindowStyle Hidden \"Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','\"\"\"Command Prompt\"\"\"','-d','\"\"\"%V\\.\"\"\"')\""

[HKEY_CLASSES_ROOT\Directory\Shell\002flyout]
"MUIVerb"="PowerShell"
"HasLUAShield"=""
"Icon"="powershell.exe"

[HKEY_CLASSES_ROOT\Directory\Shell\002flyout\command]
@="powershell.exe -WindowStyle Hidden \"Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','\"\"\"Windows PowerShell\"\"\"','-d','\"\"\"%1\\.\"\"\"')\""

[HKEY_CLASSES_ROOT\Directory\Background\Shell\001flyout]
"MUIVerb"="Command Prompt"
"Icon"="imageres.dll,-5324"

[HKEY_CLASSES_ROOT\Directory\Background\Shell\001flyout\command]
@="powershell.exe -WindowStyle Hidden \"Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','\"\"\"Command Prompt\"\"\"','-d','\"\"\"%V\\.\"\"\"')\""

[HKEY_CLASSES_ROOT\Directory\Background\Shell\002flyout]
"MUIVerb"="PowerShell"
"HasLUAShield"=""
"Icon"="powershell.exe"

[HKEY_CLASSES_ROOT\Directory\Background\Shell\002flyout\command]
@="powershell.exe -WindowStyle Hidden \"Start-Process -Verb RunAs cmd.exe -ArgumentList @('/c','start wt.exe','-p','\"\"\"Windows PowerShell\"\"\"','-d','\"\"\"%V\\.\"\"\"')\""

Now Once I have it entered in to the reg i click the option and get a Trojan waring.

View attachment 182773

Anyone with a idea what windows is up to?

It's an issue with the AV when any elevated context‑menu command launches another process.

TrebleTA · 2026-09-13T13:34:31-0400

yea it very strange, it says its removed, yet soon as you use again it pops up.
Anyway to fix?

Brink · 2026-09-13T13:36:48-0400

TrebleTA said:
yea it very strange, it says its removed, yet soon as you use again it pops up.
Anyway to fix?

Not for now other than using the current version in the tutorial for a single "Open in Terminal (Admin)" context menu.

garlin · 2026-09-13T14:31:18-0400

Brink said:
Not for now other than using the current version in the tutorial for a single "Open in Terminal (Admin)" context menu.

Try this to defeat the heuristics:

Code:

@="conhost --headless powershell -C $p=@{Verb='RunAs'}; saps wt @p -a '-d \"\"\"%V\\.\"\"\"'"

1. Run powershell from "conhost --headless", so it's truly invisible (now that VBS is deprecated).
2. Hide "-Verb RunAs" as a passed command parameter.
3. Use abbreviations to confuse the heck out of the heuristics. "-a" is the shortest possible abbreviation for "-ArgumentList" since no other command options can tab-complete against it.

Personalization Add "Open in Terminal (Admin)" context menu in Windows 11

Attachments

Well-known member

My Computer My Computer

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

Active member

My Computer My Computer

At a glance

Like a rolling drone.

My Computers My Computers

At a glance

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

Active member

My Computer My Computer

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

New member

My Computer My Computer

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

New member

My Computer My Computer

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Similar Windows 11 Tutorials

My Computer

My Computers

My Computer

My Computers

My Computer

My Computers

My Computer

My Computers

My Computers

My Computer

My Computers

My Computer

My Computers

My Computer

My Computers

My Computer

My Computers

My Computer

My Computers

My Computer