I want to just post one interesting thing that i found out just now:
my wife has an Acer Aspire E1 572G Laptop with i5 processor and ACER BIOS and free Windows 10 update from originally Win 8 OEM. After yesterdays update round it got hanged during bootup at the login screen of Win10 not showing any dialogue and not providing any option for doing anything. After several restarts it did not boot into the recovery mode as it should have done by Win 10 specs. So i had to try to boot a recovery CD. So i burned one from my own Win 10 PC. Then the next thing was to get that CD booted on my wifes computer. I had to activate in the Acer BIOS the F12 boot menu option. In the BIOS there were listed several boot options as it should be from all recognized system devices amongst them the Windows boot manager. I was really surprised when i activated the boot manager to boot from CD because CD to first boot priority did not work as it should. When the boot manager was activated by me with F12 then the only available boot option was the Windows boot manager which was of course not doing anything else than hanging the boot procedure without providing any recovery option. So, my conclusion is that Microsoft changed a working Acer BIOS in the course of its OEM policy in order to leave a knowledgeable customer without recovery option. Shall my wife go now and buy a new computer? That is how Microsoft cares about their money more than about their customers...

I feel like Microsoft should be sued for damaging my wifes computer to a serious degree by destroying the ACER BIOS intentionally and therefore making it impossible to install any other operating system than the OEM Windows that came with the computer and it should be condemned to pay for all the expenses, losses of usage for the computer and so on. What is your opinion?
What should be the exact statement for the court case?

The Acer Aspire laptops have secure boot, which means you can't boot from CD.

You need to disable secure boot.

Also, for non-EFI CDs and DVDs, you'll need to enable "legacy boot."

1 members found this post helpful.

I tried what you suggested. I disabled secure boot and in BIOS all boot options were showing nicely, but when invoking the boot manager it shows only the Windows boot manager. thus i conclude that Microsoft is damaging and hacking hardware of end customers...very bad behaviour...

Maybe the BIOS can be flashed??

Did you enable legacy boot?

1 members found this post helpful.

Hi Thomas...

It appears you're not the only one who's had issues with the E1 in this way...

http://askubuntu.com/questions/42483...r-e1-with-uefi

https://ubuntuforums.org/showthread.php?t=2101655

Perhaps one of the solutions offered might be of help.

Regards...

1 members found this post helpful.

thanks for the nice advice. I was little bit messed up by the BIOs of my wifes computer. Finally i switched on legacy boot option and i could boot from CD-ROM. However, the recovery CD was also not able to get win 10 up running again. My conclusion is that the harddisk got destroyed during Win 10 Update. Such thing also happened to me. Microsoft customer supports answer: "That happens only with harddisk that are going to die soon." I had same thing when i installed Win 10 on my PC as Win 7 update. Then also my harddisk got destroyed. Windows was even warning. Maybe Microsoft tries to make some extra bucks by "motivating" its customers to buy new harddisk every now and then..

Microsoft didn't do anything with the bios other than if you did a hybrid hibernate. That would lock the boot.

You create a uefi bootable media and select it. May require a DVD uefi media as some uefi bios's don't read cd's as a potential uefi device.

2 members found this post helpful.

If BIOS is set to UEFI you need to install to the EFI partition /boot/efi instead of MBR. If UEFI is ‘disabled’ than installing to MBR is correct.

If BIOS is in UEFI mode installing to MBR can give ‘no boot device detected’

rkelsen is right; you need to disable the secure boot and quick boot as well if that's enabled.

-::-Flashing the BIOS should be the last resort as it can render the machine completely inoperable.-::-
(if you don't have the exact BIOS update/upgrade from the manufacturer and the proper file for the exact machine)

2 members found this post helpful.

You're welcome, hope you get it working correctly.

Regards...

1 members found this post helpful.

jefro hit it on the head. I've had no problems booting from a USB stick via EFI boot, and have done so on an older iMac and on a newer laptop. Booted openSUSE, but pretty much any distro of Linux that supports EFI should have no problems.

The 'gotcha' is when it comes to partitioning. I monkeyed with it first, an didn't create the /boot/efi partition...the system would work fine, IF I booted it from USB, and selected "boot from hard drive" from the menu. After leaving such things alone, and in the hands of the installer, it worked without a hitch. You should be able to use Linux Mint, openSUSE, Ubuntu, or Fedora with no problems with EFI.

1 members found this post helpful.