![]() When you get this error message, it is possible to work around it easily without having to use diskpart or manually re-partition your disks and drives: The easiest solution for this error is to force Windows to re-arrange its ordering of the drives. Fixes for this error Fix #1: Eject and re-insert the USB If Windows setup cannot reliably determine which is the boot drive, this error will appear. Also, some USB sticks present themselves to Microsoft Windows as a regular drive instead of identifying as a bootable USB. This especially happens when using larger USB drives to install Windows or if you have configured your BIOS to boot from the USB drive first always. You can read everything there is to know about the MBR configuration and boot process here.ĭepending on how your PC is configured and which hardware you are using, Windows setup can sometimes be unable to tell which drive is an external USB drive and which drive is a local disk that Windows should be installed to. This error does not normally apply to EFI and UEFI installations of Windows 7, Windows 8, or Windows 10. It depends on your motherboard, your USB interface, the USB stick you are using, and the version of Windows you are installing.ĭuring setup, Windows must identify which drive is your primary boot drive in order to correctly configure the MBR and bootloader. This error is hardware-dependant and its appearance varies from PC to PC. See the setup log files for more information. Setup was unable to create a new system partition or locate an existing system partition. My plan for tomorrow is to get an M2 SSD and see if the SATA makes a difference.īut that's currently all I can think of.If attempting to install Windows from a USB drive, external drive, thumbdrive, USB stick, etc instead of using a CD or DVD, the following error can appear: I'd be grateful for any pointers as I am stuck on this issue for 2 days straight. ![]() Has anyone run into a similar issue or did I miss a critical piece of documentation? for Raid, are sometimes to be supplied, I haven't ever had to supply a driver since Windows 10 for simple storage devices. 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. Just Windows setup will not accept this disk to install to and it claims there is no disk in the system. Using the console with Shift+F10 during Windows setup I can use diskpart and it shows the drive correctly. I have tried various options in Bios, such as enabling/disabling CSM compatibility, etc.įunnily 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. The hardware to deploy to is an Asus X570 Prime and the SSD is a SATA Samsung Evo 850 1TB drive. 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". I already successfully managed to deploy Windows 11 with and without unattend.xml answer files. I have an Iventoy server running on 1.0.17 and it is working.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |