Closed B00ze64 closed 4 years ago
Thanks for the report. This looks like a regression indeed. I'll look into it when I get a chance.
I'd like to piggyback on this. Rufus 3.11 seems to be the latest version, and now the target system HAS to be UEFI, not BIOS. I've been happily booting from USB sticks with iso's burned via Rufus for months on an ancient HP Compaq with an AMD 64 Athlon X2. (Some of us are poor, yo!)
Yesterday it didn't work. I urge the developer to put back the BIOS functionality so those of us who can't afford new UEFI systems can be spared the mess that is UNetbootin.
As indicated above, I am planning to fix this in version 3.12.
Thanks much! Rufus rocks as hard as the old band of the same name. Shout-out to Chaka Khan.
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 burning Kaspersky Rescue Disk 2018 (downloaded today) with Rufus 3.04 I am offered the option of BIOS or UEFI, but with Rufus 3.11, the only option offered is UEFI. The KRD ISO is of course compatible with BIOS/CSM. The FAQ (from 2015) mentions Kaspersky are bad boys, and break GRUB identification, and it appears they are still doing it, but I opened the issue because Rufus 3.04 still offered a choice of BIOS or UEFI; Rufus 3.11 does not anymore.
Log