UEFI Bootable USB Flash Drive - Create in Windows

[Sagnalrac]

Are you using a USB 3.0 port?

Hi theog!

When I read your question the first time, I was wondering why did you ask that. But after a little research, it seems that USB 3.0 ports need an OS to function properly. At least that was I understood from this post:

How To Fix Boot/BCD 0xc000000f Error Windows 7 | Think Like A Computer


Thanks and Greetings!

 

[Sky90po]

Under Format Options, check Quick format.

Is it better to uncheck these? thx

 

[Akeo]

If you are using a flash drive, no. All this does is fill all sectors of the drive with zeroes, which is a very slow operation that will also reduce the life of your drive, as flash memory (especially the one in cheap flash drives) has a much more limited number of write cycles before failure compared to regular HDDs.

Unless you have a need to erase any trace of your old data (which isn't something that this method will guarantee as flash drives are known to reorganize sectors around, and could remap existing sectors as spares that won't be erased), unchecking the option is pointless, which is why it is selected in Rufus by default.

 

[B Ogbrsh]

I'm trying to install Windows 10 64bit on my UEFI motherboard.

I created my Win 10 installation USB drive using Rufus and created the drive using the GPT partition scheme with 32bit file system.

I configured my internal HDD with the GUID partition scheme.

When I boot from the USB drive everything seems to be going fine until I get to the point of choosing the HDD to install to, then the installation stopw with the error message that the HDD has the MBR partition scheme even though I partitioned it with GUID.

Why is the installation not seeing the correct partition scheme?

 

[Akeo]

Please realize that the GPT partition scheme you select in Rufus applies only to the USB you boot from, not the internal HDD you install Windows to.

Whatever you select in Rufus becomes completely irrelevant once the Windows installer has booted (though it may help to ensure that Windows boots in UEFI mode and not in BIOS mode). Especially, it's not because you selected GPT in Rufus that the Windows installer will automatically use GPT for the partition scheme.

You probably need to clear/repartition your HDD (which seems to be MBR - and Rufus cannot change that on its own) from the Windows installer so that it will be converted to GPT. But this is a Windows installer issue, not a Rufus issue.

 

[Clintlgm]

I'm trying to install Windows 10 64bit on my UEFI motherboard.

I created my Win 10 installation USB drive using Rufus and created the drive using the GPT partition scheme with 32bit file system.

I configured my internal HDD with the GUID partition scheme.

When I boot from the USB drive everything seems to be going fine until I get to the point of choosing the HDD to install to, then the installation stopw with the error message that the HDD has the MBR partition scheme even though I partitioned it with GUID.

Why is the installation not seeing the correct partition scheme?

Your trying to use a 32 but OS in UEFI that's not going to work UEFI requires 64bit OS After making your 64bit install USB with Rufus or Windows tool use diskpart to clean your hard drive then let the Windows install create the needed partitions to run UEFI GPT

 

[B Ogbrsh]

I'm trying to install Windows 10 64bit on my UEFI motherboard.

I created my Win 10 installation USB drive using Rufus and created the drive using the GPT partition scheme with 32bit file system.

I configured my internal HDD with the GUID partition scheme.

When I boot from the USB drive everything seems to be going fine until I get to the point of choosing the HDD to install to, then the installation stopw with the error message that the HDD has the MBR partition scheme even though I partitioned it with GUID.

Why is the installation not seeing the correct partition scheme?

Your trying to use a 32 but OS in UEFI that's not going to work UEFI requires 64bit OS After making your 64bit install USB with Rufus or Windows tool use diskpart to clean your hard drive then let the Windows install create the needed partitions to run UEFI GPT

I was installing the 64bit version.

I had made the mistake of formatting and partitioning the drive to FAT/GPT before I started the Win 10 installation which in my case did not work.

So, during the installation I started a command prompt and ran 'diskpart', identified my drive and used the 'clean' command to prepare the drive. This time the partition was recognised and the installation proceeded without a hitch.

I still don't know how a previously prepared drive created with the GPT partition scheme was recognised by the Win 10 installer as MBR?

 

[Akeo]

The problem when you talk about "drive" is we don't know if you're talking about your USB drive or the internal HDD drive that you are installing Windows onto. These are 2 completely separate disks, and the only one that matters for Windows, in terms of partition scheme, is the HDD.

So when you say "a previously prepared drive created with the GPT partition scheme" I have to assume that you are talking about the USB drive, which, as far as Windows is concerned, and as I previously explained, is completely irrelevant to the Windows installer process, since it is NOT the disk you're installing Windows onto. It could be using a wild file system and your own custom partition scheme, and the Windows installer would be just fine as long as it can boot and read the installation files from it. So the fact that that drive is GPT is completely irrelevant to the whole installation process.

The only thing that matters to Windows is the target drive, i.e. the internal HDD. When Windows complains that it's unhappy with that drive because it's using the MBR partition scheme, I believe it, because if the only thing you did was create an USB installation drive in Rufus, you certainly did not change the partition scheme from that drive, which was probably MBR. And this is further corroborated by the fact that after you applied the 'clean' command to your installation HDD (which does remove the partition scheme), the installer was fine, since it could now create the partition scheme it wanted on that drive.

So really, everything you are stating above makes sense, unless you are indicating that you did attempt to manually change your target HDD to GPT partition scheme. But if that's the case, then you clearly did something wrong, since that's not what the Windows installer saw as being used by your target drive until you used diskpart.

 

[Clintlgm]

I'm trying to install Windows 10 64bit on my UEFI motherboard.

I created my Win 10 installation USB drive using Rufus and created the drive using the GPT partition scheme with 32bit file system.

32 bit and GPT are incompatible Your USB should have been formatted Fat 32 your Target hard drive should have been cleaned and converted GPT or just left clean.

I configured my internal HDD with the GUID partition scheme.

Again Target HD should be Clean or Clean and converted to GPT

When I boot from the USB drive everything seems to be going fine until I get to the point of choosing the HDD to install to, then the installation stopw with the error message that the HDD has the MBR partition scheme even though I partitioned it with GUID.

Why is the installation not seeing the correct partition scheme?

Your trying to use a 32 but OS in UEFI that's not going to work UEFI requires 64bit OS After making your 64bit install USB with Rufus or Windows tool use diskpart to clean your hard drive then let the Windows install create the needed partitions to run UEFI GPT

I was installing the 64bit version.

I had made the mistake of formatting and partitioning the drive to FAT/GPT before I started the Win 10 installation which in my case did not work.

Yes FAT is for BIOS and GPT is for UEFI, both Systems you either have one or the other for OS HD/SSD . In you case your HD remained FAT

So, during the installation I started a command prompt and ran 'diskpart', identified my drive and used the 'clean' command to prepare the drive. This time the partition was recognised and the installation proceeded without a hitch.

You solved the problem By entering Diskpart and Cleaning your HD which allowed the windows install to create the UEFI needed partitions

I still don't know how a previously prepared drive created with the GPT partition scheme was recognised by the Win 10 installer as MBR?

Yes were all either just learned or are learning this new UEFI system it is a much better system than BIOS/MBR but a little tricky to install to until you understand the way of it. https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface explains the system technically.

 

[B Ogbrsh]

[SOLVED]

Your trying to use a 32 but OS in UEFI that's not going to work UEFI requires 64bit OS After making your 64bit install USB with Rufus or Windows tool use diskpart to clean your hard drive then let the Windows install create the needed partitions to run UEFI GPT

I was installing the 64bit version.

I had made the mistake of formatting and partitioning the drive to FAT/GPT before I started the Win 10 installation which in my case did not work.

Yes FAT is for BIOS and GPT is for UEFI, both Systems you either have one or the other for OS HD/SSD . In you case your HD remained FAT

So, during the installation I started a command prompt and ran 'diskpart', identified my drive and used the 'clean' command to prepare the drive. This time the partition was recognised and the installation proceeded without a hitch.

You solved the problem By entering Diskpart and Cleaning your HD which allowed the windows install to create the UEFI needed partitions

I still don't know how a previously prepared drive created with the GPT partition scheme was recognised by the Win 10 installer as MBR?

Yes were all either just learned or are learning this new UEFI system it is a much better system than BIOS/MBR but a little tricky to install to until you understand the way of it. https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface explains the system technically.

Hi

Thanks for the reply.

My system is UEFI. When I created the USB Win 10 installer (drive, stick, device ,medium I never know what to call it) I created it on a Windows machine using Rufus, this creates a (I'll call it a USB stick) with the GPT partition scheme and the FAT filing system. This is fully recognised by the machine and installation proceeds as normal.

When I choose a HDD for the installation of Win 10 I first installed the drive in a Hackintosh machine and used OS X El Capitan 'disk utility' to partition the new HDD with the GUID (GPT) partition scheme with the FAT file system The same as the USB stick, I then removed the newly created HDD and installed it in the new machine and ran the Win 10 installer which told me the HDD had a MBR partition scheme.

When I re-installed the HDD in the Hackintosh disk utility reports the HDD as having the GUID partition scheme??

Next time I will leave the target HDD alone and let the Windows 10 installer sort the drive out.

 

[Akeo]

and used OS X El Capitan 'disk utility' to partition the new HDD with the GUID (GPT) partition scheme with the FAT file system The same as the USB stick

Why? Windows can NOT be installed on a FAT filesystem. It should be NTFS. But then again, Windows does NOT need you to format the file system beforehand (it would be a pretty lousy installer if it couldn't create the file system it wants to install the OS).

Once again, the way you partitioned and formatted the USB is irrelevant to how you need to partition and format the target disk. It's not because the USB was using GPT and FAT that your target drive has to use GPT and FAT, or that you actually need to format your target drive at all.

I'm pretty sure that what the installer was really complaining about, if the only available partition on your target drive was using a FAT filesystem, was that there was no partition it could use to install Windows.

If both your USB and the target HDD were indeed using the GPT partition scheme, and you had formatted the partition you wanted to use for Windows installation on the target HDD with a FAT file system, the installer will definitely complain about that.

Next time I will leave the target HDD alone and let the Windows 10 installer sort the drive out.

Good thinking. Only the OS installer knows what it really needs to install the OS, and is usually smart enough to create it. Trying to second guess, and create things beforehand is usually a recipe for issues.

 

[vx544]

hello, i got problem n still unresolve..

trying to install win 7 64 bit for my sony vaio E series.. but got stack and cant do anything.

when im using legacy mode, it can go through booting to enter instalation proccess but got error on partitioning menu, it says "windows cannot be installed on this disk, this computer hardware blablablabla. ensure that the disk blablabla".

so i think i should use uefi mode, but no progress at all,it stuck at logo screen booting no matter how many times i've tried.

then i tried using bootable usb efi (in this thread tutorial). again, it got stuck with error at booting "\EFI\Microsoft\BOOT\BCD. Status 0xc0000000d" no matter how many times i've tried, either using rufus or manually.

my goal is to be able to install win 7 64 bit.

btw SV's bios is somewhat simple, it's just provide boot mode and priority change, no advance boot for like CSM n stuff i've been reading.

pls help..:huh:

 

[Brink]

Hello vx544, and welcome to Eight Forums.

You might see if the solution in the thread below may be able to help you as well.

\BOOT\BCD 0xc000000d unreadable boot configuration data Solved - Windows 7 Help Forums

 

[SteelCat33]

Hi guys,

I may be missing something and I have to admit I didn't read all the 52 pages of subnotes and the rest of the forum. So if this was solved before, I apologize and would be satisfied with just a link to that thread.

Any ways this is my problem.

I'm trying to create a UEFI USB flash drive to install Win 7 Pro x64 with SP1. I tried twice using Rukus and then becouse it didn't work once with "Diskpart", both times using instructions on this forum.

When I select it from the boot options it hangs on the black screen, before the Win logo starts to esemble or what ever MS called that.

My current configuration is: Win 10 Ent, installed with GPT and UEFI, secure and fast boot disabled.
I have cretated a vsdx. on dirve D:\
My only goal is to get the working Win 7 Pro intallation and then officaly upgrade it to Win 10 before 29.7.

Tnx for any inside.

Regards,
SteelCat

 

[Brink]

Hello SteelCat, and welcome to Eight Forums.

Where did you get the Windows 7 ISO from? If not from an official source (ex: Microsoft), then that could be the issue.

 

[SteelCat33]

Hello Brink,

tnx for a quick reply. The image is from an officiall source, but it was modifed so it doesn't ask you for a key, in the first part of setup. Insted it displays a list of Windows images on the drive (similar that it was with Win Vista, if you choose to imput your key later).

But I installed with that image before in non UEFI mode and It was fine.

I have an RTM version also somewhere, I will try with that later.

Regards,
SteelCat

P.S.: One more question does the actvation of a free genuine windows 10 differentiate between boot modes when it makes your harware fingerprint. As I said my goal is to get a working win10 licence so I might be able to use it later. It would be a shame to vaste a working win7 key.

 

[Brink]

It's possible that whatever you did to modify it will cause it not to work with UEFI, and only Legacy BIOS.

Activation isn't affected by installing in UEFI or Legacy BIOS.

 

[Gnomer]

I was attempting to install Windows 7 x64 on a GPT disk and was getting the "Windows cannot be installed to this disk. The selected disk is of the GPT partition style." error because my USB would not boot in UEFI mode.

Step 11 was a lifesaver, it was exactly what I needed to make it work. Thank you so much for this tutorial!

 

[Brink]

Hello Gnomer, and welcome to Eight Forums.

For Windows 7 issues, it would be best to post at our sister site Windows 7 Help Forums instead.

You might see if this below may help for now.

UEFI (Unified Extensible Firmware Interface) - Install Windows 7 with - Windows 7 Help Forums

 

[mikzaman]

thxx