# gdisk /dev/sddowY# cgdisk /dev/sdd1Gef000700# mkfs.vfat -F 32 /dev/sdd1# mkfs.ntfs -f /dev/sdd2 Appreciate it.Īfter some internet searching I found some supposed idea that you can format it with the partitioning scheme of a FAT32 EFI system and a larger NTFS partition to hold the sources folder (with only the boot.wim file on the system partition's sources folder and an ei.cfg containing \n Retail), but this doesn't even register as a bootable drive by the UEFI firmware.
oh right, okay the install.wim file is 4.5GB, thanks. This is supposed to be a hybrid image, no? It should work fine to dd it.īut fine, what if we format the stick as FAT32, set the partition ID to ef00 (EFI system, since GPT doesn't have a bootable flag) and copy the files over. but then why can I browse the files on the usb when looking for drivers? Either way MSI doesn't have a download for the usb controller drivers, and 1803 installed just fine using the exact same setup (including the same usb stick. Okay, what if I reboot now that I've changed the GPT, maybe it's just cranky? Still nothing, maybe it can't read the usb. I point it at networking, SATA controller, and chipset drivers respectively (as provided by MSI) but no dice. Well that's odd, shift+f10 diskpart, it appears that it can see all connected drives so it should be an issue, figure I'll rebuild the gpt on the target drive anyway just for good measure.Okay, whatever. It boots just fine, I select my language, click "Install Now" and on the "Gathering Information" step I get hit with "A media driver your computer needs is missing" So I write the image to my usb stick using dd:ĭd if=Downloads/Win10_2004_English_圆4.iso of=/dev/sdd bs=4M status=progress Recently my windows 10 install broke on windows update, figured it's probably time to reinstall instead of fixing it so I download the iso from microsoft (windows 10 2004), it installs fine under a VM, the ISO appears to work.
0 kommentar(er)
