wslview stopped working in 24H2

[Meinersbur]

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$\...

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

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

• I agree to follow this project's Code of Conduct

[brozkeff]

Just upgraded one company PC to 24h2 and discovered this bug and confirm it worked OK on 22H2 and 23H2 and stopped on 24H2. I upgraded older wslu to latest version from the ppa apt repo, no change.

Start : This command cannot be run due to the error: Prvek nebyl nalezen. At line:1 char:128 + ... oding(852); Start "\\wsl$\REDACTED ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Start-Process], InvalidOperationException + FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand

Currently I applied workaround by not displaying PDF from wsl via wslview but directly via explorer.exe in a following manner. Not optimal as it does not open users' default pdf viewer but Edge but until the issue is fixed this is the method I use to make our scripts using wslview work at least somehow:

WIN_PATH=$(wslpath -w "${SCRIPT_DIR}/${PDF_FILE}")
explorer.exe "${WIN_PATH}"`