Windows 11 [SOLVED] "There is an error selecting this partition for install" is persecuting me

• You’re getting the infamous “There is an error selecting this partition for install” after wiping the NVMe with GParted.
• Startup Repair now shows multiple broken Windows entries.
• Both drives have a mixed or incomplete partition state, and Windows install can’t proceed.

What Went Wrong?​

1. Partition Table Confusion: GParted may have left the NVMe without a usable partition table or with a format Windows Setup doesn’t like (Windows expects GPT for UEFI or MBR for legacy BIOS).
2. Boot Record Mess: Multiple failed installs have left several broken boot entries, confusing both BIOS/UEFI and Windows setup.
3. Remnants in Boot Manager: Thus the Startup Repair list full of zombies.

Cleanest Fix (with minimal hair-pulling):​

1. Back Up Anything Important​

2. Prep Both Drives (Wipe from Windows Installer)​

1. Boot with the Windows 11 USB installer.
2. When you get to the partition selection screen, press Shift + F10 to bring up the Command Prompt.
3. Type diskpart and press Enter.

In diskpart:​

• List your drives:
  list disk
• Select the NVMe and HDD one at a time (replace X with disk number):
  
  Code:

  select disk X
  clean

  (Do this for both SSD and HDD if you want both completely blank.)
• Create GPT partition table (recommended for modern UEFI systems):
  convert gpt
• Exit diskpart (exit).

3. Reboot the Installer​

• Close all windows and reboot the installer (yes, just literally restart the computer).
• When back at the install screen, you should see both drives as “Unallocated Space.”

4. Install Windows 11​

• Select the NVMe SSD, click “New” (let Windows create all needed partitions), then click “Next.”
• Install should proceed without the partition selection error.

Additional Tips:​

• BIOS Settings: Check BIOS/UEFI for:
  • Storage must be set to AHCI (not RAID or Intel Optane, unless that’s required).
  • Set Boot Mode to UEFI (not Legacy/CSM).
• Multiple Windows Entries: Once successfully installed, you can clean up the old boot entries using the command (in Command Prompt as admin):
  
  Code:

  bcdedit /enum all
  bcdedit /delete {identifier}

  Or easier: use the free tool EasyBCD.

Why Not GParted?​

TL;DR​

1. Use diskpart in the Windows installer to clean and convert gpt both drives.
2. Reboot and install Win11 fresh to the SSD.
3. Enjoy far fewer black screens!

1. All Disks Already GPT​

2. Pure UEFI, No Legacy BIOS​

3. Multiple Windows Boot Entries ("Zombies")​

• The boot records ("zombie" Windows boot entries) are stored not on a drive partition but in the EFI System Partition (ESP)—usually on the disk set as the primary boot device in UEFI, often the first drive you installed Windows on.
• The Boot Configuration Data (BCD) is in a hidden folder inside this EFI partition.

1. Access Command Prompt from Windows Install Media:
   • Boot the system using your Windows install USB.
   • At the setup screen, press Shift + F10 to open the command prompt.
2. Launch the Boot Manager tool:
   bcdedit /enum all
   • This lists all entries.
   • Note the identifiers (like {current}, {default}, {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}).
3. Delete unwanted entries:
   bcdedit /delete {identifier}
   • Only delete entries you’re sure are remnants! You can recognize duplicates—often, only the desired Windows install (on the NVMe) should remain.
4. Optional: Rebuild BCD completely (Advanced):
   If the boot entries are a mess, you can rebuild:
   
   Code:

   bootrec /scanos
   bootrec /rebuildbcd

   And, if needed:
   bootrec /fixboot
   (If these throw “Access denied,” it’s because of UEFI partition permissions, let me know if it happens and I’ll provide a workaround.)
5. Graphical Utilities:
   Tools like EasyBCD or Visual BCD Editor can make this safer if you’re comfortable booting into Windows or WinPE.

Accessing Data from the Previous Installation​

• If you have the old Windows data on the HDD (or even on a separate partition of the SSD), do not format or delete its data partition.
• During a new Windows installation, select “Custom,” and choose only the empty/unallocated space on your NVMe.
• Windows will create its required partitions on the SSD, leaving your original HDD partitions (and data) untouched.
• After Windows boots, you can browse the HDD and copy data as needed.

If you want to reuse the old Windows partition as data only:

• After copying/backup, you can reformat that partition as NTFS and use it strictly for storage.

Click to expand...

• Use bcdedit in command prompt to clean up old Windows boot entries from EFI/BCD.
• When reinstalling Windows 11, install onto the NVMe, but do not touch/format/delete partitions on your original data drive.
• Windows should then boot cleanly from SSD, and you’ll retain access to all your files on the HDD.

Here's How to Interpret and Clean Up:​

1. Firmware Application (101fffff)​

• As you said, these are system/firmware-related (USB/DVD/Network/PXE boot), and should be left untouched.

2. Bootloaders (7 Entries)​

• The one showing partition=C: is likely from your main/previous Windows install.
• Entries with only \WINDOWS\system32\winload.efi but without a clear partition are usually orphaned—these can be left behind by failed installations or incomplete OS removals.
  • If you don't have 7 distinct, valid installations, these are safe to remove. They do not point to a real Windows installation anymore and are just "ghosts".

3. Recovery Environment Bootloaders​

• Entries with displaymessageoverride Recovery or description Windows Recovery Environment refer to the Windows Recovery Environment (WinRE) on each install. You typically only need the active, valid WinRE.
• These can multiply if Windows has been reinstalled several times or on multiple drives.
• It's not strictly necessary to remove old WinRE entries—they do no harm—but if you want a tidy BCD, you can remove those that point to a deleted installation or inaccessible partition.

4. Resume from Hibernate​

• If you don't use hibernate (or have done multiple installs without cleaning), you'll see extra entries here. Windows creates these for each install environment.
• You normally only need the one corresponding to your current install.

5. Memory Tester, EMS, Debugger, RAM Defects, Global/Boot Loader Settings​

• These are standard and should not be modified or deleted.

How to Clean Up?​

1. Make a Backup!
   • Export your current BCD for safety:
     bcdedit /export C:\bcdbackup
2. Identify and Remove Orphaned Bootloaders
   • For every extra/unknown Windows Boot Loader entry:
     • Use the identifier shown by bcdedit.
     • Example to remove:
       bcdedit /delete {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
     • Repeat for unrelated or orphaned entries (but not your main C.
3. Recovery Environment & Resume from Hibernate
   • Remove only those associated with non-existent Windows installations.
   • If unsure, you can leave these alone—they won't impact booting, just clutter the list.

Will Cleaning Entries Let the Original Boot?​

• Removing the orphaned bootloader entries won't risk the functioning entry (C:), and may even let you boot to your original installation more directly.
• Cleaning up unused recovery/hibernate entries tightens things, but isn’t strictly required for normal operation.

What to Leave Untouched​

• As you suspected: firmware/EMS/Memory Tester/Debugger/Global/Boot Loader settings are generally essential and should be left alone.

Summary​

• Remove any extra Windows Boot Loader entries not needed, especially those not pointing to C: or a legitimate Windows folder.
• Only remove Recovery Environment or Resume from Hibernate if you are sure they're not associated with your live install.
• Leave system/firmware/global settings entries untouched.

ChatGPT said:

Thanks for the clarifications! Let’s address your points:

---

1. All Disks Already GPT​

That’s good—removes a big source of installer headaches.

2. Pure UEFI, No Legacy BIOS​

Excellent—less stuff to troubleshoot.

3. Multiple Windows Boot Entries ("Zombies")​

Where are these stored?

• The boot records ("zombie" Windows boot entries) are stored not on a drive partition but in the EFI System Partition (ESP)—usually on the disk set as the primary boot device in UEFI, often the first drive you installed Windows on.
• The Boot Configuration Data (BCD) is in a hidden folder inside this EFI partition.

How to clean them up?

1. Access Command Prompt from Windows Install Media:
   • Boot the system using your Windows install USB.
   • At the setup screen, press Shift + F10 to open the command prompt.
2. Launch the Boot Manager tool:
   bcdedit /enum all
   • This lists all entries.
   • Note the identifiers (like {current}, {default}, {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}).
3. Delete unwanted entries:
   bcdedit /delete {identifier}
   • Only delete entries you’re sure are remnants! You can recognize duplicates—often, only the desired Windows install (on the NVMe) should remain.
4. Optional: Rebuild BCD completely (Advanced):
   If the boot entries are a mess, you can rebuild:
   
   Code:

   bootrec /scanos
   bootrec /rebuildbcd

   And, if needed:
   bootrec /fixboot
   (If these throw “Access denied,” it’s because of UEFI partition permissions, let me know if it happens and I’ll provide a workaround.)
5. Graphical Utilities:
   Tools like EasyBCD or Visual BCD Editor can make this safer if you’re comfortable booting into Windows or WinPE.

---

Accessing Data from the Previous Installation​

• If you have the old Windows data on the HDD (or even on a separate partition of the SSD), do not format or delete its data partition.
• During a new Windows installation, select “Custom,” and choose only the empty/unallocated space on your NVMe.
• Windows will create its required partitions on the SSD, leaving your original HDD partitions (and data) untouched.
• After Windows boots, you can browse the HDD and copy data as needed.

---

Summary of What to Do:

• Use bcdedit in command prompt to clean up old Windows boot entries from EFI/BCD.
• When reinstalling Windows 11, install onto the NVMe, but do not touch/format/delete partitions on your original data drive.
• Windows should then boot cleanly from SSD, and you’ll retain access to all your files on the HDD.

If you have exported a BCD listing or any log files you’d like me to check, just let me know or upload the file. And, if you want step-by-step screenshots for any bcdedit operation, just ask!

Click to expand...

• Missing/incorrect BCD entries.
• Corrupt or missing EFI boot files.
• Windows setup not finding the right EFI/System partition.

1. Boot from Windows 11 Installation USB​

• Start your computer and boot from the USB Windows installer.

2. Open Command Prompt​

• At the "Install Windows" screen, press Shift + F10.

3. Rebuild Boot Files​

a) Identify Windows Install​

diskpart
list volume
exit

b) Rebuild EFI Boot Files​

diskpart
list disk
select disk 0  (pick your system disk)
list partition
select partition X   (pick the small, FAT32 EFI partition)
assign letter=S
exit

4. Restart​

• Remove the installer USB and boot normally.

If you still get 0xc000000e:​

• There may be leftover or corrupt boot entries. You can use:
  
  Code:

  bootrec /scanos
  bootrec /rebuildbcd
  bootrec /fixboot

  (If “Access is denied” on bootrec /fixboot, let me know.)

What is likely happening?​

ChatGPT said:

Great, you're on the right track inspecting your BCD entries!

Here's How to Interpret and Clean Up:​

1. Firmware Application (101fffff)​

• As you said, these are system/firmware-related (USB/DVD/Network/PXE boot), and should be left untouched.

2. Bootloaders (7 Entries)​

• The one showing partition=C: is likely from your main/previous Windows install.
• Entries with only \WINDOWS\system32\winload.efibut without a clear partition are usually orphaned—these can be left behind by failed installations or incomplete OS removals.
  • If you don't have 7 distinct, valid installations, these are safe to remove. They do not point to a real Windows installation anymore and are just "ghosts".

3. Recovery Environment Bootloaders​

• Entries with displaymessageoverride Recovery or description Windows Recovery Environment refer to the Windows Recovery Environment (WinRE) on each install. You typically only need the active, valid WinRE.
• These can multiply if Windows has been reinstalled several times or on multiple drives.
• It's not strictly necessary to remove old WinRE entries—they do no harm—but if you want a tidy BCD, you can remove those that point to a deleted installation or inaccessible partition.

4. Resume from Hibernate​

• If you don't use hibernate (or have done multiple installs without cleaning), you'll see extra entries here. Windows creates these for each install environment.
• You normally only need the one corresponding to your current install.

5. Memory Tester, EMS, Debugger, RAM Defects, Global/Boot Loader Settings​

• These are standard and should not be modified or deleted.

---

How to Clean Up?​

1. Make a Backup!
   • Export your current BCD for safety:
     bcdedit /export C:\bcdbackup
2. Identify and Remove Orphaned Bootloaders
   • For every extra/unknown Windows Boot Loaderentry:
     • Use the identifier shown by bcdedit.
     • Example to remove:
       bcdedit /delete {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
     • Repeat for unrelated or orphaned entries (but not your main C.
3. Recovery Environment & Resume from Hibernate
   • Remove only those associated with non-existent Windows installations.
   • If unsure, you can leave these alone—they won't impact booting, just clutter the list.

---

Will Cleaning Entries Let the Original Boot?​

• Removing the orphaned bootloader entries won't risk the functioning entry (C:), and may even let you boot to your original installation more directly.
• Cleaning up unused recovery/hibernate entries tightens things, but isn’t strictly required for normal operation.

---

What to Leave Untouched​

• As you suspected: firmware/EMS/Memory Tester/Debugger/Global/Boot Loader settings are generally essential and should be left alone.

---

Summary​

• Remove any extra Windows Boot Loader entries not needed, especially those not pointing to C: or a legitimate Windows folder.
• Only remove Recovery Environment or Resume from Hibernate if you are sure they're not associated with your live install.
• Leave system/firmware/global settings entries untouched.

---

If you’re not sure about any particular entry, feel free to copy and paste its details here (remove any identifiers for privacy if you wish), and I’ll tell you which to keep or remove!
You're very close to a neat, single-boot system—well done!

Click to expand...

Volume List Explained​

• Volume 0: USB installation media (ISO), UDF.
• Volume 1: C: – Your main Windows partition (905 GB, NTFS).
• Volume 2: D: – Likely a recovery or OEM partition (25 GB, NTFS, labeled LENOVO).
• Volume 3: SYSTEM_DRV – 260 MB, FAT32, Hidden. This is likely your EFI System Partition (ESP).
• Volume 4: WINRE_DRV – 1000 MB, NTFS, Hidden. This is likely your Windows Recovery Environment partition.
• Volume 5: Another drive, likely an HDD with data (931 GB, NTFS).
• Volume 6/7: Ventoy USB stick (exFAT/FAT).

How to Rebuild Boot Files With This Layout​

1. Assign a Letter to the EFI Partition (if it's not already assigned)​

diskpart
select volume 3
assign letter=S
exit

2. Use BCDBOOT to Rebuild Boot Files​

• This copies the correct boot files from your Windows install (C:\Windows) to the EFI partition now mounted as S:.

3. Remove Installation Media and Reboot​

• Exit Command Prompt, remove any USB installation/drives, and reboot your PC.

Notes​

• If Volume 5 (931 GB, NTFS) is a second drive, you don’t need to do anything with it—focus on the EFI/System/Windows partitions for boot repair.
• If you get any specific error after these steps, let me know verbatim what it says.

ChatGPT said:

Thanks for sharing the list volume output—this helps clarify your drive structure. Here’s a breakdown and the next steps for repairing your boot:

Volume List Explained​

• Volume 0: USB installation media (ISO), UDF.
• Volume 1: C: – Your main Windows partition (905 GB, NTFS).
• Volume 2: D: – Likely a recovery or OEM partition (25 GB, NTFS, labeled LENOVO).
• Volume 3: SYSTEM_DRV – 260 MB, FAT32, Hidden. This is likely your EFI System Partition (ESP).
• Volume 4: WINRE_DRV – 1000 MB, NTFS, Hidden. This is likely your Windows Recovery Environment partition.
• Volume 5: Another drive, likely an HDD with data (931 GB, NTFS).
• Volume 6/7: Ventoy USB stick (exFAT/FAT).

---

How to Rebuild Boot Files With This Layout​

1. Assign a Letter to the EFI Partition (if it's not already assigned)​

Since SYSTEM_DRV is the EFI partition, let's assign it the S: letter:
Open Command Prompt from the installer and run:

Code:

diskpart
select volume 3
assign letter=S
exit

2. Use BCDBOOT to Rebuild Boot Files​

Now, back at the prompt, run:
bcdboot C:\Windows /s S: /f UEFI

• This copies the correct boot files from your Windows install (C:\Windows) to the EFI partition now mounted as S:.

3. Remove Installation Media and Reboot​

• Exit Command Prompt, remove any USB installation/drives, and reboot your PC.

---

Notes​

• If Volume 5 (931 GB, NTFS) is a second drive, you don’t need to do anything with it—focus on the EFI/System/Windows partitions for boot repair.
• If you get any specific error after these steps, let me know verbatim what it says.

---

You are very close! Running bcdboot with the correct EFI volume letter should fix the 0xc000000e "boot device can't be found" error. If you see a new issue or different error, feel free to post a photo and I'll guide you further.

Click to expand...

Correct Boot Repair Steps for Installing Windows 11 on Volume 5​

1. Confirm the EFI Partition to Use​

2. Assign Drive Letters (if needed)​

diskpart
select volume 3   (EFI partition, SYSTEM_DRV)
assign letter=S
select volume 5   (your new Windows, 931 GB)
assign letter=W
exit

3. Write Boot Files for New Windows​

4. (Optional) Tidy Up BCD​

• If you want to default to booting this new install, you can set boot order in BIOS/UEFI, or adjust with bcdedit (let me know if you want the actual steps for that).
• Old/unused boot entries can be removed after you confirm everything boots as you want.

5. Reboot​

Regarding "Fixing the Original Installation"​

Summary/Best Practice​

• Use bcdboot specifying the right Windows source folder and EFI partition letter.
• Your system will allow multi-boot if you repair/add boot files for both Windows installations.
• Once set up, you can clean up duplicates in the boot menu with bcdedit or a tool like EasyBCD.

ChatGPT said:

Ah, thanks for clarifying! If Volume 5 (931 GB, NTFS) is your freshly created partition and the target for the new Windows 11 install, here’s how to approach it:

---

Correct Boot Repair Steps for Installing Windows 11 on Volume 5​

1. Confirm the EFI Partition to Use​

Your system already has an EFI partition (SYSTEM_DRV, 260 MB, FAT32, likely Volume 3). You'll want the EFI boot files for your new Windows 11 install (on Volume 5) to be written to this partition.

2. Assign Drive Letters (if needed)​

If not already assigned:

Code:

diskpart
select volume 3   (EFI partition, SYSTEM_DRV)
assign letter=S
select volume 5   (your new Windows, 931 GB)
assign letter=W
exit

Now, your new Windows partition is W: and the EFI partition is S:.

3. Write Boot Files for New Windows​

From Command Prompt, run:
bcdboot W:\Windows /s S: /f UEFI
This command copies the necessary EFI boot files for the Windows install on W: to the EFI partition S:.

4. (Optional) Tidy Up BCD​

This will add the new Windows install to your UEFI boot menu.

• If you want to default to booting this new install, you can set boot order in BIOS/UEFI, or adjust with bcdedit (let me know if you want the actual steps for that).
• Old/unused boot entries can be removed after you confirm everything boots as you want.

5. Reboot​

Close Command Prompt, remove installer media, and reboot. The system should now boot into your freshly installed Windows 11 on Volume 5.

---

Regarding "Fixing the Original Installation"​

If you want to also repair the boot files for the original install (probably on Volume 1, C:):
bcdboot C:\Windows /s S: /f UEFI
This will add both installations to the boot menu. You’ll be able to choose at boot time (unless you later remove one from boot options).

---

Summary/Best Practice​

• Use bcdboot specifying the right Windows source folder and EFI partition letter.
• Your system will allow multi-boot if you repair/add boot files for both Windows installations.
• Once set up, you can clean up duplicates in the boot menu with bcdedit or a tool like EasyBCD.

---

If you want more help with making your new Windows install the default, or instructions on cleaning up the boot menu, just ask! And if anything isn’t quite clear, send a pic of your boot menu after setup—happy to keep guiding you through.

Click to expand...

• Assign W: to the old Windows volume (Volume 1).
• Assign C: to the new Windows installation volume (Volume 5, your intended permanent install).
• Use these letters accordingly with bcdboot for boot repair, for example:

• After the install and once Windows boots, it will set C: as the active system drive for your new installation.
• If you want, you can use Disk Management later to remove or repurpose the old Windows partition.
• When you’re sure all your data and setup are working on the new install, you may consider formatting the old volume, using it for storage, or even deleting its boot entry with bcdedit.

Here’s what your plan actually achieves:​

1. diskpart clean wipes the partition table and all data—removes all boot records, EFI partitions, and hidden installer gremlins.
2. convert gpt ensures both drives are ready for pure UEFI use (modern Windows needs GPT with UEFI).
3. Letting Windows installer create partitions means the installer will generate exactly what it expects for EFI, recovery, and system—no legacy leftovers to trip things up.

Recommended Clean Install Sequence​

1. Boot from Windows install USB.
2. At the “Where do you want to install Windows?” screen, press Shift + F10 to open Command Prompt.
3. Run these commands for each drive:
   For Disk 0:
   
   Code:

   diskpart
   select disk 0
   clean
   convert gpt
   exit

   For Disk 1:
   
   Code:

   diskpart
   select disk 1
   clean
   convert gpt
   exit

4. Close Command Prompt.
5. Back in the installer, click “Refresh.” Both disks will show as unallocated space.
6. Select your NVMe SSD (or disk of choice) for Windows installation. Click New—let Windows create all needed partitions. Click Next to install.
7. You can leave the second disk unallocated for now or format it in Windows later.

Why This Works​

• Removes all prior partition/BCD/EFI confusion.
• Avoids leftover boot menu “zombies.”
• Guarantees Windows creates partitions its way.

Warning​

• This will erase all data on both drives. Make sure all needed data is backed up before proceeding!

Final note​