[BUG] WSL mounted drive roots fail to render content in V4 compared to V3 functionality

[BabakAmini]

Application Version

0.0.47.0

Operating System

Windows 11

Description

Unlike V3, the root directories of mounted WSL drives do not list any files or folders in One Commander V4. However, manually navigating deeper past the root mount point (e.g., into Ubuntu-26.04 subfolder) restores normal folder display operations.

Steps to Reproduce

1. Open the root mount path of a WSL instance inside One Commander V4.
2. Notice the panel structure displays as completely empty.
3. Manually type or navigate deeper into a specific distribution subfolder (e.g., ...\Ubuntu-26.04\).

Expected Behavior

No response

[m1l]

I just installed wsl and Ubuntu and it shows up

But I will make some changes in .47 so once you update please let me know if the issue persists

[BabakAmini]

Do you mean 0.0.48.0? I am using 0.0.47.0 right now.

[BabakAmini]

Still have the same issue after upgrading to 0.48.

[m1l]

\wsl.localhost is a special WSL filesystem provider exposed through Windows UNC semantics, OC just asks for content and doesn't do anything special compared to other folders. Try also \wsl$ . Both list Ubuntu for me, so I need a way to reproduce it to be able to look for workarounds. All I did it typed wsl in terminal, restarted when it asked and on next start installed Ubuntu from MS Store

[BabakAmini]

I just tried \wsl$, but I'm still getting the same issue in V4. I wish I could give you a way to reproduce it.

[m1l]

I think I know the reason it worked in v3. It used WinRT APIs Windows.Storage. I currently don't plan on including that because it is a huge payload just for one small task. I'll look for an alternative , but I'll have to put it as low priority for now as it affects only tiny percentage of users