Elevated permissions do not pass through Windows Terminal in some cases #7001

Open
opened 2026-01-31 00:52:39 +00:00 by claunia · 0 comments
Owner

Originally created by @WSLUser on GitHub (Mar 19, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.720]
Windows Terminal version (if applicable): 0.10.761.0

Any other software?

WSL

Steps to reproduce

Enable WSL. Install a distro from the Store. Doesn't matter which one. Follow the account setup procedure. Close the window and open WT in elevated mode (Right click and Runas Administrator)and verify it shows in the drop down menu. Use default tab or open a new one (cmd, PS, WSL Distro). Run wsl.exe --export Distroname (as reported in wsl --list) C:\User\user\Desktop\SomeFilename.tar

Expected behavior

I expect the export to be successful.

Actual behavior

Permission Denied.

Compared to Conhost only Window: If I open an elevated CMD window and run the command, It works as intended. This shows that for some reason, even when WT is running in elevated mode, the shells are running in non-elevated mode. Possible cause for regression: #4874

Originally created by @WSLUser on GitHub (Mar 19, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.720] Windows Terminal version (if applicable): 0.10.761.0 Any other software? ``` WSL # Steps to reproduce <!-- A description of how to trigger this bug. --> Enable WSL. Install a distro from the Store. Doesn't matter which one. Follow the account setup procedure. Close the window and open WT in elevated mode (Right click and `Runas Administrator`)and verify it shows in the drop down menu. Use default tab or open a new one (cmd, PS, WSL Distro). Run `wsl.exe --export Distroname` (as reported in `wsl --list`) C:\User\user\Desktop\SomeFilename.tar # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> I expect the export to be successful. # Actual behavior <!-- What's actually happening? --> Permission Denied. Compared to Conhost only Window: If I open an elevated CMD window and run the command, It works as intended. This shows that for some reason, even when WT is running in elevated mode, the shells are running in non-elevated mode. Possible cause for regression: #4874
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7001