Technical Anshu
Tutorials Blog
🔤 Drive Letter Trap

Windows Drive Letter Changes Inside WinPE Find the Real Windows Partition

Every offline repair command needs the drive letter of the Windows partition - but inside WinPE that letter is almost never C. This is the two-minute check that decides whether your repair works or silently repairs the wrong thing.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute read
🎥 Full video - see the drive letter check done live inside the WinPE CMD Toolkit before the repair starts

Here is the most common beginner failure in offline repair: boot WinPE, open the command prompt, type a repair command aimed at C: - and repair the recovery partition, the EFI partition, or nothing at all. WinPE builds its own letter map every time it starts, and X: is always its own RAM disk. Your Windows partition is present and healthy, just wearing a different letter for this session. Confirm the letter first and every command after it becomes reliable.

DISKPART - list volume (example machine)
Volume ### Ltr Label Fs Type Size Status Info ---------- --- ------------ ----- ----------- ------- --------- -------- Volume 0 F DVD-ROM 0 B No Media Volume 1 D Windows NTFS Partition 465 GB Healthy Volume 2 E Data NTFS Partition 931 GB Healthy Volume 3 System FAT32 Partition 100 MB Healthy System Volume 4 C Recovery NTFS Partition 650 MB Healthy Hidden
A real trap: on this machine C: is the small Recovery partition and the actual Windows lives on D:. Letters and labels are examples - always verify on your own machine.
1

Open Diskpart and List Every Volume

From the WinPE command prompt, run diskpart and then list volume. You get one row per partition and removable drive: letter, label, file system, size and status.

  1. Ignore X: completely - that is the WinPE RAM disk your tools are running from
  2. The USB you booted from also takes a letter here, which pushes the hard disk letters further down
  3. Note the size of each NTFS partition - your Windows partition is usually the one whose size matches what you know from the PC, often 100 GB or more
2

Use the Label and File System as Clues

Three quick clues separate the partitions before you test anything:

  1. FAT32, around 100 to 300 MB, often labelled System - that is the EFI boot partition. Repair commands never target it, but bcdboot needs its letter later
  2. NTFS, a few hundred MB, labelled Recovery - the Windows recovery partition. It sometimes grabs C: inside WinPE, which is exactly the trap in the screenshot above
  3. NTFS, large, labelled Windows or with no label - your main candidate for the real Windows partition
3

Prove It with the Dir Test

Clues are not proof. The 10-second test that never lies is listing the candidate letter:

  1. Exit diskpart with exit and run dir D:\ - replace D: with your candidate letter
  2. The real Windows partition shows the folders Windows, Users, Program Files and Program Files (x86) together at the top level
  3. Double-confirm with dir D:\Windows\System32 - hundreds of system files should scroll past
  4. If the letter shows only a few folders or an error, test the next candidate letter the same way
4

Write the Letter Down and Use It Everywhere

Once confirmed, that letter is the target for the whole session: chkdsk D: /f, sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows, dism /image:D:\ ... and bcdboot D:\Windows ... all take it.

  1. If the EFI partition has no letter and you need it for boot repair, go back into diskpart, select volume 3 (its number from your list) and assign letter=Z
  2. Do not remove or change letters on anything else - assignments inside WinPE last only for this session and do not alter the installed Windows
5

When the Windows Partition Does Not Appear at All

Sometimes list volume shows the disk but no large NTFS partition - or no disk at all. That is a different problem from a changed letter:

  1. BitLocker: an encrypted volume shows up but its contents stay locked and unreadable. Unlock it first with manage-bde -unlock D: -recoverypassword followed by your 48-digit recovery key, then repair
  2. Missing storage driver: on newer laptops with Intel VMD or RAID mode, WinPE may not see the NVMe disk until the storage driver is loaded - many custom WinPE builds include a driver loader tool for exactly this
  3. Dead disk: if list disk in diskpart shows nothing at all, check cables and BIOS - a disk the firmware cannot see is a hardware case, not a repair case
🔴 Never format or "fix" a partition whose letter you guessed. Every year, recovery partitions get formatted and data drives get chkdsk-repaired by people who assumed C: was Windows. The dir test takes ten seconds - it is the cheapest insurance in all of PC repair.

🎥 See the Letter Check Done Live in the Video

Watch how the real Windows partition is identified inside the WinPE CMD Toolkit before a single repair command is run.

▶️ Watch Full Video
❓ Frequently Asked Questions

Do letters inside WinPE change my real Windows letters?

No. WinPE's letter map exists only in its own RAM session. When Windows boots normally afterwards, its partition is C: again, exactly as before. Assigning a letter to the EFI partition inside WinPE is also temporary and harmless.

Why does WinPE give itself X:?

WinPE loads its whole system into a RAM disk so the USB can even be removed mid-session. X: is reserved for that RAM disk by design, which is why X: is never your hard disk and never a repair target.

Diskpart shows my drive but dir says the device is not ready - why?

That usually means the volume is BitLocker-locked, the file system is badly damaged, or the storage driver is missing so the disk is only half-visible. Unlock BitLocker if it applies, load the storage driver if your WinPE offers one, and treat a still-invisible disk as a hardware problem.

This guide is based on the Technical Anshu video on fixing corrupted Windows with a custom WinPE CMD Toolkit • Stuck on a step - ask in the video comments and the community will help 🙏