Dual Windows Boot winload.efi error on every restart

Step-by-Step Guide to Dual Boot Windows on Separate Drives​

1.​

• Ensure both SSDs/HDDs are installed and recognized in BIOS.
• Decide which OS goes on which drive (e.g., Windows 11 on Drive 0, Windows 10 on Drive 1).
• Disconnect the second drive while installing the first OS to avoid bootloader entanglement.

2.​

• Use the Windows Media Creation Tool or Rufus to create a bootable USB.
• Boot from the USB and install Windows on the first drive.
• Once installed, shut down and reconnect the second drive.

3.​

• Repeat the bootable USB creation for the second Windows version.
• Boot from USB and install on the second drive.
• Each OS will have its own EFI partition, keeping them independent.

Dual Boot Windows 11 and 10 on Two Physical Disks ... shows how to install Windows 10 and 11 on separate SSDs and switch between them using BIOS boot options.

Dual Boot Windows from TWO Physical SSD drivesOne ... walks through preparing the second drive, downloading ISO files, and completing installation.

4.​

• Use your BIOS/UEFI boot menu (usually F12, F10, or Esc during startup) to choose which OS to boot.
• Alternatively, install EasyBCD on one OS to create a boot menu that includes both installations.

Windows & Linux: Dual Drive Dual Boot explains how to use BIOS boot selection to keep OSes isolated and avoid bootloader conflicts.

---

Bonus: Dual Booting with Linux​

If you're mixing Windows with Linux, the process is similar but requires attention to GRUB and EFI partitions.

Dual Boot - Windows 11 and Ubuntu LTS | Separate Drive ... shows how to install Ubuntu on a separate drive with its own EFI partition.

Dual Boot Windows & Linux from TWO Separate SSD's (One ... demonstrates keeping Windows and Linux fully independent while still dual booting.

---

Tips and Considerations​

• Always back up your data before starting.
• Use GPT partitioning and UEFI boot mode for modern systems.
• Keep drives physically separate during installation to avoid bootloader overwrites.
• If you're using BitLocker, disable it before installing another OS.

---

If you're curious about doing this with just one drive, Dual Boot With Only One Drive!! explores that route—but separate drives are cleaner and safer, especially for someone like you who values control and transparency.

Want help scripting a boot menu or automating drive prep with PowerShell? I’d be glad to dive deeper.

I got the above from CoPilot . Maybe it will help.

KYHI said:

the part you still do not get is - only one drive should have an EFI partition.... so until you clean up the second drive - good luck..
As it could of been fixed in a few minutes... as I can see in your images you are not following advice...

Click to expand...

No sorry i dont get it. Should i delete the EFI partition on the broken windows? But now that i formatd the other partition as i showed you in the picture the thing that worked before dont work so i dont get into the broken windows at all now

Josey Wales said:

Step-by-Step Guide to Dual Boot Windows on Separate Drives​

1.​

• Ensure both SSDs/HDDs are installed and recognized in BIOS.
• Decide which OS goes on which drive (e.g., Windows 11 on Drive 0, Windows 10 on Drive 1).
• Disconnect the second drive while installing the first OS to avoid bootloader entanglement.

2.​

• Use the Windows Media Creation Tool or Rufus to create a bootable USB.
• Boot from the USB and install Windows on the first drive.
• Once installed, shut down and reconnect the second drive.

3.​

• Repeat the bootable USB creation for the second Windows version.
• Boot from USB and install on the second drive.
• Each OS will have its own EFI partition, keeping them independent.

Dual Boot Windows 11 and 10 on Two Physical Disks ... shows how to install Windows 10 and 11 on separate SSDs and switch between them using BIOS boot options.

Dual Boot Windows from TWO Physical SSD drivesOne ... walks through preparing the second drive, downloading ISO files, and completing installation.

4.​

• Use your BIOS/UEFI boot menu (usually F12, F10, or Esc during startup) to choose which OS to boot.
• Alternatively, install EasyBCD on one OS to create a boot menu that includes both installations.

Windows & Linux: Dual Drive Dual Boot explains how to use BIOS boot selection to keep OSes isolated and avoid bootloader conflicts.

---

Bonus: Dual Booting with Linux​

If you're mixing Windows with Linux, the process is similar but requires attention to GRUB and EFI partitions.

