-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Cannot change directory into wsl distro #15773
Copy link
Copy link
Closed
Labels
Area-FileSystem-Providerspecific to the FileSystem providerspecific to the FileSystem providerNeeds-ReproThe issue author needs to provide repro steps.The issue author needs to provide repro steps.Resolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or more
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
This issue was supposedly fixed #10674
However, I am still seeing the exact same issue described in #10360 and #15497.
Expected behavior
PS C:\Users> cd //wsl$/fedoraremix/
PS Microsoft.PowerShell.Core\FileSystem::\\wsl$\fedoraremix>Actual behavior
PS C:\Users> cd //wsl$/fedoraremix/
Set-Location: Cannot find path '//wsl$/fedoraremix/' because it does not exist.Error details
Set-Location: Cannot find path '//wsl$/fedoraremix/' because it does not exist.Environment data
PS> $psversiontable
Name Value
---- -----
PSVersion 7.2.0-preview.7
PSEdition Core
GitCommitId 7.2.0-preview.7
OS Microsoft Windows 10.0.19042
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0and
Name Value
---- -----
PSVersion 7.1.3
PSEdition Core
GitCommitId 7.1.3
OS Microsoft Windows 10.0.19042
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area-FileSystem-Providerspecific to the FileSystem providerspecific to the FileSystem providerNeeds-ReproThe issue author needs to provide repro steps.The issue author needs to provide repro steps.Resolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or more