We have seen circumstantial evidence of WD drives causing issues. Circumstantial evidence is not scientific, however, so we cannot say with certainty whether those drives are incompatible or problematic. We should also check if SATA Mode is set to AHCI in BIOS Setup.
This is a tricky issue. Do you still have your OC 0.6.1 EFI folder? If so, please give it another try to confirm that Windows is able to boot directly from OC Picker. If it works, please compress and post the OC 0.6.1 folder (you may remove serial numbers from config.plist).
Again, we have circumstantial evidence to suggest that WD drives may be problematic. Do you have a third NVMe SSD that is not a WD brand?
Yes I still have 0.6.1 and Windows boots fine. I can attach it. However, I don't have the OpenCore tool for 0.6.1. I have the latest one for 0.6.5. So I am concerned that, if I edit that 0.6.1 with OpenCore to remove the serials and save it, it will screw up the format. I can also edit the config.plist with plist editor if that's better.
Regarding the NVMe, I have one spare Samsung EVOo + 250GB which is the one I used to clone the Sabrent one (since I thought that maybe it would fix the pb.
The current config is:
- slot 1: EVO + 1TB macOS
- slot 2: WD SN750 1TB
- slot 3: Sabrent 500GB Windows 10
- PCIe x4 adapter: empty
if I swap slot 2 and 3 (or move the WD to the PCIe x4 adapter, the system does not start.
In previous config I had:
- slot 1: EVO + 1TB macOS
- slot 2: EVO + 250GB Windows 10
- slot 3: empty
- PCIe x4 adapter: WD SN750 1TB
With the WD in slot 3, the system would not start.
It is hard to find a pattern because there have been combinations where the WD remained in the PCIe x4 adapter and the issue was coming from the NVMe disks slotted in slots 1 to 3.
