Windows 10: Creator's Update- Disk Layout for UEFI firmware isn't supported error

My drives do have those partitions and the drives are GPT. However I too get the same error message

 

@AndreyT, I would try moving the pagefile from drive D: to drive C:. Also, instead of using the upgrade assistant, I would download the ISO file using the Media Creation Tool, mount the ISO file, and run setup.exe from the mounted ISO file.

 

My 3-month old Win10 computer shows 4 partitions on the 1TB drive with only C: and D: being lettered, default install of Win10. I believe that's the proper way it should be done.

 

Took some figuring out from this thread and several others, but I finally solved the identical issue on my end and I'm hoping this serves as a guide for others:

My error was identical to the OP when updating to Windows 10 version 1703. Following the below link, I was able to find the error log from C:\$Windows.~BT\Sources\Panther\setupact.log.
[FIX] Windows Cant Be Installed Because This PC Has An Unsupported Disk Layout For UEFI Firmware

Went through recommended troubleshooting, recreating MSR with DISKPART - no dice.

Looking at the log more carefully revealed something strange, specifically the following line:
CONX ConX::Compatibility::CSystemAbstraction::GetSystemVolumeNtPath: Detected system partition NT path: [\Device\HarddiskVolume3]

Returned to Diskpart > list volume, it appears that C was actually Volume 5, not Volume 3 as detected.

My volume 3 actually contains my secondary boot option of Windows 7 which is not UEFI. This seems to be the root of the problem.

A quick trip to the bios allowed me to disable that drive's SATA port.

Rebooted Windows 10 without the drive, install performs as intended. It appears this specific update is not correctly identifying the drive. If you take away these other drives as options for failure, you'll force it to update on the correct drive alone.

TLDR: If you're getting this error with more than one drive, simply disable all hard drives but C where possible. This should solve your issue if you're sure you're setup for UEFI on your active GPT disk with a proper MSR.