Open prosinger opened 2 months ago
Do you have secure boot enabled? Winbtrfs does not work with secure boot, presumably because the driver is not signed.
I am running this and it works fine as long as secure boot is disabled: Edition Windows 11 Pro Version 23H2 Installed on 8/8/2023 OS build 22635.4082 Experience Windows Feature Experience Pack 1000.22700.1038.0
That refers to Windows 10. Does it work in 11? That registry entries basically disables Window's requirement for signed drivers, similar to disabling secure boot in BIOS.
I actually don't care that much one way or the other about secure boot, it's what you would use on your Mom's system to prevent her from loading spyware. There is a way, search for "attestation signing", but it's not easy (or free) for a solitary developer to achieve. Maybe the open source community will eventually agree on a framework for signing 3rd party Windows drivers similar to what Fedora has done.
Maybe the open source community will eventually agree on a framework for signing 3rd party Windows drivers similar to what Fedora has done.
This seems unlikely. The number of open-source Windows drivers is insignificant and AFAIK none of them have consistent funding. There will of course always be ways to load unsigned (or signed with a non-Microsoft approved signing certificate) drivers, but this will likely cause issues that are dealbreakers for a significant chunk of users (e.g. most major game anti cheats would likely refuse to run).
Do you have secure boot enabled? Winbtrfs does not work with secure boot, presumably because the driver is not signed.
I am running this and it works fine as long as secure boot is disabled: Edition Windows 11 Pro Version 23H2 Installed on 8/8/2023 OS build 22635.4082 Experience Windows Feature Experience Pack 1000.22700.1038.0
I don't have secure boot set up. Linux doesn't work with it (at least I think so), and I'm sharing a btrfs parittion between Lin and Win. It just stopped working when this new update kicked in for Win11 I have tried to remove the driver and set it up again, but same thing happens. It doesn't see the device anymore
That refers to Windows 10. Does it work in 11?
Yes,I can using,what about you?
Linux doesn't work with it
Depends. Debian and Ubuntu work with it for sure.
That refers to Windows 10. Does it work in 11?
I wrote that before Windows 11 came out, and as far as I'm aware it's still the case.
That registry entries basically disables Window's requirement for signed drivers, similar to disabling secure boot in BIOS.
This is not true. It makes it so Windows only requires drivers to be signed with normal certificates, not EV ones.
Same here, it was working for me but then it stopped after an update. I made sure the reg key was still set, I had core isolation enabled but after disabling it it still didn't work.
I've just tried installing the driver on a fresh install of Windows 11 24H2 (10.0.26100.863) and everything worked fine.
I just did an install on Windows 11 build 22631.4169 and the winbtrfs driver did not work with secure boot enabled. However, as soon as I disabled secure boot, it worked just fine. I can now share nicely between Linux and Windows. If you have issues, I would suggest double-checking the bios settings to ensure secure boot is in fact disabled. I have not tried the workaround for Windows 10, so it may be it is possible to get both secure boot and btrfs. I will try at some point and revert.
I've updated the README to say that although Windows 11 pretends that it needs Secure Boot, it doesn't really and will work fine with it turned off.
I can confirm that I don't have secure boot set up (keys deleted), and Fast boot disabled, but it doesn't work ever since the update
my setup is BTRFS raid0 though, that might be different compared to others
Eventlog:
The btrfs service failed to start due to the following error: The system cannot find the device specified.