btrfs

btrfs copied to clipboard

I am using Windows 10 (Version 10.0.18362 Build 18362) and after install driver I see it in device manager and regedit but I don't see a volume (e.g. in explorer). Thanks in advance for any help.

Do you have a disk already formatted as BTRFS?

Yes

Is the Btrfs controller showing in Device Manager with no exclamation point?

Yes, there it is. Without any problem (reported by Windows).

Weird. Please try the new release and see if that fixes it.

I'm afraid @MegaZeroX10 doesn't really know how to help here.

If you don't see it in this menu (as an unknown file system or as BTRFS) then your computer likely isn't seeing the drive My only other suggestion is to open diskpart, type list disk, then plug your device in, and then list the devices again. If you don't see another one pop up, there's an issue between the computer and the drive that is not related to the driver. Note: if it's a SATA drive, make sure you have hot swapping on before you plug it in, or plug it in with the computer off.

I can see it in diskmgr. Every partition is blank in FS column.

EDIT: I checked with new version. Without changes. Problem is still.

I'm experiencing this problem in Windows Server 2003 when using v1.5. The Disk with the BTRFS partition shows up in Disk Management but I can't assign a drive letter to it (no dialog box shows when I try to do it).

The same issue occurs in Windows 7 but the driver is able to assign a drive letter to the partition.

I have the same issue on one of my systems and it only affects SATA and Nvme drives, Btrfs partitions on USB drives work fine. I also tried versions 1.7 and 1.6 of WinBtrfs, but that didn't fix it.

Btrfs partitions on the virtual drive from my RAID controller are also not recognized. The RAID controller doesn't cause this problem, the issue persists when I remove it. I will try a fresh Windows installation on the same machine when I have the time.

@damian101: The version 1.7 had some problems, try with 1.7.1

@ale5000-git I did. I just tried 1.7 and 1.6 after 1.7.1 failed, to see if they maybe work.

@damian101, what's your RAID controller? Is this hardware or software RAID?

@It's a hardware raid controller, Fujitsu D3116, with the LSI SAS 2208 ROC.

I'm experiencing this problem in Windows Server 2003 when using v1.5. The Disk with the BTRFS partition shows up in Disk Management but I can't assign a drive letter to it (no dialog box shows when I try to do it).

I tried using v1.7.1 and am still having the issue being mentioned. I also get a "DiskPart could not assign the drive letter or mount point. Make sure the drive letter or mount point is valid." when I try assigning a drive letter using DiskPart.

After having the first BSOD described in #246, all the Btrfs partitions now show up, including the Btrfs partition on the virtual drive of my hardware RAID controller.

Maybe this will fix the issue being discussed:

1. Open a Command Prompt ran as Administrator.
2. Run diskpart.
3. Type automount enable and press Enter.
4. Type exit and press Enter.
5. Close the Command Prompt window.

I have same issue. On Thinkpad 10 tablet with eMMC. One part is ntfs(windows 10) and the second is btrfs.

Properties in the menu are not active.

Also I have same issue on my laptop with nvme samsung 970 evo.

UPDATED:

Open a Command Prompt ran as Administrator. Run diskpart. Type automount enable and press Enter. Type exit and press Enter. Close the Command Prompt

After apply this and REBOOT second drive appeared in explorer. I will try this on my laptop later.

Maybe this will fix the issue being discussed:

1. Open a Command Prompt ran as Administrator.

2. Run diskpart.

3. Type automount enable and press Enter.

4. Type exit and press Enter.

5. Close the Command Prompt window.

Didn't work here on Widnows 10 1909 build 18363.1316, even after reboot

Same issue on Windows 7. I converted an EXT4 partition to BTRFS via btrfs-convert on Linux and it's not showing up on Windows. But before this, I've tried with a removable USB drive formatted to BTRFS via GParted and it worked flawlessly.

Btrfs Controller is shown in Device Manager. Diskpart does not show the BTRFS volume (and is running very slow for some reason). However, the Disk Management tool does show it but does not allow me to change its drive letter, only allows to delete it.

WinBtrfs 1.7.9 Windows 7 6.1.7601 Service Pack 1 Build 7601 x64

Same issue occurred to me after I disabled CSM and enabled secureboot via bios, I suspect it was caused by the signed btrfs driver.

Same issue occurred to me after I disabled CSM and enabled secureboot via bios, I suspect it was caused by the signed btrfs driver.

Confirmed fixed with secureboot enabled by writing the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CI\Policy DWORD -> UpgradedSystem VALUE -> 1

Maybe this will fix the issue being discussed:

1. Open a Command Prompt ran as Administrator.
2. Run diskpart.
3. Type automount enable and press Enter.
4. Type exit and press Enter.
5. Close the Command Prompt window.

This work for me on Windows 8.1

Closing old issues

Maybe this will fix the issue being discussed:

1. Open a Command Prompt ran as Administrator.

2. Run diskpart.

3. Type automount enable and press Enter.

4. Type exit and press Enter.

5. Close the Command Prompt window.

It is tragi-comic that in 2024 with such a mature, stable code, MS Windows 10 (not winbtrfs) randomly turns off that automount and you are stuck completely clueless staring to screen wondering why BTRFS drive with 1TB of data doesn't show up. Especially when you are messing with Gentoo Linux install :-)

@maharmstone I can't really ask a deep level system driver developer to fiddle with UI etc but, is there a chance to check this issue deeper if we provide all the information etc? I suspect Windows 10 core however it won't likely get anything except security updates. I don't want you or anyone to hack/patch crazy things to fix their bug, but there must be something to do. For example, a command/registry key user can change so that automount setting sticks.

Gentoo made me enter many fdisk etc interaction and I almost had heart-attack when I saw drive missing (I obviously back it up to gdrive via duplicati) . A less experienced user can seriously panic.