starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

WSL under Terminal (preview) exposes Windows file system. #9234

New Issue
Closed
opened 2026-01-31 01:49:18 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 01:49:18 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Jun 24, 2020).

Environment

Microsoft Windows [Version 10.0.19041.329]
Windows Terminal version: latest preview build downloaded via Microsoft Store.
Widows Command Prompt

Steps to reproduce

Expected behavior

When I run the "ls" command under WSL running with Windows Terminal it should only show the files related to that WSL instance as it works under "Command Prompt".

Actual behavior

The entire file listing and hierarchy of all files (including files belonging to Windows) in that directory is shown.

Originally created by @ghost on GitHub (Jun 24, 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 Microsoft Windows [Version 10.0.19041.329] Windows Terminal version: latest preview build downloaded via Microsoft Store. Widows Command Prompt ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> # Expected behavior When I run the "ls" command under WSL running with Windows Terminal it should only show the files related to that WSL instance as it works under "Command Prompt". # Actual behavior The entire file listing and hierarchy of all files (including files belonging to Windows) in that directory is shown.
claunia commented 2026-01-31 01:49:19 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 24, 2020):

This is by design. Filesystem interoperability is one of the main features of WSL - this means you can use linux tools with you Windows files, and vice-versa.

If you have any other WSL questions, https://github.com/microsoft/WSL would be the appropriate place to ask.

@zadjii-msft commented on GitHub (Jun 24, 2020): This is by design. Filesystem interoperability is one of the main features of WSL - this means you can use linux tools with you Windows files, and vice-versa. If you have any other WSL questions, https://github.com/microsoft/WSL would be the appropriate place to ask.
claunia commented 2026-01-31 01:49:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 24, 2020):

What part of our documentation made you believe that WSL would be isolated from Windows, and that this was a bug? I'd like to bring it to the attention to the WSL team to make sure we're communicating effectively.

@DHowett commented on GitHub (Jun 24, 2020): What part of our documentation made you believe that WSL would be isolated from Windows, and that this was a bug? I'd like to bring it to the attention to the WSL team to make sure we're communicating effectively.
claunia commented 2026-01-31 01:49:20 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 25, 2020):

It's not that WSL "would" be isolated, but that bug-report stems from my belief that WSL "should" be isolated from the rest of the Windows file-system. For one thing, the "file structure" differs between Windows and Linux, secondly, since one is essentially running Linux in a virtual machine (WSL) why should the inner OS have access to the file-system of the master OS?

@ghost commented on GitHub (Jun 25, 2020): It's not that WSL "would" be isolated, but that bug-report stems from my belief that WSL "should" be isolated from the rest of the Windows file-system. For one thing, the "file structure" differs between Windows and Linux, secondly, since one is essentially running Linux in a virtual machine (WSL) why should the inner OS have access to the file-system of the master OS?
claunia commented 2026-01-31 01:49:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 25, 2020):

The by-default resource sharing is one of the core tenets of WSL. It’s not a primary/secondary OS situation, it’s intended to enable hybrid workflows that span both operating systems.

You can disable the integration, but since this is the terminal repo and it’s late in the evening I’ll have to direct you to the WSL docs to learn how 😄

@DHowett commented on GitHub (Jun 25, 2020): The by-default resource sharing is one of the core tenets of WSL. It’s not a primary/secondary OS situation, it’s intended to enable hybrid workflows that span both operating systems. You can disable the integration, but since this is the terminal repo and it’s late in the evening I’ll have to direct you to the WSL docs to learn how :smile:
claunia commented 2026-01-31 01:49:20 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 25, 2020):

If by-default resource sharing is one of the core tenets of WSL and this so-called feature (which you categorize as "not bug") isn't being considered a Terminal related issue, then why is it so that this so-called feature of "WSL" is only available under Terminal and absolutely absent under "Command Prompt"?
I think you people are confused about the situation.
It's high time you exhibited maturity and got your act straight.

