Unable to install Win 7 x64 in UEFI mode on ASUS MoBo (TR4 socket)

MihaiN

n00b
Joined
Apr 13, 2017
Messages
27
Hi everyone,

It's been a long time since I've posted here, but last time I did I received very pertinent and helpful answers.
Hoping this will happen once again now, and also maybe help others with the same issue.

So my problem is when I try to install Windows 7 x64 in UEFI mode on my new Asus Prime X399-A motherboard (TR4 socket with Threadripper 1920X CPU installed). Also, this is being installed on an M.2 NVMe SSD from Intel 760p series.

I have made a bootable USB flash drive with Rufus and this is the error I'm getting when trying to boot from it:
Status: 0xc000000d
Info: The boot selection failed because a required device is inaccessible.

IMG_20190203_172935.jpg

I have deactivated Secure Boot under BIOS:

IMG_20190208_201808.jpg

Other BIOS settings I've made:

- CSM (Compatibility Support Module) configuration:

IMG_20190208_201754.jpg

- Boot Configuration:

IMG_20190208_201734.jpg

- Fast Boot has also been disabled

These are the settings used in Rufus to make the bootable USB:

Rufus settings.png

I have to note that this is an image I made myself by downloading untouched MSDN image of Windows 7 SP1 x64 and slipstreaming Simplix update pack which contains all updates to this moment (Jan 2019).
This will make the install.wim file of 4,66GB which makes it impossible to create the bootable USB under FAT32 file system. So NTFS was the only way to go.

I'm certain that I've done everything correct when creating the Windows image with slipstreamed updates because I also tried creating the bootable USB with MBR partition scheme and installer booted just fine.
By using Asus' EZ Installer tool and slipstreaming USB 3.0 & NVMe hotfix in the installer, Windows 7 was successfully installed with MBR partition scheme, this is how I know the image I made is fine.

But MBR is not what I'm after. I know that in Jan 2020 Microsoft will drop support of Win7 and probably not long after I will start having problems with unsupported software. Plus that if I upgrade to an RTX GPU, I will not have RTX support on Win7. So I know installing Windows 10 is inevitable, I'm just waiting for a more stable version and am not in a rush. I also am not a fan of Win10...

Because I'm after the possibility to have 2 separate Windows' installed (7 & 10) and boot up whichever I require based on my needs, I need to install Win7 with GPT partition scheme and (why not) NTFS file system.

Perhaps others with Asus motherboards have run into the same issue and know a fix for it.
If this has been already discussed, apologies. I did search the threads, but have not found this particular error when trying to install a fresh Windows.

I'm really hopping there's something I missed and there's a workaround for this because I know for a fact Win7 x64 does support UEFI mode.
Since making the bootable USB with the exact same settings for Win10 did launch the installation process, it seems like there might be something missing from the Win7 installation files, I'm just not advanced enough to figure it out.

One more thing I want to point out: I did also try to disable CSM from BIOS and that was a major mistake. My PC refused to boot, only a black screen came up. Then I used a jumper to shortcircuit PINs 1 & 2 in order to reset CMOS as specified in the manual and then my PC wouldn't even power up anymore. I had to repeat the process TWICE with the battery removed in order for it to work.
So disabling CSM is a no go.

I googled all I could and tried my best to figure it out by myself by changing different BIOS settings, but I'm stuck and need input from more advanced users.
 
I know nothing about RUFUS, but i am guessing it creates an EFI partition, most motherboards will only boot from a fat32 partition.
it looks to me that this USB drive has previously been used as an MBR device, set your bios to boot only from EFI device and see what happens
 
I know nothing about RUFUS, but i am guessing it creates an EFI partition, most motherboards will only boot from a fat32 partition.
it looks to me that this USB drive has previously been used as an MBR device, set your bios to boot only from EFI device and see what happens
I've already tried that.
I used the untouched MSDN image of Windows 7 SP1 x64 which has an install.wim that's less that 4GB, made a bootable USB with GPT partition scheme and FAT32 file system. Same error.

Changing BIOS to boot only from UEFI device makes no difference.

Based on what I found here, it looks more like a BIOS problem. Because it's similar to my issue, even though error is not the same.
Trying to install Win10 in UEFI works fine but Win7 doesn't... it sure looks like an Asus BIOS screw over.

I had another idea, but not sure if it's a brilliant one... what if I try to flash the BIOS to the very first version listed on Asus website as being compatible with my mobo?
I know it's risky, but is there really any chance in messing up the mobo itself?
It originally came with version 0807, I flashed it to the latest one which is 0808 and behavior is the same.

Opinions on flashing to first release 0318 from 2017/08/16 ?
 
When you are accessing the boot menu, are you choosing UEFI:<usb name>? It should be listed twice, once without UEFI: listed and once with it. If you are choosing the one without then it's going to install in MBR mode.

I would recommend trying it without using the fix pack. Just use a virgin ISO booted disk created with EZ Installer (for the injected drivers) then select the UEFI <usb name> as the boot menu drive.

You may also want to revert to default settings, and only disable Secure Boot. Leave CSM auto.

I know this is a newer board, but I use to run Windows 7 as UEFI GPT disk with a P67 board, so I know it works.
 
Had similar issue where it would ask for DVD drivers using a flash drive?! and a b450 bios issue that would cause all usb to stop working.

Grab the gigabyte usb tool. It adds usb drivers to your flash Iso.
 
One last thing, I know this is going to sound crazy but try burning the ISO (with injected drivers by EZ Creator) to DVD and installing. I've seen UEFI work better with Windows 7 if booting from DVD.
 
When you are accessing the boot menu, are you choosing UEFI:<usb name>? It should be listed twice, once without UEFI: listed and once with it. If you are choosing the one without then it's going to install in MBR mode.

I would recommend trying it without using the fix pack. Just use a virgin ISO booted disk created with EZ Installer (for the injected drivers) then select the UEFI <usb name> as the boot menu drive..
Thanks for the tip, but I've actually already tried that.
As mentioned above, I used the untouched MSDN image of Windows 7 SP1 x64 which has an install.wim that's less that 4GB, injected USB3.0 and NVMe drivers, made a bootable USB with GPT partition scheme and FAT32 file system. Same error.
And yes, the first boot option was always the USB option that started with UEFI:<usb name>

You may also want to revert to default settings, and only disable Secure Boot. Leave CSM auto.

I know this is a newer board, but I use to run Windows 7 as UEFI GPT disk with a P67 board, so I know it works.
Tried that as well, so I reset BIOS to default, only disable Secure Boot, and end result is the same.

One last thing, I know this is going to sound crazy but try burning the ISO (with injected drivers by EZ Creator) to DVD and installing. I've seen UEFI work better with Windows 7 if booting from DVD.
That actually came to mind.
I have a DVD-RW optical drive lying around, only problem is it's very old and has 40-pin IDE interface, not SATA. Finding an adapter to connect it to the SATA ports on the board seems challenging...
 
After making the changes, have you ran a "clean" command on the NVMe Intel disk? This wipes out the MBR and reset it to non-initialized state and would allow the installer to initialize it as GPT if you boot into the UEFI installer.

https://www.buffalotech.com/knowledge-base/cleaning-a-disk-in-windows-7-using-diskpart

You can run this command from the WIndows 7 setup screen. When the Install 7 screen first pops up, press shift+F10 to bring up cmd prompt and use the commands. Alt-tab between cmd and Windows 7 setup, then continue with setup.

I've done a lot of Windows 7 reinstall with GPT and went through all of these problems before. It's always been related to how the USB is created in my instances. DVD is an easy fix since there is no way for it to be incorrect, only one format. I just would hate to see you buy a DVD and have something not work (issues with the board, etc). Know anyone with a USB DVD drive that you could borrow?

You may also want to try a different USB creator, just in case a Rufus setting isn't right. Microsoft makes one for Windows 7. Just create the ISO with EZ and try this tool to create the USB https://www.microsoft.com/en-us/download/details.aspx?id=56485 TBH though I don't remember if this tool works with UEFI install, but it's worth a shot.
 
Last edited:
Did you try asking Rufus to check the device for bad blocks?

If that passes try a different USB pen.
I've encountered a few that were either tricky or impossible to make bootable.
 
After making the changes, have you ran a "clean" command on the NVMe Intel disk? This wipes out the MBR and reset it to non-initialized state and would allow the installer to initialize it as GPT if you boot into the UEFI installer.

https://www.buffalotech.com/knowledge-base/cleaning-a-disk-in-windows-7-using-diskpart

You can run this command from the WIndows 7 setup screen. When the Install 7 screen first pops up, press shift+F10 to bring up cmd prompt and use the commands. Alt-tab between cmd and Windows 7 setup, then continue with setup.
Well, I need to actually boot to the Windows installer in order to be able to do that :)
Until I figure out a way to do that - starting to actually wonder IF I'll figure out a way with this blasted mobo - no point in formatting the SSD. But thanks for the tips, I'll be sure to do that.

I've done a lot of Windows 7 reinstall with GPT and went through all of these problems before. It's always been related to how the USB is created in my instances. DVD is an easy fix since there is no way for it to be incorrect, only one format. I just would hate to see you buy a DVD and have something not work (issues with the board, etc). Know anyone with a USB DVD drive that you could borrow?

You may also want to try a different USB creator, just in case a Rufus setting isn't right. Microsoft makes one for Windows 7. Just create the ISO with EZ and try this tool to create the USB https://www.microsoft.com/en-us/download/details.aspx?id=56485 TBH though I don't remember if this tool works with UEFI install, but it's worth a shot.
Internal DVD Writers are quite cheap, found a brand new Asus DRW-24D5MT for 12-13€ and ordered it. Will pick it up tomorrow.
I figured it might be a better idea to go for an internal one rather than external because if I connect the external one to the same USB ports which give me headaches with the flash drive, then perhaps I'll run into the same issue again.
I'm hoping that if it's connected to one of the SATA ports then maybe my chances will increase.
If it doesn't work, not a problem, I have 30 day return period, so no loss.

Did you try asking Rufus to check the device for bad blocks?

If that passes try a different USB pen.
I've encountered a few that were either tricky or impossible to make bootable.
Already ahead of you.
Yes, I did make Rufus check it for bad blocks and it passed without issues.
I did also order last week a better quality flash drive - an Patriot Supersonic Rage XT USB 3.0 - as I've read good things about it.
Will try that as well tomorrow and let you guys know.
 
Well, I need to actually boot to the Windows installer in order to be able to do that :)
Until I figure out a way to do that - starting to actually wonder IF I'll figure out a way with this blasted mobo - no point in formatting the SSD. But thanks for the tips, I'll be sure to do that.
I thought I read that you were able to get 7 installed on here in MBR mode. I assumed getting to setup screen isn't an issue for you.
 
Tried 2 other things today, both to no success.

I ordered for myself a new flash drive, a Patriot Supersonic Rage XT USB 3.0 as I've read good things about it.
It behaves exactly as the other no name one I used the other days, same error when trying to boot in UEFI with GPT partition format and FAT32 file system.

I bought an Asus DRW-24D5MT Writer and booted from a very old Win7 x64 bootable DVD I had, so old that it doesn't even have SP1 integrated.
Selected boot priority in BIOS to boot in UEFI mode first, a message comes up with "Press any key to boot from CD/DVD..." and nothing happens. Screen just goes black for a second and then it enters BIOS, or just boots from the next boot priority.
The DVD boots fine in Legacy - MBR.
Is there any reason a DVD this old would not boot in UEFI ?
I want to know if I should waste a blank DVD to write a more recent image on it.
 
Yes, a TR4 platform being tortured with a 10-11 years old OS?! Priceless.
It could be worse - to try Windows XP.
 
You could try this.
Start the install on another PC.
At the first reboot, swap to your motherboard and let it finish.
I havent tested this method but you never know.

Alternatively:
Do a full MBR installation, let it finish.
Create a backup of the 100MB boot partition and the main OS partition to another drive. Dont make this backup bootable, you do not want the system files!
Using the same drive, start Installing windows on another machine using UEFI, delete all partitions so it is completely fresh. You arent going to keep this Windows, only the system for UEFI.
After the first shut down it will have the system in place. Restore the earlier backup 100MB boot partition and the OS partition to the drive and it will use the new UEFI boot system.

I have done this many times with my current Windows installation.
My main SSD uses MBR and does not boot using the UEFI method.
But when I restore it to a backup drive that was previously UEFI, it boots UEFI and operates perfectly.
When the backup boots I select the UEFI option.


edit
I went a few steps ahead there :)
I suggest trying to create the boot USB pen on another PC, I think your PC is playing hard to get.
 
This might be strongly considered a super small last ditch try: noticed you were using the latest version of Rufus. Have you by any chance tried v2.18, going back to the last pre-3.xx version chain? It probably won't make any difference but figure it couldn't hurt trying. Some of the choices might look different.
 
I don't know if it'll work, but try enabling "Interrupt 19 capture". (int19h is the BIOS routine that boots the OS from a hard drive).
 
So, OP did you get it to work?
In UEFI mode, that would be a no.
I even tried burning a new DVD9 with a Win7 x64 MSDN image into which I've personally slipstream'd all the updates up to this point (simplix update pack). Behaves just like the antique Win7 DVD I had and refuses to boot in UEFI.

Right now I'm using it in Legacy mode which is the only way I could get it to install.

I tried this with GTX970 and then RTX2070 GPU which most certainly have UEFI drivers integrated.
I do have an Areca RAID card in another PCI-E slot, but I already tried removing it when booting from either flash drive or DVD.
No other devices connected to any of my PCI-E slots.

Even Intel states here (page 7) how Asus BIOS' should be configured for booting under UEFI when using their NVMe SSDs and I've already done that.

I really don't know what the issue is and what is preventing it from booting under UEFI, but I have given up as I'm tired, and just sticking with Legacy :(
 
Last edited:
Thanks for answer. I have same experience as you, so all that "UEFI NVMe installs" on Threadripper are equal to unicorns and dragons ;) .
I did testing on Asrock, Gigabyte and MSI boards and results are same - Legacy works, UEFI is no go.
You can pass first error, by replacing original boot.wim with one from Windows 10, but it fail after first reboot.
And to make that even more interesting, I did move disk with failed installation to Ryzen system (1700x) and it finished without problem :( .
 
AXm77 : Thanks, that's very useful info. It reassures me that it's not just me and my setup.
Well actually, now that you mentioned it, maybe it has to do with installing on NVMe SSDs? Perhaps there's something wrong with the NVMe drivers which we anyway have to manually slipstream into the Win7 image, and maybe they're not properly optimized for UEFI?

I haven't tried installing on a SATA SSD, though I do have an old Samsung 850 EVO which I tried to use for this purpose (just out of curiosity) but for some reason it wasn't listed in the boot priority, haven't managed to figure out why.
BIOS does see it plugged in the SATA port, but just doesn't list it in the boot priority.
 
Nope, I don't think drivers are problem, because with same drivers Ryzen will finish installation, but you can always try, maybe you can learn something new.
 
Ah sorry, I misunderstood your previous post. I thought you said installation failed on Ryzen, too.

Ok, then it's quite clear. If the Ryzen PC also had an NVMe SSD and you successfully installed in UEFI then it's not the drivers or the NVMe SSD itself.
It's the blasted TR4 socket :mad:

And why do I say TR4 in general and not just 1st or 2nd or the new 3rd gen of Threadrippers that will come out?
Because Asus has on their website drivers listed for Win7 for their AM4 boards, but only Win10 drivers for their TR4 boards.
Take their Prime X470 (AM4 socket) board. If you go here, you can select both Win7 and Win10. That's actually where I got all the drivers for my board except the chipset ones.
And if you want to download drivers for the Prime X399 (TR4 socket and the board I bought) from here, you can select only Win10.
 
It was exactly same disk, I moved that disk (intel 750 PCIe) to my Ryzen system to check it, UEFI itself set it as a startup disk and it finish installation.

One more thing: on what BIOS you have flashed? When I tested Asrock board with first BIOS compatible with second gen. , even legacy Win7 stop booting.
 
I initially tried installing on the BIOS the board came with, which was 0807 - the one which (similar to your AsRock board) offered support to 2nd gen Threadripper.
Then I flashed to the latest one which was 0808. It only offered improved stability.

I've got no problem in installing and booting in Legacy with either version of BIOS.
 
I did tested X399M with latest 3.5 BIOS and it did work, before I tested 3.1 and Win7 hang up on animation.
 
Hmm... then it's strictly regarding the manufacturer's BIOS.
Guess it's time to start sending some hate e-mails to Asus.

Thanks for all the replies, they've been really helpful in identifying who and what is to blame.
 
Back
Top