Closed LordBurrito closed 4 years ago
Thanks for the report.
The fact that you get the warning An NTFS service is already loaded
indicates that the UEFI firmware advertises that it already has an NTFS driver, and therefore that the one that UEFI:NTFS (which is the custom UEFI bootloader that Rufus installs to boot from NTFS partitions) should not be necessary.
As a result, because you can't have 2 separate drivers (the one from the ASUS UEFI firmware and the one from Rufus) installed for the same purpose (providing access to NTFS volumes), the UEFI:NTFS bootloader attempts to use the ASUS advertised one to boot.
However, it seems that this driver, which should be able to handle the generic calls issued by UEFI:NTFS to locate and launch the Windows bootloader residing on the NTFS partition, doesn't play nice and returns a mapping error...
Now, if you are lucky, the above means that when you are trying to boot your Windows USB drive, you should see 2 entries for UEFI boot of that device: One for the UEFI:NTFS bootloader (that resides on the second small FAT partition that Rufus created on the drive, and which is the one that produces the messages above) and one for the Windows bootloader that resides on the primary NTFS partition. If that is the case, you should try the other bootloader, as, if Asus didn't screw up their NTFS driver, it should allow you to boot Windows without using the UEFI:NTFS workaround.
One the other hand, if you only see one entry for the UEFI boot of your USB drive, then it means that Asus screwed up their driver, as it means that, as far as UEFI applications are concerned, they do advertise that an NTFS driver is available to access NTFS partitions, yet, if that driver cannot be used to enumerate the Windows native bootloader (which is what should produce the second UEFI boot entry for your USB drive), or to allow UEFI applications to access NTFS files, then it means that their driver is broken.
So, do you see two boot entries for the USB drive or not? And if you see two, what happens when you select the other one?
Hi pbatard,
I do see two entries but I have the same error:
That's not possible. The 2 entries clearly reference 2 different partitions which means that it's impossible for the UEFI:NTFS bootloader to be executed when you select Partition 1.
This means that, no, you are not seeing the same error when you select Partition 1, because the UEFI firmware will try to run a completely different bootloader then.
So, what error do you get then?
I've manually tried to boot into the two partition. Probably one doesn't really show anything and it immediately tries to boot the second one; that's why I see the same error
Then you'll need to take it with Asus, because that's an Asus issue.
The fact that you can select the first partition means that their own NTFS driver managed to locate \efi\boot\bootx64.efi
on the NTFS partition (which is Partition 1). Yet, even as it did locate that bootloader, it doesn't seem to be able to launch it, which it should (because that's the whole point of having an NTFS driver in the firmware).
In other words, you should see the exact same issue (failure to boot) if you simply create an NTFS drive with a single partition and then manually copy the whole content of your Windows ISO, in which case you need to tell Asus support that their NTFS driver doesn't work and needs to be fixed.
Thanks, I'll try to contact them even if I don't think they could really help me.
Do you think downgrading the BIOS I could resolve the problem and would you recommend it to me?
A downgrade is unlikely to resolve your problem. If the issue is what I think it is, it probably has to do with a lack of maturity of the UEFI NTFS driver used by motherboard manufacturers, in which case you want a BIOS with a more up to date NTFS driver, rather than a more ancient one, and therefore one that might be even more problematic.
At any rate, I would encourage you to run the test I advised (copy the whole content on a single NTFS partition and see if you can boot from that), because if, as I suspect, you can't boot from such a media, then you have every right to vehemently complain to Asus support about their NTFS driver and ask them to fix it ASAP by indicating that it directly prevents you from installing Windows.
What do you mean with "copy the whole content on a single NTFS partition" ?
What do you think it's the best way to let them know about the problem ? Could I give them some information/log to really prove the issue ?
Thanks
If you do that and it doesn't boot, then you have demonstrated that their NTFS driver is broken, plain and simple.
You may also validate the SHA-1 of your Win10_1903_V2_EnglishInternational_x64.iso
image to demonstrate to them that you are using a genuine unmodified Microsoft Windows 10 ISO and that therefore it's not an issue with the source media.
Do that, and you should have a very clear case with Asus support, that will be hard for them to dismiss as something external to their UEFI firmware.
Hi pbatard,
sorry to bother you again, I was wondering if you could explain why I'm able to boot Ubuntu ,on the same motherboard and same nvme, in UEFI mode.
I don't see why you shouldn't as long as you use FAT32, which I suppose is what you used to create your drive, since you didn't say otherwise. The problem is with using NTFS.
And again, the one test that can remotely try to pin this issue on Rufus/UEFI:NTFS rather than Asus is if you create a Windows bootable drive using a single NTFS partition, using the steps I highlighted above (i.e. not using Rufus) and you find that it boots. Did you run that test? Because if as I strongly suspect, it doesn't work either, it's when reporting that test to Asus support that you can irrevocably demonstrate to them, without them being able to try to push back the issue on some third party utility being used in the process, that their UEFI NTFS driver is broken and needs to be fixed.
Since I don't think there is much that can be added to what's already been pointed out, I will now close this issue.
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
I'm trying to boot windows 10 in UEFI mode with CSM disabled but I receive this error:
I've tried to use different ISO all taken from the windows website.
I'm able to boot an Ubuntu image with CSM disabled.
I'm using: Motherboard - Asus Rog Z370-H BIOS version 2102 CPU - Intel 8700K SSD - Samsung 960 EVO 250GB m.2
let me know if you need something else
Thanks
Log