pbatard
commented
6 years ago Thanks for opening a new issue.
As I mentioned in the previous one, I suspect that the problem comes from the EfiFs NTFS driver having switched from using the IMAGE_SUBSYSTEM_EFI_RUNTIME_DRIVER PE type to IMAGE_SUBSYSTEM_EFI_BOOT_SERVICE_DRIVER, which I suspect some UEFI Firmwares might not like. The problem however is that I had to change that attribute because it was creating issues with other UEFI firmwares, and IMAGE_SUBSYSTEM_EFI_BOOT_SERVICE_DRIVER is the proper type to use for what UEFI:NTFS is doing.
You are mentioning that you went through a BIOS update, so I wonder if that update is preventing EFI executables with IMAGE_SUBSYSTEM_EFI_BOOT_SERVICE_DRIVER from running.
Here's what you can do to validate that this is indeed the issue, using the USB you created with Rufus 3.3:
-
Download CFF Explorer from here. If you don't know which version you should pick, I'd recommend the CFF Explorer (x86 Version, stand-alone, Zip Archive) as this is smaller and it doesn't need to be installed.
-
Plug in the Flash Drive created by Rufus. Since you're running on Windows 10, you should be able to access both the partitions Rufus created on that drive, including the UEFI:NTFS. However, Windows may not mount it automatically, and Disk Management seems to have trouble displaying small partition to do the following with the GUI, in which case you will have to assign a letter manually using
diskpart. In case you cannot see theUEFI_NTFSpartition, you should:- Open an elevated command prompt
- Run
diskpart - Run
list vol. This will list all the volumes available, and you should see something likeVolume 7 UEFI_NTFS FAT Removable 512 KB Healthyin your list. Take a note of the volume number for the UEFI_NTFS partition. - Run
sel vol #where#is the number above (e.g.sel vol 7) - Run
assign letter=XwhereXis any drive letter that is not already in use. After that, you should be able to access the UEFI:NTFS partition from Windows Explorer. A screenshot of the procedure is also provided below:
-
With both CFF Explorer and the UEFI:NTFS partiton available, launch CFF Explorer
-
Open
EFI\Rufus\ntfs_x64.efion the UEFI:NTFS partition -
On the left pane navigate to Nt Headers → Optional Header. This should allow you to view the Subsystem property and see that it is set to EFI Boot Driver:
-
Click on EFI Boot Driver and change it to EFI Runtime Driver and then click the Save button (select Yes when it asks you to overwrite the file)
-
Try to boot the USB again and see if that works better.
Of course, this is just one possibility, and I may be off mark (especially it's possible that I had already changed the subsystem type before 2.18, in which case the above probably won't help).
The other thing that I'd like you to try, to confirm that this has to do with the EFI driver, is to pick the EFI\Rufus\ntfs_x64.efi from the 2.18 drive and copy it to the 3.3 drive (replacing the existing one) and see how that works. Alternatively, you can try each of the ntfs_x64.efi from https://efi.akeo.ie/downloads/, starting with EfiFs 1.0 (and then selecting the x64 repository) to see which one works and which one doesn't, as this may help me pinpoint what the issue might be.
zanechua
Mattiwatti
devedse
lock[bot]
farid220
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
Motherboard: S2600CP4 Bios Revision: R02.06.E006 Rufus version: 3.3
Here's the log from Rufus: https://gist.github.com/zanechua/36c2416c9d8035623a0efb51a176d7af
Here are the errors I am getting on boot:
EDIT:
So it seems like the last version of Rufus v2 works.
Rufus version: 2.18
Here's the log from Rufus: https://gist.github.com/zanechua/acf8c67c7026814796f7da6414dd6e3e
I don't think it's the bios update though since 2.18 works. I haven't formatted this computer in awhile so I might have been using 2.18 and this is the first time I am using 3.x on this computer.