Skip to content
New issue

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

Linux menu option in File Explorer not functioning properly #7845

Closed
1 of 2 tasks
gbiagini opened this issue Dec 16, 2021 · 7 comments
Closed
1 of 2 tasks

Linux menu option in File Explorer not functioning properly #7845

gbiagini opened this issue Dec 16, 2021 · 7 comments

Comments

@gbiagini
Copy link

Version

Microsoft Windows [Version 10.0.22000.376]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.60.1

Distro Version

Ubuntu

Other Software

Windows File Explorer

Repro Steps

Open File Explorer, select "Linux" from sidebar

Expected Behavior

Open Linux folder, showing Ubuntu (and other potentially installed WSL distros) folders

Actual Behavior

Error message:
"\wsl.localhost is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Insufficient system resources exist to complete the requested service."

Diagnostic Logs

dmesg |grep 9p

[    0.612346] 9p: Installing v9fs 9p2000 file system support
[    0.612359] FS-Cache: Netfs '9p' registered for caching
[    0.692744] 9pnet: Installing 9P2000 support
[    4.513151] 9pnet_virtio: no channels available for device drvfs
[    4.613289] 9pnet_virtio: no channels available for device drvfs
[    5.006581] 9pnet_virtio: no channels available for device drvfs
@gbiagini
Copy link
Author

gbiagini commented Dec 16, 2021

Removing cbfsconnect2017 from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order and HwOrder provides a temporary fix and allows the Linux menu to function, but does not persist after reboot.

Directly accessing \\wsl.localhost in the File Explorer address bar also allows access into the Linux menu, but is also only a temporary fix.

@gbiagini
Copy link
Author

The cbfsconnect2017 driver seems to be required by Box Drive. Renaming the driver in its directory seems to have solved the issue so far and persisted through reboot.

However, doing this breaks Box Drive functionality and requires the app to be deleted. It seems like it should be handled on the WSL end.

@ruderod
Copy link

ruderod commented Dec 17, 2021

so you can see linux file paths in windows explorer? i see its Build 19603 only.
https://blogs.windows.com/windows-insider/2020/04/08/announcing-windows-10-insider-preview-build-19603/

@gbiagini
Copy link
Author

so you can see linux file paths in windows explorer? i see its Build 19603 only. https://blogs.windows.com/windows-insider/2020/04/08/announcing-windows-10-insider-preview-build-19603/

Yes, I'm on Windows 11 Pro on the Insiders Beta channel, so I'm on build 22000.

As an update, the fix (removing cbfsconnect2017 from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order and HwOrder, then renaming the driver .sys file itself) has persisted since yesterday, and does not seem to have any affect on Google Drive for Desktop or OneDrive functionality that I've noticed. However, it's unfortunate to be unable to use Box Drive as well.

@gbiagini
Copy link
Author

Updating 27 days later to say that the fix has still persisted. I'm confident that the cbfsconnect2017 driver from Box Drive was the culprit for anyone interested. I've continuously used Google Drive and OneDrive and neither has produced errors.

I'm not closing the issue, because uninstalling Box Drive is a workaround, not a fix. But I imagine priority is elsewhere, given an available workaround. Maybe a workaround-available tag should be added?

@madhoun
Copy link

madhoun commented Apr 25, 2023

seems like this is still an issue - uninstalling box drive allows me to access "Linux" from sidebar in File Explorer on Windows 11 OS Build 22621.1555

Copy link
Contributor

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants