I'm unable to install Windows in UEFI mode - Acer Aspire e5 573g

Can you enter the exact model? Example an515-51-75kz. Did you convert the flash drive to gpt and formatted it in fat32?

Model Acer Aspire e5 573g
Yeah, I had converted in GPT but formatted in NTFS

No! Format usb stick in mode fat32!

USB disk is formatted in fat32

Did you create a password and disable secure boot?

Yes, I did.

Recently, I installed windows using another laptop by switching hard drives and now it boot up with a startup recovery

Ok! check this file create for me:

instalar windows 10 inglês.pdf

I'll refer to these methods but first, I'm getting UNEXPECTED STORE EXCEPTION error. Can you please tell me what's the cause for this error.

And now
SYSTEM SERVICE EXCEPTION error.

Are you trying to install windows 10? Have you checked if the problem with another hdd?

Let's add another option for you to try and some info on the process.

Installing any recent Windows (7+) in UEFI mode is rather simple, but there are some things to take into consideration.
- Secure Boot is one of them, some BIOSes don't even present those options, but making it simple to understand: when it's on it verifies digital signatures on whatever you try to boot. It doesn't actually prevent you from installing Windows in UEFI mode, but when in doubt you can deactivate it for the installation (activating it again after the system is installed is trivial).
- Partition types, booting off an USB formatted as NTFS while Secure Boot is turned on can be tricky (it may involve introducing your own keys into the store... bla bla) so if at all possible don't do it. Most Windows ISOs fit in FAT32 formatted volumes, and if they don't because the install.wim file inside of the sources folder is >4GB in size it can always be split up.

So practical steps I'd recommend you do:
1. Ensure UEFI is selected if there's such an option in your BIOS, check Secure Boot settings.
2. Get an installation image, you can use any and there are several ways of obtaining it (for Windows 10 there's an official download utility for example, for others there are several different services like Heidoc's Windows ISO downloader tool).
3. Get Rufus, nice little utility that does everything for you regarding setting up the USB drive and copying the installation files to it. It's pretty straightforward, you click the SELECT button, select the USB stick you want to use from the drop down list and click Start. There are many other options, but just make sure that the Target system is set to either UEFI, or BIOS or UEFI (i.e. not CSM).

Once that's done, boot off of that USB stick and go along, you don't have to partition the internal disk as the installation program takes care of that, just make sure it's all clean and its partition table is GPT. Again, several ways to do it, I find diskpart to be useful for that, but do it however you like.

The only thing I can think of that could give you trouble (aside from a faulty hard drive) is that you're unable to see any internal storage during Windows setup, which would mean you'd need to load an storage driver before installing, but I don't think that's the case here (and if you do, what you need are Intel RST drivers (just the drivers, sometimes referred to as F6 drivers) I believe judging by your machine, this would be a good read on the matter).

Let's add another option for you to try and some info on the process.

Installing any recent Windows (7+) in UEFI mode is rather simple, but there are some things to take into consideration.
- Secure Boot is one of them, some BIOSes don't even present those options, but making it simple to understand: when it's on it verifies digital signatures on whatever you try to boot. It doesn't actually prevent you from installing Windows in UEFI mode, but when in doubt you can deactivate it for the installation (activating it again after the system is installed is trivial).
- Partition types, booting off an USB formatted as NTFS while Secure Boot is turned on can be tricky (it may involve introducing your own keys into the store... bla bla) so if at all possible don't do it. Most Windows ISOs fit in FAT32 formatted volumes, and if they don't because the install.wim file inside of the sources folder is >4GB in size it can always be split up.

So practical steps I'd recommend you do:
1. Ensure UEFI is selected if there's such an option in your BIOS, check Secure Boot settings.
2. Get an installation image, you can use any and there are several ways of obtaining it (for Windows 10 there's an official download utility for example, for others there are several different services like Heidoc's Windows ISO downloader tool).
3. Get Rufus, nice little utility that does everything for you regarding setting up the USB drive and copying the installation files to it. It's pretty straightforward, you click the SELECT button, select the USB stick you want to use from the drop down list and click Start. There are many other options, but just make sure that the Target system is set to either UEFI, or BIOS or UEFI (i.e. not CSM).

Once that's done, boot off of that USB stick and go along, you don't have to partition the internal disk as the installation program takes care of that, just make sure it's all clean and its partition table is GPT. Again, several ways to do it, I find diskpart to be useful for that, but do it however you like.

The only thing I can think of that could give you trouble (aside from a faulty hard drive) is that you're unable to see any internal storage during Windows setup, which would mean you'd need to load an storage driver before installing, but I don't think that's the case here (and if you do, what you need are Intel RST drivers (just the drivers, sometimes referred to as F6 drivers) I believe judging by your machine, this would be a good read on the matter).

Let's add another option for you to try and some info on the process.

Installing any recent Windows (7+) in UEFI mode is rather simple, but there are some things to take into consideration.
- Secure Boot is one of them, some BIOSes don't even present those options, but making it simple to understand: when it's on it verifies digital signatures on whatever you try to boot. It doesn't actually prevent you from installing Windows in UEFI mode, but when in doubt you can deactivate it for the installation (activating it again after the system is installed is trivial).
- Partition types, booting off an USB formatted as NTFS while Secure Boot is turned on can be tricky (it may involve introducing your own keys into the store... bla bla) so if at all possible don't do it. Most Windows ISOs fit in FAT32 formatted volumes, and if they don't because the install.wim file inside of the sources folder is >4GB in size it can always be split up.

So practical steps I'd recommend you do:
1. Ensure UEFI is selected if there's such an option in your BIOS, check Secure Boot settings.
2. Get an installation image, you can use any and there are several ways of obtaining it (for Windows 10 there's an official download utility for example, for others there are several different services like Heidoc's Windows ISO downloader tool).
3. Get Rufus, nice little utility that does everything for you regarding setting up the USB drive and copying the installation files to it. It's pretty straightforward, you click the SELECT button, select the USB stick you want to use from the drop down list and click Start. There are many other options, but just make sure that the Target system is set to either UEFI, or BIOS or UEFI (i.e. not CSM).

Once that's done, boot off of that USB stick and go along, you don't have to partition the internal disk as the installation program takes care of that, just make sure it's all clean and its partition table is GPT. Again, several ways to do it, I find diskpart to be useful for that, but do it however you like.

The only thing I can think of that could give you trouble (aside from a faulty hard drive) is that you're unable to see any internal storage during Windows setup, which would mean you'd need to load an storage driver before installing, but I don't think that's the case here (and if you do, what you need are Intel RST drivers (just the drivers, sometimes referred to as F6 drivers) I believe judging by your machine, this would be a good read on the matter).

Well, I followed your procedure thoroughly @alphanic but the problem remains the same.

I get errors like drivers missing or corrupted even if I'm only booting up the windows setup.

Missing drivers huh...

I just built a Windows 10 live environment (it was intended to diagnose a different thing, but it may help here too) and I have uploaded it here: MEGA link.

You can use Rufus as well to transfer its contents to a USB stick (a 1GB one suffices), when using UEFI it'd automatically choose GPT and if you'd rather use it in an older BIOS system selecting MBR as the partition scheme should change the rest of the settings accordingly.

Anyway, after booting from it you'll be presented (hopefully) with this screen:

Default view of the live environment

