MildBill

Member
Joined
Aug 17, 2025
Messages
4
Hi, here is my issue. I have an HP 17-cp3047nr laptop it came with Windows 11 Home installed, I immediately upgraded it to Windows 11 Pro. Computer worked fine. I have had it for about 4 months. I was using easeus partition master to format an SD card. The computer all of a sudden reboots and somehow my windows os is corrupted. So using ventoy i booted into linux used Gparted to delete the drive and create a new GPT NTFS drive.The bios is setup to boot as uefi however when I try to install Windows on it from a USB flash drive it gives an error that it can't install to that drive. I took the drive out of the lap top and reformatted it on another of Windows computers with easus and put it back in my laptop and used a different windows boot drive same problem will not install to this drive.
 

Thanks — good detail. Short answer: this is almost always either a leftover partition/partition‑table problem (Windows dislikes how GParted/EaseUS left the disk), a storage‑mode/driver mismatch (RAID/IRST vs AHCI or missing NVMe driver), or failing/locked hardware. The quickest reliable fix is to wipe the disk from the Windows installer with diskpart (so Windows creates the correct GPT/EFI layout) and confirm firmware settings first. Below I give a safe, ordered checklist you can follow and what to report back if it still fails.
What to check first (quick):
  • Is the drive internal (M.2 NVMe or SATA) or an external SD/USB? (You said internal laptop drive, confirm NVMe vs SATA.)
  • Post the exact installer error text (copy it or take a photo). That message matters.
  • If you have another internal/data drive attached, disconnect it while installing (prevents confusion and leftover boot entries).
Recommended step‑by‑step (do this from the Windows 11 USB installer)
1) Boot the installer and open a Command Prompt (Shift + F10). Then run diskpart and do this (replace X with the target disk number shown by list disk):
  • diskpart
  • list disk
  • select disk X
  • clean
  • convert gpt
  • create partition efi size=100
  • format quick fs=fat32 label=System
  • create partition msr size=16
  • create partition primary
  • format quick fs=ntfs label=Windows
  • assign letter=C
  • exit
    This forces a clean GPT + correct EFI and MSR partitions so Windows Setup can install. Many successful fixes use this exact flow. n → select the NTFS partition you created (or simply select the unallocated space after running clean/convert and click New so Setup builds partitions automatically). This avoids Linux/GParted-created metadata that Setup dislikes.
3) Check BIOS/UEFI settings (power off, eBoot mode = UEFI (not Legacy/CSM).
  • Storage mode = AHCI (not RAID/Intel RST). If the laptop is set to RAID/IRST, either switch to AHCI or load the OEM IRST driver during Setup. Many HPs default to Intel RST/RAID and that will prevent install unless the correct driver is loaded.
  • Temporarily disable Secure Boot while troubleshooting (re-enable after successful install).
    If you find “RAID” or “Intel RST” enabled, either change to AHCI (and then reinstall) or download the IRST driver from HP and “Load driver” in Setup.
4) If Windows setup reports it cannot find/format the disk or asks for drivers, try loading the storage/NVMe driver from an HP support USB (put driver files on a second USB and use “Load driver” in Setup). This is the usual cure when the installer can’t talk to an NVMe controller.
5) If the disk still refuses install after the above:
  • Test the drive health on another PC ( run CrystalDiskInfo or smartctl). A failing SSD will act weird after partitioning attempts. Forum reports show driver/device errors after cloning/partitioning that indicated hardware or driver faults (stornvme-type errors). If you see device driver errors in Event Viewer or the drive disappears from Linux tools intermittently, consider hardware failure.
Extra troubleshooting notes
  • Avoid reformatting the disk in Linux/GParted before trying the Windows installer; Windows setup prefers being given an unallocated disk (or use diskpart as above) so it can create the EFI/MSR/Windows partitions correctly.
  • If you get an error like “Windows cannot be installed to this disk. The selected disk has an MBR partition table…” it means the disk is MBR while firmwvert gpt step fixes that. If the error is different, tell me the exact text.
  • If you see “Access denied” running bootrec /fixboot during repairs, that’s an EFI permission quirk — I can give the workaround if you hit that.
What I need from you if thxact installer error text or a photo of the partition selection screen.
  • The Diskpart output from the Windows installer (run: diskpart → list diskst partition). Paste those outputs here.
  • Confirm whether the drive is NVMe (M.2) or a SATA HDD/SSD, and whether you tried installing with any other drives attached.
If you want, I’ll walk you through each diskpart command step‑by‑step while you’re at the installer. Start with the diskpart clean/convert gpt flow above and tell me the installer message if it still refuses — we’ll take it from there.
 

Thanks — good detail. Short answer: this is almost always either a leftover partition/partition‑table problem (Windows dislikes how GParted/EaseUS left the disk), a storage‑mode/driver mismatch (RAID/IRST vs AHCI or missing NVMe driver), or failing/locked hardware. The quickest reliable fix is to wipe the disk from the Windows installer with diskpart (so Windows creates the correct GPT/EFI layout) and confirm firmware settings first. Below I give a safe, ordered checklist you can follow and what to report back if it still fails.
What to check first (quick):
  • Is the drive internal (M.2 NVMe or SATA) or an external SD/USB? (You said internal laptop drive, confirm NVMe vs SATA.)
  • Post the exact installer error text (copy it or take a photo). That message matters.
  • If you have another internal/data drive attached, disconnect it while installing (prevents confusion and leftover boot entries).
Recommended step‑by‑step (do this from the Windows 11 USB installer)
1) Boot the installer and open a Command Prompt (Shift + F10). Then run diskpart and do this (replace X with the target disk number shown by list disk):
  • diskpart
  • list disk
  • select disk X
  • clean
  • convert gpt
  • create partition efi size=100
  • format quick fs=fat32 label=System
  • create partition msr size=16
  • create partition primary
  • format quick fs=ntfs label=Windows
  • assign letter=C
  • exit
    This forces a clean GPT + correct EFI and MSR partitions so Windows Setup can install. Many successful fixes use this exact flow. n → select the NTFS partition you created (or simply select the unallocated space after running clean/convert and click New so Setup builds partitions automatically). This avoids Linux/GParted-created metadata that Setup dislikes.
3) Check BIOS/UEFI settings (power off, eBoot mode = UEFI (not Legacy/CSM).
  • Storage mode = AHCI (not RAID/Intel RST). If the laptop is set to RAID/IRST, either switch to AHCI or load the OEM IRST driver during Setup. Many HPs default to Intel RST/RAID and that will prevent install unless the correct driver is loaded.
  • Temporarily disable Secure Boot while troubleshooting (re-enable after successful install).
    If you find “RAID” or “Intel RST” enabled, either change to AHCI (and then reinstall) or download the IRST driver from HP and “Load driver” in Setup.
4) If Windows setup reports it cannot find/format the disk or asks for drivers, try loading the storage/NVMe driver from an HP support USB (put driver files on a second USB and use “Load driver” in Setup). This is the usual cure when the installer can’t talk to an NVMe controller.
5) If the disk still refuses install after the above:
  • Test the drive health on another PC ( run CrystalDiskInfo or smartctl). A failing SSD will act weird after partitioning attempts. Forum reports show driver/device errors after cloning/partitioning that indicated hardware or driver faults (stornvme-type errors). If you see device driver errors in Event Viewer or the drive disappears from Linux tools intermittently, consider hardware failure.
Extra troubleshooting notes
  • Avoid reformatting the disk in Linux/GParted before trying the Windows installer; Windows setup prefers being given an unallocated disk (or use diskpart as above) so it can create the EFI/MSR/Windows partitions correctly.
  • If you get an error like “Windows cannot be installed to this disk. The selected disk has an MBR partition table…” it means the disk is MBR while firmwvert gpt step fixes that. If the error is different, tell me the exact text.
  • If you see “Access denied” running bootrec /fixboot during repairs, that’s an EFI permission quirk — I can give the workaround if you hit that.
What I need from you if thxact installer error text or a photo of the partition selection screen.
  • The Diskpart output from the Windows installer (run: diskpart → list diskst partition). Paste those outputs here.
  • Confirm whether the drive is NVMe (M.2) or a SATA HDD/SSD, and whether you tried installing with any other drives attached.
If you want, I’ll walk you through each diskpart command step‑by‑step while you’re at the installer. Start with the diskpart clean/convert gpt flow above and tell me the installer message if it still refuses — we’ll take it from there.
I will get to this ASAP
 

Great — thanks for the follow‑up. Sounds like you’ve got the right plan. When you’re ready, I can walk you through the exact diskprep and install steps from the Windows installer (Shift+F10 → diskpart) and troubleshoot whatever error shows up. Wiping the disk with diskpart so Windows creates the EFI/MSR/C: layout usually fixes this; likewise check for RAID/IRST vs AHCI storage mode because that will stop the installer cold. u follow now or I’ll walk you through live)
  • Make a full backup of any data if you haven’t already.
  • Disconnect any other internal/external drives and USB sticks except the Windows installer USB.
  • Confirm whether the internal drive is NVMe (M.2) or SATA.
  • Boot the Windows USB in UEFI mode (boot menu shows “UEFI: …”). If it’s booting legacy/CSM, recreate USB as UEFI/GPT or choose the UEFI boot entry.
  • In BIOS: set storage to AHCI (not RAID/Intel RST). If it must stay RST, download the OEM IRST driver and load it from a second USB during setup.
If you want to try the fast diskprep now‑line)
  1. Boot installer → press Shift+F10 to open Command Prompt.
  2. In CMD:
    • diskpart
    • list disk ← post the output here (or paste it)
    • select disk X ← replace X with the disk number matching your internal drive (double‑check size)
    • clean
    • convert gpt
    • create partition efi size=100
    • format quick fs=fat32 label=System
    • create partition msr size=16
    • create partition primary
    • format quick fs=ntfs label=Windows
    • exit
  3. Close CMD, click Refresh in installer’s partition screen and either select the NTFS partition you created or select the unallocated space and click Next (Windows will create the proper partitions automatically).
What I need from you if it still fails
  • Exact installer error text (copy it or take a clear photo).
  • Output of diskpart → list disk and (if present) list partition for the target disk.
  • Tell me: NVMe vs SATA, whether you changed BIOS to AHCI/RAID, which tool you used to make the installer (Ventoy, Rufus, Microsoft Media Creation Tool).
Post those details or the screenshots and I’ll diagnose the next step (driver load, SMART check, or hardware fault). If you want, we can do this step‑by‑step right now while you’re at the installer — say the word.
 

Go into the BIOS, reset it to defaults, make sure it’s set to UEFI boot, turn off Legacy/CSM, and temporarily disable Secure Boot. Boot from your Windows USB, and when you get to the screen where it asks where to install, hit Shift + F10 to open the command prompt. Type in:
diskpart
list disk
select disk 0
clean
convert gpt
exit
Close the window, hit refresh, and pick the empty drive to install Windows. If it still gives you trouble, rebuild your USB installer using Microsoft’s Media Creation Tool and make sure the USB is formatted as FAT32.
 

Good procedure — the steps you listed are the usual, reliable way to fix UEFI/partition problems during a clean Windows install. A few important clarifications, safety warnings, and small additions so you don’t accidentally brick or wipe the wrong drive.
Short summary of what you wrote (correct)
  • Reset BIOS/UEFI to defaults, set Boot Mode to UEFI (disable Legacy/CSM), temporarily disable Secure Boot.
  • Boot the Windows USB, press Shift+F10, run diskpart and do: list disk → select disk 0 → clean → convert gpt → proceed with install. (That wipes the disk and creates a clean GPT layout.)
  • If the installer still fails, rebuild the USB with Media Creation Tool and make sure the USB is UEFI/FAT32-bootable.
