I am running Win 10 TP build 9926 and earlier today received notification that fbl_impressive 10041 professional was available for download.  The update downloaded without a problem but at 9% preparation to install I received the message:-

"Couldn't install Windows 10 Technical Preview.  Windows can't be installed because this PC has an unsupported disk layout for UEFI firmware.  Please reboot and change the PC's firmware to BIOS to allow Windows to setup to continue."

Win 10 TP build 9926 is installed on an ASUS Z97 Deluxe motherboard with an SSD formatted GPART and using the full UEFI bios.  Can anyone please tell me what is meant by "change the PC's firmware to BIOS to allow Windows to setup"

I think it's the gpart disk formatting....

Renee

I have the same problem here. I installed with UEFI and I have a second partition with Windows 8.1 Pro x64. 

I am going to try rebooting enabling BOIS and then report back. 

Good luck everyone! 

• Edited by mitchell-vb Thursday, March 19, 2015 11:51 AM Word correction ('Samen' should be 'Same'.

Instead of saying: "Samen over here" or "Same Problem" (including me, I've actually the same problem), can't someone just give a solution if there is even one...

I am sure that if anyone had a solution then they would present it here.  Until an answer arrives however there is a standard process to follow:-

1. Report the issue to Microsoft via the feedback app and supply as much information as possible - I have done that.  Like all other original posters (OP's), my first reaction is "am I alone" or are others having the same problem?.  This is important because if you are alone then there is a low probability of finding an answer.  However, if many people have the same problem then there is a higher probability of finding a solution -i.e. there is power in the many!
2. I am happy to receive "same here" responses.  I now know that I am not alone.
3. As the number of people with the same problem rises then Microsoft will take action - especially here on Technet.

I hope that this helps those who wonder about the value of "same here" responses.

• Edited by Middleleaze Thursday, March 19, 2015 11:08 AM

Instead of saying: "Samen over here" or "Same Problem" (including me, I've actually the same problem), can't someone just give a solution if there is even one...

I am sure that if anyone had a solution then they would present it here.  Until an answer arrives however there is a standard process to follow:-

1. Report the issue and supply as much information as possible.  Like all other original posters (OP's), my first reaction is "am I alone" or are others having the same problem?.  This is important because if you are alone then there is a low probability of finding an answer.  However, if many people have the same problem then there is a higher probability of finding a solution -i.e. there is power in the many!
2. I am happy to receive "same here" responses.  I now know that I am not alone.
3. As the number of people with the same problem rises then Microsoft will take action - especially here on Technet.

I hope that this helps those who wonder about the value of "same here" responses.

Just one thing.

None of the above will make a dent unless you report your problem to Microsoft by using the Feedback app.

Posting here rarely gets the attention from Microsoft.

• Edited by david hk129 Thursday, March 19, 2015 10:15 AM

Instead of saying: "Samen over here" or "Same Problem" (including me, I've actually the same problem), can't someone just give a solution if there is even one...

I am sure that if anyone had a solution then they would present it here.  Until an answer arrives however there is a standard process to follow:-

1. Report the issue and supply as much information as possible.  Like all other original posters (OP's), my first reaction is "am I alone" or are others having the same problem?.  This is important because if you are alone then there is a low probability of finding an answer.  However, if many people have the same problem then there is a higher probability of finding a solution -i.e. there is power in the many!
2. I am happy to receive "same here" responses.  I now know that I am not alone.
3. As the number of people with the same problem rises then Microsoft will take action - especially here on Technet.

I hope that this helps those who wonder about the value of "same here" responses.

Just one thing.

None of the above will make a dent unless you report your problem to Microsoft by using the Feedback app.

Posting here rarely gets the attention from Microsoft.

• Edited by Middleleaze Thursday, March 19, 2015 11:07 AM

I have solved it.

made a blogpost explaining what you need to do :)

https://moln1.wordpress.com/2015/03/19/solved-couldnt-install-windows-10-technical-preview/

Tried that for my issue (same as above) but didn't work.

Still get the error about disk and uefi, then says 0x8024200D.

I have the same issue on Asus Tab (me400c) and I have *no* idea how to change the BIOS settings. It is also not worth the effort at this point.  Build 9926 was OK but dog-slow.

Rolling back to 8.1

.......... I have since checked and my item does appear in the "Most Recent" list but, as yet, there are no suggestions.................

MS does not reply back to individual Insider who posted the feedback.

The Feedback app is the means for MS to tally up all the problems posted, prioritize the list and then decide which are to be tackled.

There is nothing more you can do after you posted on the feedback app.

Thank you! This worked for me, too!

On Asus VivoTab Smart (ME400C)

I have solved it.

made a blogpost explaining what you need to do :)

https://moln1.wordpress.com/2015/03/19/solved-couldnt-install-windows-10-technical-preview/

I have the same issue here. Essentially what it is saying is that your disk partition style is set to the older MBR style which doesn't allow for UEFI installs. For a quick fix you can do this. Windows menu > Shift Click on Restart > Advanced Settings > UEFI Settings or something similar. From there in your "bios settings" some manufactures allow you to change the bios mode from secure or uefi, to legacy or bios and try again. But what is odd is that in order for you to be running the 9926 build with UEFI mode on, your partition style has to GPT (the newer, required style) in the first place. So from what I can tell Windows is incorrectly detecting detecting your partition style as MBR... which isn't possible if you're upgrading. I wouldn't recommend the fix I gave as you lose the security and boot speed of UEFI, as well as that windows will hopefully fix this anyways.

Hello,

See the answer on this thread and try that .

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/error-when-installing-build-10041-windows-cant-be/e08699a9-f803-4cb6-8304-75a36ec9050c?tm=1426811995041

I am running Win 10 TP build 9926 and earlier today received notification that fbl_impressive 10041 professional was available for download.  The update downloaded without a problem but at 9% preparation to install I received the message:-

"Couldn't install Windows 10 Technical Preview.  Windows can't be installed because this PC has an unsupported disk layout for UEFI firmware.  Please reboot and change the PC's firmware to BIOS to allow Windows to setup to continue."

Win 10 TP build 9926 is installed on an ASUS Z97 Deluxe motherboard with an SSD formatted GPART and using the full UEFI bios.  Can anyone please tell me what is meant by "change the PC's firmware to BIOS to allow Windows to setup"

• Proposed as answer by Stan Kay 22 minutes ago