Unable to boot: `EFI_INVALID_PARAMETER`

[clansty]

I tried to boot Win11 22H2 and Win10 20H1. They are all unable to boot and reports: EFI_INVALID_PARAMETER. I think it's not error about versions.

I boot windows from a subvolume of my btrfs partitition, after install windows and btrfs driver and then rsync the system from Linux. And the compress of btrfs is on, zstd:3.

freeldr.ini

[FREELOADER]
TimeOut=10
DefaultOS=Windows

[Operating Systems]
Windows="Windows"
Windows_Debug="Windows (Debug)"

[Windows]
SystemPath=btrfs(e63aab1d-0a59-4c43-9fb6-ab92dd897378)\Windows
Options=/SUBVOL=11a

[Windows_Debug]
...

btrfs subvol list

ID 256 gen 47987 top level 5 path @
ID 257 gen 47987 top level 5 path @home
ID 258 gen 47987 top level 5 path @root
ID 259 gen 47987 top level 5 path @srv
ID 260 gen 47987 top level 5 path @logs
ID 261 gen 47987 top level 5 path @pkgs
ID 262 gen 36182 top level 256 path @/var/lib/portables
ID 263 gen 36182 top level 256 path @/var/lib/machines
ID 264 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/2f5769bfb2ef300ada9a93edf2b9d1b9b5657105d5108a3425765296fc13355d
ID 265 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/4b8024bbd3d27e4baaf3ae259730a8c2d12682a4f1487329152d96771b7abb46
ID 266 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/318fb7c9558d949e9f897c6b1637e1430206e9307e05fdd58fabac107beb4820
ID 267 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/8fff223b6e8e4ce76200b1312aba93fd7583d3c9be087627b23b770c8ea06494
ID 268 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/aeb994e8cbdcd0c6baf0cf102182653c5a9832bee8596df18135592e804515cd
ID 269 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/5ab05c750b3af63cf8a951c02635de3ac194b1003b705884af3cafb4859970ce
ID 270 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/20219a64ff7dce116699f5f5cd6e6be80b1e3c988f8d2cd62984dbcdd7a3cf1f
ID 271 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/1f0052cb4cb8638174aa7cedc6d0d065cbc53ed9c07e0c6833e7b1f6948d83b9
ID 272 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/b5d466b95e88da8db61a0e4e56cf290e70ae1988a2b225bc8a7c92c2f90ef6ba
ID 273 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/98e185843c874192e4615334fd1d09ca3e7f546d255b3db555cf8e13138a9a7f
ID 274 gen 36182 top level 256 path @/var/lib/docker/btrfs/subvolumes/0ee288ce7acb39fa8992a5fea372a1e11f94ff90ce866d0203a9436c3f57c153
ID 275 gen 47987 top level 5 path @nixos
ID 276 gen 48244 top level 275 path @nixos/@
ID 277 gen 48244 top level 275 path @nixos/@home
ID 278 gen 47609 top level 276 path @nixos/@/srv
ID 279 gen 36817 top level 276 path @nixos/@/var/lib/machines
ID 280 gen 48137 top level 276 path @nixos/@/tmp
ID 281 gen 48008 top level 5 path @windows
ID 282 gen 48179 top level 5 path @windows10

boot error

[maharmstone]

Support for both these versions hasn't been implemented yet.

[clansty]

Oh, I made a typo, the Win10 version I installed is 20H1, and I tried both the binary in release and the binary built from latest source with Visual Studio.

[clansty]

I tried to use ntfs2btrfs to convert the partition to btrfs, and start quibble directly instead of chainloading from systemd-boot, but the result is same.

Is there any way to get a detailed log?

[i2]

I also think getting a detailed log would be helpful in diagnosing what might be the root of non-bootable setups. Thanks!