Thank you for checking on this, and affirming that this is not happening on your side!
To confirm, I have been mapping the WSL directory using the following command and have also rebooted the machine:
net use W: \\wsl.localhost\WLinux /user:myusername
----
I found the answer to my own question: I was launching the first instance of Total Commander differently from the subsequent ones.
I used the following AHK (v1) script to start the first instance of Total Commander. However, I launched subsequent instances manually without AHK by emulating control-clicks on Total Commander's system tray icon. More specifically, since I had pinned TC as the first icon on the taskbar, I used Shift + Win + 1 to open additional instances.
The intention behind this approach was to launch Total Commander without admin privileges since my AHK script runs with elevated permissions. However, using RunAs in this way seems to have caused the initial instance of Total Commander to display "broken" network drives, and to completely fail at connecting to WSL directories.
To confirm, I have been mapping the WSL directory using the following command and have also rebooted the machine:
net use W: \\wsl.localhost\WLinux /user:myusername
----
I found the answer to my own question: I was launching the first instance of Total Commander differently from the subsequent ones.
I used the following AHK (v1) script to start the first instance of Total Commander. However, I launched subsequent instances manually without AHK by emulating control-clicks on Total Commander's system tray icon. More specifically, since I had pinned TC as the first icon on the taskbar, I used Shift + Win + 1 to open additional instances.
Code:
RunAs, username, password Run "C:\Program Files\totalcmd\TOTALCMD.EXE" RunAsStatistics: Posted by llinfeng — 2025-02-16, 23:43 UTC