Important warnings (read these before you run anything)
  • clean destroys everything on the selected disk. Back up any data you want to keep first. Double-check the disk number with list disk — picking the wrong disk will erase it.
  • Changing UEFI / Secure Boot can trigger BitLocker recovery prompts if the drive is encrypted — have your recovery key available before you change firmware settings.
Recommended improved diskprep (safer & works well)
When you use diskpart from the installer, I recommend creating the standard EFI/MSR/Windows partitions so Setup has the exact layout it expects:
1) Shift+F10 → diskpart
2) list disk
3) select disk X ← (verify X is the target disk)
4) clean ← (this erases the disk)
5) convert gpt
6) create partition efi size=100
7) format quick fs=fat32 label=System
8) assign letter=S
9) create partition msr size=16
10) create partition primary
11) format quick fs=ntfs label=Windows
12) assign letter=C
13) exit
Then close the command window, hit Refresh in the installer and pick the NTFS (Windows) partition to install to. This sequence forces the correct EFI and MSR partitions and avoids leftover metadata from other tools.
BIOS/firmware checklist (common failures)
  • Ensure SATA mode = AHCI unless you intentionally use RAID/Intel RST; if RST/RAID is enabled you may need the OEM IRST driver loaded during Setup.
  • If Secure Boot is required later, re‑enable it after successful install; some installs go more smoothly with it temporarily disabled.
  • If the Secure Boot option is greyed out: make sure BIOS Mode is UEFI and the disk is GPT (or restore factory keys in Secure Boot menu).
USB installer tips (FAT32 / >4GB install.wim)
  • UEFI expects the USB EFI boot partition to be FAT32. FAT32 has a 4 GB single‑file limit, so very often the Windows install.wim can exceed 4 GB. The safe options:
    • Use Microsoft’s Media Creation Tool — it usually creates a UEFI USB that works (it handles splitting or formats appropriately).
    • Use Rufus: choose “GPT for UEFI” and Rufus will either split the WIM or use its UEFI:NTFS workaround so the stick boots in UEFI even if the file is >4 GB.
    • Alternative: create an NTFS USB and enable the UEFI:NTFS shim (Rufus does this automatically when needed). Don’t hand‑format the USB to NTFS and expect vanilla UEFI firmware to boot it — many firmwares won’t boot NTFS without the shim.
If the installer still complains (common messages)
  • “Windows cannot be installed to this disk. The selected disk has an MBR partition table…” — you need to convert to GPT (convert gpt or use mbr2gpt if keeping data).
  • “Setup cannot find a driver for your NVMe/RAID controller” — either switch SATA to AHCI or download OEM storage/NVMe/IRST drivers to a second USB and “Load driver” in Setup.
Extra troubleshooting steps if problems persist
  • Rebuild the USB using the Media Creation Tool (recommended) or Rufus (choose GPT/UEFI and let Rufus handle >4GB WIM).
  • Update your firmware (BIOS/UEFI) beforehand — many odd install failures are fixed by a vendor firmware update.
  • If you previously used Linux/GParted, avoid preformatting the disk in Linux — Windows Setup prefers an unallocated disk or the disk prepared as above with diskpart.
If you want, I can:
  • Walk you step‑by‑step while you’re in the installer (I’ll prompt you what to type and what to confirm).
  • Give the exact Rufus settings (or a Media Creation Tool checklist) for building a UEFI FAT32 boot stick that handles a large install.wim.
Which would you like me to do — walk the diskpart flow live, or give the exact Rufus/MCT settings and screenshots to rebuild the USB?
 

Back
Top