@ghost commented on GitHub (Jun 25, 2020): If by-default resource sharing is one of the core tenets of WSL and this so-called feature (which you categorize as "not bug") isn't being considered a Terminal related issue, then why is it so that this so-called feature of "WSL" is only available under Terminal and absolutely absent under "Command Prompt"? I think you people are confused about the situation. It's high time you exhibited maturity and got your act straight.
claunia commented 2026-01-31 01:49:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 25, 2020):

I'd just like to take a quick moment to remind to you please make sure you're following our code of conduct when contributing here. There's clearly a bit of a misunderstanding in this thread, no need to resort to insults.

Is what you're really reporting that wsl from cmd.exe gives different results for ls than when run from the Terminal?
image

That's certainly highly unusual. Perhaps you've got multiple different distros configured? Could you share the output of wsl -l?

@zadjii-msft commented on GitHub (Jun 25, 2020): I'd just like to take a quick moment to remind to you please make sure you're following our [code of conduct](https://opensource.microsoft.com/codeofconduct/) when contributing here. There's clearly a bit of a misunderstanding in this thread, no need to resort to insults. Is what you're really reporting that `wsl` from `cmd.exe` gives different results for `ls` than when run from the Terminal? ![image](https://user-images.githubusercontent.com/18356694/85724288-afa12500-b6b9-11ea-86eb-d1f7c3cdae52.png) That's certainly highly unusual. Perhaps you've got multiple different distros configured? Could you share the output of `wsl -l`?
claunia commented 2026-01-31 01:49:21 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 25, 2020):

Firstly, I apologise for uttering harsh words towards the glorious work being done by a bunch of snowflakes.
Secondly, after this comment, I pledge never to turn brutal in spite of any moronic behaviour exhibited by any of those who'eve pledged allegiance to your "code of conduct".
Third, I am now proceeding with a reinstall of my Windows 10 system from scratch, I'll run the tests you've asked me to and submit the results at the earliest which might help you deliver an improved product.

@ghost commented on GitHub (Jun 25, 2020): Firstly, I apologise for uttering harsh words towards the glorious work being done by a bunch of snowflakes. Secondly, after this comment, I pledge never to turn brutal in spite of any moronic behaviour exhibited by any of those who'eve pledged allegiance to your "code of conduct". Third, I am now proceeding with a reinstall of my Windows 10 system from scratch, I'll run the tests you've asked me to and submit the results at the earliest which might help you deliver an improved product.
claunia commented 2026-01-31 01:49:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 25, 2020):

See, I don't think that "be respectful" is too much to ask. That's like, human decency 101. If you want more help on this issue, you can either try to show some basic respect for the people you're working with, or I'm gonna have to lock this thread. Thanks!

@zadjii-msft commented on GitHub (Jun 25, 2020): See, I don't think that "be respectful" is too much to ask. That's like, human decency 101. If you want more help on this issue, you can either try to show some basic respect for the people you're working with, or I'm gonna have to lock this thread. Thanks!
claunia commented 2026-01-31 01:49:21 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (Jun 25, 2020):

@mayureshkathe It seems your magnificent intellect is being underutilized by way of repeated feeble attempts to troll the developers. Perhaps it would be better spent on discerning an optimal solution to the core problems of the troubled Korean Armistice Agreement, or maybe unravelling the secrets of the Riemann Hypothesis.

Or, you could spend ten or twenty minutes challenging your own assumptions about the goals of WSL.

@oising commented on GitHub (Jun 25, 2020): @mayureshkathe It seems your magnificent intellect is being underutilized by way of repeated feeble attempts to troll the developers. Perhaps it would be better spent on discerning an optimal solution to the core problems of the troubled Korean Armistice Agreement, or maybe unravelling the secrets of the Riemann Hypothesis. Or, you could spend ten or twenty minutes challenging your own assumptions about the goals of WSL.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Needs-Tag-Fix Needs-Triage Product-WSL Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9234
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?