Dual Boot - Windows 11 and Ubuntu LTS | Separate Drive ... shows how to install Ubuntu on a separate drive with its own EFI partition.

Dual Boot Windows & Linux from TWO Separate SSD's (One ... demonstrates keeping Windows and Linux fully independent while still dual booting.

---

Tips and Considerations​

• Always back up your data before starting.
• Use GPT partitioning and UEFI boot mode for modern systems.
• Keep drives physically separate during installation to avoid bootloader overwrites.
• If you're using BitLocker, disable it before installing another OS.

---

If you're curious about doing this with just one drive, Dual Boot With Only One Drive!! explores that route—but separate drives are cleaner and safer, especially for someone like you who values control and transparency.

Want help scripting a boot menu or automating drive prep with PowerShell? I’d be glad to dive deeper.

I got the above from CoPilot . Maybe it will help.

Click to expand...

i have seperate drives. one is on a m2 drive the other one the broken one on a ssd. but it was the other way around before i changed them. i wanted my working os on my m2 drive it was on the ssd before, so i did a full image of the 2 windows and then installed windows in reverse order. so now the broken one is on ssd and working on m2.

im about to redo it. should i uncheck the EFI? if yes on which one?

Wow. All these error corrections and multiple recovery partitions. Why does it need to be so complicated? I used to struggle with dual boot constantly like this too. Then I got lazy and downloaded Easy BCD It works well for me except for when Windows tries to take out my Linux. Seems like no matter what you do Windows will try to take out Linux sooner or later.

i formated the drive this time before installing windows on it with backup. so now i dont have those partitions that was there before. but i still have the winload issue

now scanos does not find any windows installations. my working windows works i can get into it, but still in recovery it shows 0 installed windows os

in your first attachment both disks 5&7 have Fat32 EFI partitions and missing the MSR partition..
the second attachment is disk 4...

please show Marcium (i assume) full screen & all disks

and then which disk# is your Primary

What error message are you getting?

The application or operating system couldn't be loaded because a required file is missing or contains errors.
File: \Windows\system32\winload.efi
Error code: 0xc0000225

-or-

The application or operating system couldn't be loaded because a required file is missing or contains errors.
File: \Windows\system32\winload.efi
Error code: 0xc000000e

Are there any other error messages?

GreatLove said:

now scanos does not find any windows installations. my working windows works i can get into it, but still in recovery it shows 0 installed windows os

Click to expand...

Do not use the following commands.

bootrec /scanos
bootrec /rebuildbcd

That's all outdated stuff not used on UEFI/GPT based system.

KYHI said:

in your first attachment both disks 5&7 have Fat32 EFI partitions and missing the MSR partition..
the second attachment is disk 4...

please show Marcium (i assume) full screen & all disks

and then which disk# is your Primary

Click to expand...

i formated the drive thats why it has changed. disk 4 is broken windows disk 6 is working windows

aubergine said:

What error message are you getting?

The application or operating system couldn't be loaded because a required file is missing or contains errors.
File: \Windows\system32\winload.efi
Error code: 0xc0000225

-or-

The application or operating system couldn't be loaded because a required file is missing or contains errors.
File: \Windows\system32\winload.efi
Error code: 0xc000000e

Are there any other error messages?



Do not use the following commands.

bootrec /scanos
bootrec /rebuildbcd

That's all outdated stuff not used on UEFI/GPT based system.

Click to expand...

this one
The application or operating system couldn't be loaded because a required file is missing or contains errors.
File: \Windows\system32\winload.efi
Error code: 0xc000000e

See this and see if you can find anything.
Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{085744c4-7a2c-11f0-813a-806e6f6e6963}
{085744c5-7a2c-11f0-813a-806e6f6e6963}
{af83c56b-7cf9-11f0-9e7b-806e6f6e6963}
{079bdd7e-7d1a-11f0-9e83-806e6f6e6963}
{079bdd7f-7d1a-11f0-9e83-806e6f6e6963}
{079bdd80-7d1a-11f0-9e83-806e6f6e6963}
timeout 1

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {5aa463b4-7d62-11f0-8be8-a8a60f80744e}
displayorder {current}
{085744c4-7a2c-11f0-813a-806e6f6e6963}
{085744c5-7a2c-11f0-813a-806e6f6e6963}
{8d8bd708-7bf0-11f0-9e5c-806e6f6e6963}
{69ad63bf-7c53-11f0-9e67-806e6f6e6963}
{69ad63c0-7c53-11f0-9e67-806e6f6e6963}
{69ad63c1-7c53-11f0-9e67-806e6f6e6963}
{ec9f3646-7cfc-11f0-9e7c-580205bd26e5}
toolsdisplayorder {memdiag}
timeout 10
displaybootmenu Yes

Firmware Application (101fffff)
-------------------------------
identifier {079bdd7e-7d1a-11f0-9e83-806e6f6e6963}
description UEFI:CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier {079bdd7f-7d1a-11f0-9e83-806e6f6e6963}
description UEFI:Removable Device

Firmware Application (101fffff)
-------------------------------
identifier {079bdd80-7d1a-11f0-9e83-806e6f6e6963}
description UEFI:Network Device

Firmware Application (101fffff)
-------------------------------
identifier {085744c4-7a2c-11f0-813a-806e6f6e6963}
device partition=P:
description UEFI: SanDisk, Partition 1

Firmware Application (101fffff)
-------------------------------
identifier {085744c5-7a2c-11f0-813a-806e6f6e6963}
device partition=L:
description UEFI: SanDisk, Partition 2

Firmware Application (101fffff)
-------------------------------
identifier {af83c56b-7cf9-11f0-9e7b-806e6f6e6963}
device partition=M:
description UEFI: KingstonDataTraveler G2 PMAP, Partition 1

Firmware Application (101fffff)
-------------------------------
identifier {e569c198-7a93-11f0-b7cc-f1fe0e6b6131}
device partition=P:
description UEFI: SanDisk, Partition 1

Firmware Application (101fffff)
-------------------------------
identifier {e569c19a-7a93-11f0-b7cc-f1fe0e6b6131}
device partition=P:
description UEFI: SanDisk, Partition 1

Windows Boot Loader
-------------------
identifier {00c29570-7e6c-4687-b701-7b9bc7155894}
device ramdisk=[C:]\Aomei\AomeiBoot.wim,{08ec6eaa-5623-4431-8452-abaea83c7675}
description Aomei PE
osdevice ramdisk=[C:]\Aomei\AomeiBoot.wim,{08ec6eaa-5623-4431-8452-abaea83c7675}
systemroot \Windows
nx OptIn
detecthal Yes
winpe Yes

Windows Boot Loader
-------------------
identifier {1b6da1dc-500b-11f0-80f6-ebc98864acf4}
device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{1b6da1dd-500b-11f0-80f6-ebc98864acf4}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{1b6da1dd-500b-11f0-80f6-ebc98864acf4}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \windows\system32\winload.efi
description Windows 11
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \windows
resumeobject {5aa463b4-7d62-11f0-8be8-a8a60f80744e}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {94723ecd-a6d1-11ef-bfdc-d6c3724ce2ea}
device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{94723ece-a6d1-11ef-bfdc-d6c3724ce2ea}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{94723ece-a6d1-11ef-bfdc-d6c3724ce2ea}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Windows Boot Loader
-------------------
identifier {e569c196-7a93-11f0-b7cc-f1fe0e6b6131}
device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{e569c197-7a93-11f0-b7cc-f1fe0e6b6131}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{e569c197-7a93-11f0-b7cc-f1fe0e6b6131}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Windows Boot Loader
-------------------
identifier {ec9f3646-7cfc-11f0-9e7c-580205bd26e5}
device partition=D:
path \Windows\system32\winload.efi
description FL
locale en-US
osdevice partition=D:
systemroot \Windows
nx OptIn

Resume from Hibernate
---------------------
identifier {5aa463b4-7d62-11f0-8be8-a8a60f80744e}
device partition=C:
path \windows\system32\winresume.efi
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
custom:21000026 partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {e569c194-7a93-11f0-b7cc-f1fe0e6b6131}
device partition=C:
path \WINDOWS\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {e569c196-7a93-11f0-b7cc-f1fe0e6b6131}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
custom:21000026 partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {fbe69249-7c87-11f0-814e-806e6f6e6963}
device partition=D:
path \Windows\system32\winresume.efi
description FL
locale en-US
inherit {resumeloadersettings}
filedevice partition=D:
custom:21000026 partition=D:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-us
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Local

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {04a7f7d9-1dd2-4dc8-8388-3c1f528d3afa}
ramdisksdidevice unknown
ramdisksdipath \Aomei\AomeiBoot.sdi

Device options
--------------
identifier {08ec6eaa-5623-4431-8452-abaea83c7675}
ramdisksdidevice partition=C:
ramdisksdipath \Aomei\AomeiBoot.sdi

Device options
--------------
identifier {1b6da1dd-500b-11f0-80f6-ebc98864acf4}
description Windows Recovery
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {5d5f0a9e-7b5b-11f0-9e51-ca5fb35d7e19}
description Windows Setup
ramdisksdidevice partition=C:
ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi

Device options
--------------
identifier {94723ece-a6d1-11ef-bfdc-d6c3724ce2ea}
description Windows Recovery
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {cee0c180-c0dc-464b-8990-7c099a0bfc8e}
ramdisksdidevice partition=C:
ramdisksdipath \Aomei\AomeiBoot.sdi

Device options
--------------
identifier {e569c197-7a93-11f0-b7cc-f1fe0e6b6131}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume4
ramdisksdipath \Recovery\WindowsRE\boot.sdi

GreatLove said:

this one
The application or operating system couldn't be loaded because a required file is missing or contains errors.
File: \Windows\system32\winload.efi
Error code: 0xc000000e

Click to expand...

I have had the same error message in a virtual machine (image below). I failed to fix the 0xc000000e error in the virtual machine. Dual boot installation (one is cloned), one worked the other didn't.



This seems to be the most difficult error code because the error code can be caused by many things.

If you get a 0xc000000e error, even though you format the EFI system partition before the BCDBOOT command, then the problem is somewhere other than the EFI system partition.

If you get a 0xc000000e error, but Windows starts by selecting "Windows Boot Manager" from the boot menu, then there is a incorrect "Windows Boot Manager" entry in the BIOS settings.

For some users, the 0xc000000e error has been resolved by disabling the Fast Boot feature in the BIOS settings.

aubergine said:

I have had the same error message in a virtual machine (image below). I failed to fix the 0xc000000e error in the virtual machine. Dual boot installation (one is cloned), one worked the other didn't.

View attachment 142827

This seems to be the most difficult error code because the error code can be caused by many things.

If you get a 0xc000000e error, even though you format the EFI system partition before the BCDBOOT command, then the problem is somewhere other than the EFI system partition.

If you get a 0xc000000e error, but Windows starts by selecting "Windows Boot Manager" from the boot menu, then there is a incorrect "Windows Boot Manager" entry in the BIOS settings.

For some users, the 0xc000000e error has been resolved by disabling the Fast Boot feature in the BIOS settings.

Click to expand...

Fast boot is already disabled. I get that error from windows boot manager where you can choose which windows you want to start. i can choose my broken windows but i get that error if i do, my other windows boots no problem

GreatLove said:

device partition=\Device\HarddiskVolume1

Click to expand...

Which Harddisk... Use Bootice and picture... We know it is the First Volume ( First Partition ) of whatever disk ??

Cloning an OS make a Duplicate of that OS Partition, thus most likely same Volume GUID...
Cloning is for adding a New Disk and Removing the Other...

Also when copying the OS - you only want to copy just the OS Partition, not the whole disk unless you intend to remove the old disk...

also why are you duplicating the existing OS - instead of Installing a Fresh New OS ( Clean Install ) to the second drive?

KYHI said:

also why are you duplicating the existing OS - instead of Installing a Fresh New OS ( Clean Install ) to the second drive?

Click to expand...

its 2 diffrent kind of windows, its 11 but its not the same one. one is fresh install (my working windows) the other is an older windows 11 that i need with everything installed in it.

Use EasyBCD to manage your Boot loader

You can copy your X:\Users\UserName folders (ie) Desktop,. Downloads, Documents etc from your older Windows 11 drive to your fresh install of Windows 11 in the same folders and install any of your 3rd party apps. (Change X: to the proper drive letter if booted into the newer Windows)

Im in no need for the old windows anymore, ill just use this new one and remove the other one once i have backed up everything

OK, if you have everything you need from the old Windows.
Press the Windows key +X choose Disk Management
Select all the partitions and Delete them.
You can also do this with the free partitioning app like Minitool Partition Wizard
Making the drive all Unallocated Space
right click that and choose to create a New Simple Volume.
Format NTFS and assign it a drive letter, use it for storage.