# Cbfs6 added to registry editor makes WSL2 Linux tree inaccessible

**URL:** <https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177>\
**Category:** General\
**Created:** [October 26, 2021, 3:40pm UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177 "2021-10-26T15:40:25Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jim](https://with.raidrive.com/letter_avatar_proxy/v4/letter/j/ac91a4/32.png) [@Jim](https://with.raidrive.com/u/Jim)\
**Post date:** [October 26, 2021, 3:40pm UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/1 "2021-10-26T15:40:25Z")

</div>

I installed RaiDrive on Windows 11 in order to access Google Drive in WSL2. However, RaiDrive makes the WSL2 Linux tree inaccessible in Windows Explorer, with an 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"

It seems that RaiDrive adds cbfs6 to HKEY\_LOCAL\_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order  
in the registry, and the addition of cbfs6 renders the WSL2 Linux tree inaccessible in Windows Explorer. If I remove cbfs6 manually from the registry, RaiDrive seems to performs correctly and WSL2 Linux tree becomes accessible, but RaiDrive would change the registry again whenever it starts. I had to uninstall RaiDrive and go back to Google Drive for Desktop.

---

<div class="post-metadata">

**Author:** ![RaiDrive](https://with.raidrive.com/user_avatar/with.raidrive.com/raidrive/32/1778_2.png) [@RaiDrive](https://with.raidrive.com/u/RaiDrive)\
**Post date:** [October 29, 2021, 2:47am UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/2 "2021-10-29T02:47:52Z")

</div>

Hi~ @Jim ,

We apologize for any inconvenience.

From what we tested internally, there were no issues with wsl2 behavior.  
I had no problems using wsl2 on windows 10 and windows 11.  
We were able to use both before and after connecting the drive and after disconnecting it.

Please be specific about what exactly you are having the problem in under what circumstances.  
It would be helpful if you send us the commands you used or screen captures.

It would also be helpful if you could send the log file(C:\ProgramData\OpenBoxLab\RaiDrive\log) by e-mail([support@raidrive.com](mailto:support@raidrive.com)).

---

<div class="post-metadata">

**Author:** ![RaiDrive](https://with.raidrive.com/user_avatar/with.raidrive.com/raidrive/32/1778_2.png) [@RaiDrive](https://with.raidrive.com/u/RaiDrive)\
**Post date:** [October 29, 2021, 5:25am UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/3 "2021-10-29T05:25:30Z")

</div>

Hi~ @Jim ,

The issue you mentioned has been reproduced.  
We will do some more internal research and report back.  
We apologize for any inconvenience.

---

<div class="post-metadata">

**Author:** ![sazonische](https://with.raidrive.com/letter_avatar_proxy/v4/letter/s/3ec8ea/32.png) [@sazonische](https://with.raidrive.com/u/sazonische)\
**Post date:** [November 30, 2021, 5:29am UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/4 "2021-11-30T05:29:06Z")

</div>

Met with the same problem, how are you progressing and are there any beta versions?

---

<div class="post-metadata">

**Author:** ![RaiDrive](https://with.raidrive.com/user_avatar/with.raidrive.com/raidrive/32/1778_2.png) [@RaiDrive](https://with.raidrive.com/u/RaiDrive)\
**Post date:** [December 2, 2021, 7:11am UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/5 "2021-12-02T07:11:33Z")

</div>

Hi~ @Jim , @sazonische .

In Windows 11, this issue occurs when cbfs6 is located in “ **Computer\HKEY\_LOCAL\_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order\NetworkProvider\Order** ” of the registry.  
If you remove the “cbfs6” item, it works normally.  
However, if you remove this, the Network Drive connected to RaiDrive in Explorer will not be visible.  
We recommend entering “\\wsl$” in the address bar of Explorer to use it.

---

<div class="post-metadata">

**Author:** ![Lucas\_Sousa\_Rosa](https://with.raidrive.com/letter_avatar_proxy/v4/letter/l/87869e/32.png) [@Lucas\_Sousa\_Rosa](https://with.raidrive.com/u/Lucas_Sousa_Rosa)\
**Post date:** [November 1, 2023, 3:44am UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/6 "2023-11-01T03:44:44Z")

</div>

Are there still no solutions to this problem?

---

<div class="post-metadata">

**Author:** ![RaiDrive](https://with.raidrive.com/user_avatar/with.raidrive.com/raidrive/32/1778_2.png) [@RaiDrive](https://with.raidrive.com/u/RaiDrive)\
**Post date:** [November 1, 2023, 7:51am UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/7 "2023-11-01T07:51:44Z")

</div>

@Lucas_Sousa_Rosa,

We’re preparing the preview version to resolve this issue and will announce soon.

---

<div class="post-metadata">

**Author:** ![3321051415](https://with.raidrive.com/letter_avatar_proxy/v4/letter/3/ecb155/32.png) [@3321051415](https://with.raidrive.com/u/3321051415)\
**Post date:** [January 16, 2024, 4:44pm UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/8 "2024-01-16T16:44:40Z")

</div>

In Windows 11, every time raidrive is started, the registry “HKEY\_LOCAL\_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order” will be changed from “P9NP,RDPNP,LanmanWorkstation,webclient” to “cbfs6,RDPNP,P9NP,LanmanWorkstation,webclient” . This will result in inability to access WSL2

---

<div class="post-metadata">

**Author:** ![RaiDrive](https://with.raidrive.com/user_avatar/with.raidrive.com/raidrive/32/1778_2.png) [@RaiDrive](https://with.raidrive.com/u/RaiDrive)\
**Post date:** [January 17, 2024, 7:34am UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/9 "2024-01-17T07:34:07Z")

</div>

Hi~ @3321051415,

You’re right. It is the limitation of CBFS6. (device driver)  
We’re preparing a new product to solve this issue.

---

<div class="post-metadata">

**Author:** ![Vigilans](https://with.raidrive.com/user_avatar/with.raidrive.com/vigilans/32/1723_2.png) [@Vigilans](https://with.raidrive.com/u/Vigilans)\
**Post date:** [June 14, 2024, 7:07am UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/10 "2024-06-14T07:07:57Z")

</div>

Cbfs6 also causes following issue:

> <https://github.com/microsoft/Windows-Containers/issues/200>
>
> This is a repost from https://github.com/docker/for-win/issues/12520, where I wa…s referred to this project instead.
> 
> \### Actual behavior
> Trying to build a Windows-based container results in the following error every time:
> 
> hcsshim::PrepareLayer - failed failed in Win32: Incorrect function. (0x1)
> 
> I have tried this with both windows/nanoserver and windows/servercore images
> 
> \### Expected behavior
> 
> A successful Dockerfile build without this error
> 
> \### Information
> \<!--
> Please, help us understand the problem. For instance:
> - Is it reproducible? Yes, every time
> - Is the problem new? This is my first time trying windows containers, so I'm not sure
> - Did the problem appear with an update? I've only used this version of docker
> - A reproducible case if this is a bug, Dockerfiles with reproduction inside is best.
> \--\>
> - Windows Version: Windows 10 Pro, 10.0.19041 Build 19041
> - Docker Desktop Version: 4.4.4 (73704)
> - WSL2 or Hyper-V backend? Hyper-V
> - Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No, just a local PC
> 
> \### Output of \`& "C:\\Program Files\\Docker\\Docker\\resources\\com.docker.diagnose.exe" check\`
> 
> \[027:08:49:15.140\]\[I\] ipc.NewClient: fc62ff43-com.docker.diagnose -\> \\\\.\\pipe\\dockerBackendV2 com.docker.service.exe
> \[goroutine 1 \[running, locked to thread\]:
> \[win/backend/pkg/service.NewClientForPath(...)
> \[ win/backend/pkg/service/service.go:40
> \[win/backend/pkg/service.NewClient({0x118e8be, 0x13}, {0x0, 0x0, 0x0})
> \[ win/backend/pkg/service/service.go:29 +0xe8
> \[common/pkg/diagkit/gather/diagnose.init()
> \[ common/pkg/diagkit/gather/diagnose/ipc\_windows.go:23 +0x11f
> Starting diagnostics
> 
> \[PASS\] DD0027: is there available disk space on the host?
> \[PASS\] DD0028: is there available VM disk space?
> \[PASS\] DD0031: does the Docker API work?
> \[PASS\] DD0004: is the Docker engine running?
> \[PASS\] DD0011: are the LinuxKit services running?
> \[PASS\] DD0016: is the LinuxKit VM running?
> \[PASS\] DD0001: is the application running?
> \[SKIP\] DD0018: does the host support virtualization?
> \[PASS\] DD0002: does the bootloader have virtualization enabled?
> \[PASS\] DD0017: can a VM be started?
> \[PASS\] DD0023: is the Containers Windows Feature enabled?
> \[PASS\] DD0015: are the binary symlinks installed?
> \[PASS\] DD0003: is the Docker CLI working?
> \[PASS\] DD0013: is the $PATH ok?
> \[PASS\] DD0005: is the user in the docker-users group?
> \[PASS\] DD0007: is the backend responding?
> \[PASS\] DD0014: are the backend processes running?
> \[PASS\] DD0008: is the native API responding?
> \[PASS\] DD0009: is the vpnkit API responding?
> \[PASS\] DD0010: is the Docker API proxy responding?
> \[PASS\] DD0006: is the Docker Desktop Service responding?
> \[PASS\] DD0012: is the VM networking working?
> \[PASS\] DD0032: do Docker networks overlap with host IPs?
> \[SKIP\] DD0030: is the image access management authorized?
> \[PASS\] DD0033: does the host have Internet access?
> No fatal errors detected.
> 
> \### Steps to reproduce the behavior
> \<!--
> A reproducible case, Dockerfiles with reproduction inside is best.
> \--\>
> 
> 
> Step 1: Create this Dockerfile:
> \`\`\`
> FROM mcr.microsoft.com/windows/nanoserver:10.0.19041.1415-amd64
> 
> RUN echo hello
> 
> RUN echo goodbye
> 
> CMD \["cmd.exe" \]
> \`\`\`
> 
> 
> Step 2: Execute the following command from in the same directory:
> 
> docker build .
> 
> 
> I get the following output every time:
> 
> \> Sending build context to Docker daemon 3.473GB
> \> Step 1/4 : FROM mcr.microsoft.com/windows/nanoserver:10.0.19041.1415-amd64
> \> ---\> c7d5f0d992fa
> \> Step 2/4 : RUN echo hello
> \> ---\> Running in b1ed8fa3108b
> \> hello
> \> 
> \> hcsshim::PrepareLayer - failed failed in Win32: Incorrect function. (0x1)

The existence of cbfs6 will cause docker’s windows image building to fail. After uninstalling raidrive, the cbfs6 driver is gone and the building can succeed.

The cbfs6 is observed through `driverquery /v`:

> cbfs6 cbfs6 cbfs6 Kernel System Running OK TRUE FALSE 294,912 49,152 0 9/21/2016 08:42:02 PM ??\C:\WINDOWS\system32\drivers\cbfs6.sys 24,576

---

<div class="post-metadata">

**Author:** ![RaiDrive](https://with.raidrive.com/user_avatar/with.raidrive.com/raidrive/32/1778_2.png) [@RaiDrive](https://with.raidrive.com/u/RaiDrive)\
**Post date:** [November 11, 2024, 9:40am UTC](https://with.raidrive.com/t/cbfs6-added-to-registry-editor-makes-wsl2-linux-tree-inaccessible/5177/11 "2024-11-11T09:40:49Z")

</div>

@3321051415, @Vigilans, @Lucas_Sousa_Rosa, @sazonische, @Jim,

Thank you for waiting for a long time.  
RaiDrive released the preview version to resolve this issue.

> [@RaiDrive Preview 2024.11.11](https://with.raidrive.com/t/raidrive-preview-2024-11-11/9273):
>
> RaiDrive Preview 2024.11.11 New Windows Subsystem for Linux support Dev Drive support Download [https://www.raidrive.com/download/preview](https://www.raidrive.com/download/preview)