Best posts made by ldiorio

@george1421 Update.

So we did some more testing and it turns out that the Intel Volume Management Device setting in our system BIOS is whats causing the issue with our NVMe drive. We found this because even after getting FOG to successfully push an image to the drive, Windows was unable to boot from it. We disabled the VMD setting and the PCI device is no longer addressed on an extended root hub and Windows booted normally, so we tested this with the orignal bzImage as well and it all still works as expected.

@george1421 Alright, just as a note I did some further testing by mixing different refind binaries and conf files. It seems something from the conf file in the dev branch is whats causing the issue because I was able to boot properly by using the master branch conf regardless of the refind binary being used.

@george1421 I did, one of the first issues I had (and this was before I even started having a problem with Windows booting) was in the new conf the ‘scanfor internal’ option was changed to ‘scanfor internal,hdbios’ which caused refind to look for BIOS boot loaders as well. That caused an immediate interrupt on my systems because they are all EFI with CSM disabled. I manually changed that line to get rEFInd to work properly, and it was at that point that I ran into the issues with Windows.

So I did more testing with the conf files now, and it seems that the scan delay is whats causing the issue. I downloaded a fresh copy of the refind binary and conf from the FOG dev-branch and made the scanfor line change as well as commented out the ‘scan_delay 5’ line. As of now, the configuration is working.