Correct me if i'm missing something cause I've never had a single problem installing W10 on my new PC. I'm wondering because I've read all the fuss with Rufus and the partitions that it creates for UEFI on many topics here. I just use an NTFS usb stick, single partition, extract the contents of the monthly updated Windows 10 iso and that's it. As I used to do so many years on my non-UEFI system. I boot from the usb stick, with CSM disabled and Secure Boot enabled. I can create GPT partitions and all that on setup.
@venejo Everything is nice, but it only works if you use a so-called legacy boot, but not if you use a UEFI boot. Another thing - you say you are using a legacy boot, why do you then need an NTFS formatted USB flash drive if normal is FAT32 (NTFS is even not recommended) and why are you then using GPT partitions if you are not using a UEFI boot? Then is normal to use MBR.
Personally I used Rufus in the past. Since I use UEFI with Secure Boot, I had to disable Secure boot when installing Windows. Until I discovered you can partition your USB disk in such a way that even though you use UEFI with Secure Boot, you didn't have to disable Secure Boot any longer when installing Windows. This is how Win10 Setup Disk [For UEFI or BIOS / UEFI with Secure Boot / Install.wim over 4 GB] got started. Presently I prefer not to use a USB disk. I just boot into Windows Recovery Use (WinPE) Boot.wim in place of (Recovery) Winre.wim and install Windows from Win10XPE. All my USB disks (have Win10XPE) just for emergency.
You have gone to a bit more advanced options than me. I just use NTFS because of the classic 4gb limitation (for the install.wim file), never had any problem with this, not even on Windows 7 - 8. The stick is with an MBR active NTFS partition. When I mentioned GPT I meant during on Windows setup (hard disks). As for the UEFI I guess since I have disabled CSM completely and the secure boot is enabled that is what the system is using on boot etc. Unless I got it wrong somewhere...
dont start the installation normally open cmd.exe with shift+F10 type this into cmd.exe: setup.exe /installfrom:<ntfs drive:>\install.wim
No problem to do that but why it is preferred and why use it since I don't get any errors during or at the end of the windows setup the way I do it? That's why i'm saying, i'm I missing something here? Update: In my BIOS the boot settings are as follows: Windows 10 Features: Windows 10 (other options available are OTHER, Windows 10 WHQL). CSM Support: Disabled Secure boot: Enabled status: active With these options never had a single problem installing Win10 with an MBR (NTFS formatted) usb. I don't know if Gigabyte (bios) has something to do with it. For example with some Linux distros I had problem with Secure boot but nothing else.
Just to add to this thread, I have a ASRock B450M motherboard, and it natively supports NTFS with UEFI (it has an embedded NTFS driver in the firmware it appears), I'm not sure how common that is though.
This is perfectly related to this topic, because if you want your computer to use a USB flash drive in UEFI mode for booting, it is necessary to use NTFS because FAT32 only allows the use of bootable media that is up to 4GB. But when it comes to legacy BIOS booting, feel free to use FAT32 and select USB from the boot menu manually and everything will work. The problem occurred when the Windows 10 bootable media went larger than 5GB, what means you need at least 8GB USB flash drive.
if its working and simple way for u then its the best for u no need to change ur ways i just gave this way which is directly solve this problem without additional steps
E2B with agFM works great for booting everything. Only thing is you need to restore secure boot keys to default due to the Kaperskys signed shim that has been blocked by microsoft that is used to uefi boot.
You can easily create your own winpese and such ISOs: User-friendly WinPE Builders ChrisPE - a PEBakery Team release PEBakery
Fun fact: UEFI installs and my superaio were one of the main reasons why I worked on that script, LOL. At the time I was having a lot of issues with solid ESD compression and I thought the solution was split wim. That also helped with my goal if getting it to work with UEFI by keeping files under 4gb. *old man voice* back in those days we didn't have these fancy mods to get around the boot limit like RUFUS has these days