That dock above allows you to start the different programs I included, from left to right:
- Explorer++, a Windows Explorer alternative for that light environment, in case you want to copy things.
- HWiNFO, an all in one system information / diagnostic utility.
- GSMARTControl, a graphical utility to check on the state of the (detected) hard drives based on their S.M.A.R.T. attributes, among other things you can see internal logs on errors or self tests.
- Hard Disk Sentinel, this one is a trial version but serves for your purpose. Just like the previous one allows you to check on the detected hard drives to see how they're fairing. Information is more readily visible compared to the previous one, and the shows a performance and health interpretation based on the data. This may be the most useful for you, if the internal hard drive is dying it should be able to tell you why (e.g. plenty of bad sectors, transmission errors over time that may be related to a bad connection or cable, etc.).
- FastStone Capture, another trial version, it's an screenshot utility in case you need to. You could save the capture somewhere to upload it later on.
- And lastly a command prompt shortcut.

I'd suggest booting off of this image and seeing what Hard Disk Sentinel has to say about your drive, maybe it's badly damaged and needs replacement. That's what those errors you're getting suggest to me I'm afraid, or maybe the USB stick you're using is the one presenting problems, but I find it unlikely.

PS. I didn't add any specific storage drivers to it yet as it's a first draft, but I think Windows 10 ought to have inbox drivers for yours (AHCI ones for sure, if they're routed through RST in a BIOS setting in case it exists I may need to add them for the OS to see the drive), let me know if it doesn't see any internal drives.

PPS. To reboot the computer after you're done, right click the dock and chose to quit, as I didn't include any shortcut for it just yet haha.

Is this image have a 32bit base architecture? The file name was WinPE32.iso. Guess I'm unable to boot because of it. Should I boot in Lagecy mode?

29212KSG said:

Is this image have a 32bit base architecture? The file name was WinPE32.iso. Guess I'm unable to boot because of it. Should I boot in Lagecy mode?

Yep, I used a 32-bit Windows 10 image as a base mostly because of the programs I wanted to include. It is WinPE based, and because of it the WoW64 subsystem that allows you to run 32-bit apps in a 64-bit Windows isn't included.

Explorer++, HWiNFO and GSMARTControl have pure 64-bit versions available, but the other 2, Hard Disk Sentinel and FastStone Capture, do not (and neither has that dock I used as a launcher for everything). That's why I used a 32-bit Windows PE instead of a 64-bit one.

But there shouldn't be any problem preventing you from booting from it, even if your processor is 64-bit capable like they have for 10 years give or take they're all able to boot 32-bit code. Since it's Windows we have Secure Boot covered too, so you could use that drive in a system that had it enabled, I gave it a shot here yesterday before posting to make sure it appeared as an option when UEFI is selected in the BIOS and whether or not Secure Boot is enabled or disabled.

These are the settings I used to create the bootable USB stick (notice the highlighted areas):

Image: https://us.v-cdn.net/6029997/uploads/editor/yj/3afa3y9b55m8.png

If you wanted it to boot when legacy is enabled (that's not an option in my machine, mine is UEFI only) the options would need to be these:

Image: https://us.v-cdn.net/6029997/uploads/editor/3m/1sznlxyaomee.png

BUT! For some reason I don't think you're alone in this, I've managed to get to the same state you're right now with your machine (sadly haha). The USB stick I had created yesterday for testing purposes doesn't appear in the boot menu. It works fine in other UEFI machines though, so I've ruled it out as a possible cause, but this one refuses to show it as a boot option.

The only boot option I see is the Windows Boot Manager belonging to the Windows installation I have in the internal disk, nothing else. If I were to hazard a guess... I'd say it's because of Acer's UEFI implementation, but more testing would be required to reach that conclusion. I don't know, it seems not to show an option to use a Windows boot manager if it already exists in the internal disk.

There's probably ways around it, I have some free time now so I'll be testing stuff, but we only wanted to know how things were doing in your laptop!!!

Oh... the irony!

I have the impression that bios does not see the usb stick when it is formatted in ntfs. Maybe you should test format usb stick using the command prompt as administrator, see:

Image: https://us.v-cdn.net/6029997/uploads/editor/kt/91em7vy0z8ld.png

Then simply extract the x64 iso only to the root of the usb stick. Importantly, secure boot must be disabled! I refer to the uefi mode and not the legacy mode.