We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 11
26100.2605
WSL 1
Ubuntu 24.04.1 LTS
wslu v4.1.3-1
wslview stopped working when not using on a drvfs file system, i.e. it has to open a network share \\wsl$\...
\\wsl$\...
2024-12-18 16:15:08 +0100CET meinersbur@Bergufflen WSL2 ~ $ wslview . Start : Impossible d’exécuter cette commande en raison de l’erreur : Élément introuvable. Au caractère Ligne:1 : 128 + ... Text.Encoding]::GetEncoding(437); Start "\\wsl$\wsl2\home\meinersbur" + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation : (:) [Start-Process], InvalidOperationException + FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand
Reproduced in WSL1 and WSL2
Run wslview .
wslview .
explorer starts showing the contents of that directory
Issue might be powershell not working with UNC paths anymore, but maybe there is another way.
The text was updated successfully, but these errors were encountered:
patrick330602
No branches or pull requests
Windows Version
Windows 11
Windows Build Number
26100.2605
WSL Version
WSL 1
Distro Version
Ubuntu 24.04.1 LTS
WSL Utilities Version
wslu v4.1.3-1
Describe the bug
wslview stopped working when not using on a drvfs file system, i.e. it has to open a network share
\\wsl$\...
Reproduced in WSL1 and WSL2
Steps to Reproduce
Run
wslview .
Expected behavior
explorer starts showing the contents of that directory
Additional context
Issue might be powershell not working with UNC paths anymore, but maybe there is another way.
Code of Conduct
The text was updated successfully, but these errors were encountered: