Hello,
My problem is solved, it was related to the lack of loading of NVMe drivers at Windows startup.
I made my image on a workstation with NVMe disks instead of sata disks, which gets around the problem.
Hello,
My problem is solved, it was related to the lack of loading of NVMe drivers at Windows startup.
I made my image on a workstation with NVMe disks instead of sata disks, which gets around the problem.
@lebrun78
Have you found a solution to your problem?
I have the same problem with bcdedit via a snapin.
Hello,
My problem is solved, it was related to the lack of loading of NVMe drivers at Windows startup.
I made my image on a workstation with NVMe disks instead of sata disks, which gets around the problem.
Hello,
As part of the reinstallation of a computer room with Fog (with Dell Precision 5820/7960), I’m encountering a problem.
I’m making an image on Fog of a Windows and Debian dualboot workstation from a workstation with a SATA SSD.
When I deploy the image on a workstation with a SATA SSD or SATA hard disk, I don’t have any problems, I can boot into Windows and Debian.
On the other hand, when I deploy the image on a workstation with an NVMe PCIe SSD (Samsung PM9A1), it’s impossible to boot on Windows, but it boots just fine on Debian.
Windows gives me this BSOD error “INACCESSIBLE_BOOT_DEVICE”.
I thought it wasn’t loading the NVMe drivers at boot time, since the host on which I made the image doesn’t have any NVMe disks, so I did this command sc.exe config stornvme start= boot so that Windows would load the driver at boot time, but it doesn’t change anything.
In the BIOS settings, both workstations are in AHCI and not in RAID.
I’ve been racking my brains for days, but I can’t find a solution.