Closed Topkek-190 closed 1 year ago
That's a UEFI/BIOS issue or target platform vs ISO mismatch, not a Rufus issue.
First of all, are you 100% sure that your target computer has a 64-bit UEFI firmware?
Because the only bootloader present on your ISO (en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.iso
) is efi\boot\bootx64.efi
(per your log about), if you happen to be trying to boot on a machine that has an x86 32-bit UEFi firmware (which can happen even if you have an x86 64-bit CPU), then you will have exactly the kind of issue you report.
Or, considering that you are using IOT, you may be using a completely different CPU architecture on your target system, such as ARM (in which case efi\boot\bootx64.efi
will never work).
At any rate, since you don't actually need Rufus to create your media on account that the sources\install.wim
from your ISO is smaller than 4 GB, I can guarantee that if you simply create a FAT32 partition on your USB, and extract the whole content of your ISO using something like 7-zip, you will see the exact same issue, whereas, if you are actually using an ISO that is compatible with your system, this should just work.
Therefore, unless you can demonstrate that when you extract your ISO onto a FAT32 partition it boots, whereas when you use Rufus it doesn't, I have no choice but to dismiss your issue as something that has nothing to do with Rufus.
It seems to be a UEFI issue but Windows's ESP has EFI\Boot\bootx64.efi and Windows boots normally so I can't understand why it wouldn't boot from the USB.
As for the architecture thing, my PC is an x86-64 Intel and the iso is en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f
which is for the x64 architecture so it's definitely
not an architecture mismatch
Here is file
output for the efi\boot\bootx64.efi
executable on the usb flash drive and the Windows ESP
Also, I've tested it with UEFI:NTFS, still doesn't work
Again, please create a FAT32 USB with a efi\boot\bootx64.efi
and try to make that boot. As long as you can't demonstrate that, when you do that, your USB boots, but not when your USB is created with Rufus, then your issue clearly is unrelated to Rufus.
Most likely, if you do have a efi\boot\bootx64.efi
for Windows, then you didn't set up your UEFI firmware settings so that USB drives will have precedence over internal drives (there's pretty much ALWAYS a setting, and sometimes multiple ones, in your UEFI firmware that governs this). Those settings a specific to the motherboard and UEFI firmware you use, so you will need to read your manual, because noone but people who have the exact same motherboard will be able to tell you precisely what you need to do.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
Checklist
<FULL LOG>
below.Rufus version: x.y.z
- I have NOT removed any part of it.Additionally (if applicable):
(✓)
button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
When I tried to boot a Windows FAT32 GPT UEFI usb pendrive formatted by Rufus, instead of booting the installer, it boots to Windows from my hard drive. I've tried booting it using the BIOS menu as well as Windows Recovery but it still boots to Windows
Log