Closed comnuoc closed 6 years ago
Your install.wim
is less than 4 GB. What happens when you try to create the same USB in FAT32 mode. You certainly don't seem to use UEFI:NTFS to boot that ISO. Furthermore, as per the UEFI:NTFS screenshot, your UEFI firmware already has an NTFS driver, so you shouldn't have had to use UEFI:NTFS to boot your NTFS partition, as the firmware should have proposed you to boot directly from it.
Also, I'd like to have the SHA-1 of the ISO you used to confirm that it's an official one.
All in all, I kind of get the feeling that there are still some details missing from your report, because what you are attempting to do is a bit illogical, so there must be a reason why you're trying to do it that way... Did you alter the content of the USB in any way after it was created? I may have to ask you to upload your efi\boot\bootx64.efi
somewhere so that I can check it out because if I find that I don't get the same issue on the UEFI systems I have whereas you do, then the only logical conclusion is that this is an issue with your UEFI firmware. have you tried to boot the same USB on a different UEFI machine? If so, did you get the same error?
Hi @pbatard ,
I'm using HP Zbook 15 G3, bios: N81 ver. 01.25 03/29/2018. I'm using dual boot Windows 10 v1709 and Linux Mint 18.3. I created usb as the following:
I didn't change anything after usb was created.
Iso sha1: efe24d454093cacdf2905014d9852f648fe59722 Efi from UEFI_NTFS partition: bootx64.efi.tar.gz Efi from Iso data partition: bootx64.efi.tar.gz
Sorry, I don't have another machine for testing.
Thank you very much for this.
I can replicate the issue with your bootx64.efi
(the one from the ISO partition). But if I use the bootx64.efi
from an official Microsoft ISO, such as en_windows_10_consumer_editions_version_1803_updated_march_2018_x64_dvd_12063379.iso
(one of the official retail ISOs for Windows 10 1803 x64), I don't get the error.
More interestingly, your bootx64.efi
also fails to boot (or at least behave in the manner expected from the regular Microsoft version) when used on a FAT32 partition, i.e. without any involvement of UEFI:NTFS or Rufus.
Did you create the ISO using the Media Creation Tool?
And again, can you please tell what happens if you use FAT32 instead of NTFS as the target file system (basically, since there is no file larger than 4GB on this ISO, you should use GPT and FAT32). Does it boot at all?
Yup, the bootx64.efi
you attached is definitely corrupted, hence your issue, and it has nothing to do with Rufus.
An x64 EFI executable should start like with MZ
and contain a PE/COFF headers. Yours has none of that, which means it is NOT a working EFI application.
In an hex editor, the beginning of a working EFI executable should look close to this:
You may want to use an hex editor with the efi\boot\bootx64.efi
from your ISO to find out how the actual file on your ISO looks, and whether it starts with MZ
. If it does, then I suspect that your USB is starting to fail and is corrupting data. If not, then you will need to recreate your ISO again, as the one you have is corrupted.
Yes, my iso file is corrupted. I have just downloaded the new Iso file, and it's working. It's my mistake, sorry. Thank so much.
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
Log
button in Rufus and copy/pasted the log into the line that says<FULL LOG>
below.Rufus version: x.y.z
- I have NOT removed any part of it.Additionally (if applicable):
#
button (at the bottom of the Rufus interface), 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
UEFI:NTFS reports
[FAIL] Load failure: [3] Unsupported
when trying to launch theefi\boot\bootx64.efi
from the ISO I use:Log