Hi all,
I have an Iventoy server running on 1.0.17 and it is working. I already successfully managed to deploy Windows 11 with and without unattend.xml answer files.
The Problem:
However, on some machines when trying to deploy either Windows 11 21H2 or 22H2, after PXE started the setup, setup claims there is no disk to be found due to a "missing driver".
The hardware to deploy to is an Asus X570 Prime and the SSD is a SATA Samsung Evo 850 1TB drive.
I have tried various options in Bios, such as enabling/disabling CSM compatibility, etc.
The weird part:
Funnily enough: the C: partition (there is an active NTFS partition on the drive with data) is even being shown during setup when you select "browse" to supply a driver for the system, so it clearly DOES see the drive.
Using the console with Shift+F10 during Windows setup I can use diskpart and it shows the drive correctly.
Just Windows setup will not accept this disk to install to and it claims there is no disk in the system.
When I run Windows 11 setup via USB stick, this error does not occur and it will detect the disk and its partitions correctly during setup -- as expected. While some exotic drivers, esp. for Raid, are sometimes to be supplied, I haven't ever had to supply a driver since Windows 10 for simple storage devices.
The question(s):
Has anyone run into a similar issue or did I miss a critical piece of documentation?
I'd be grateful for any pointers as I am stuck on this issue for 2 days straight.
---
My plan for tomorrow is to get an M2 SSD and see if the SATA makes a difference.
Maybe also try to get a newer Bios.
But that's currently all I can think of. :/
I have an Iventoy server running on 1.0.17 and it is working. I already successfully managed to deploy Windows 11 with and without unattend.xml answer files.
The Problem:
However, on some machines when trying to deploy either Windows 11 21H2 or 22H2, after PXE started the setup, setup claims there is no disk to be found due to a "missing driver".
The hardware to deploy to is an Asus X570 Prime and the SSD is a SATA Samsung Evo 850 1TB drive.
I have tried various options in Bios, such as enabling/disabling CSM compatibility, etc.
The weird part:
Funnily enough: the C: partition (there is an active NTFS partition on the drive with data) is even being shown during setup when you select "browse" to supply a driver for the system, so it clearly DOES see the drive.
Using the console with Shift+F10 during Windows setup I can use diskpart and it shows the drive correctly.
Just Windows setup will not accept this disk to install to and it claims there is no disk in the system.
When I run Windows 11 setup via USB stick, this error does not occur and it will detect the disk and its partitions correctly during setup -- as expected. While some exotic drivers, esp. for Raid, are sometimes to be supplied, I haven't ever had to supply a driver since Windows 10 for simple storage devices.
The question(s):
Has anyone run into a similar issue or did I miss a critical piece of documentation?
I'd be grateful for any pointers as I am stuck on this issue for 2 days straight.
---
My plan for tomorrow is to get an M2 SSD and see if the SATA makes a difference.
Maybe also try to get a newer Bios.
But that's currently all I can think of. :/