Windows changes boot drive letter

PNWACE · Apr 2, 2026

Hi All
Ongoing random UEFI problem I need help with. I have had to fully recover my Win11P mirrored boot disk after Windows appears to have changed drive letters causing a boot fail. EG, Windows volume C gets assigned D, data drive volume D gets assigned C, 2nd data volume drive gets assigned F and so on. And a recovery partition is assigned a new drive letter.
I have tried;
Auto Windows system boot repair - no luck
I have used diskpart to manually reassign volumes - no luck, reverts back to what Windows wants
I have run Bootrec commands - no luck
I have run rebuild BCD - no luck
I have removed all non essential hard drives, tried pulling one M.2 drive, restart and applied bootrec commands - no luck
I have swapped M.2 drives around thinking maybe a faulty M.2. Rebuilt the OS mirror in the BIOS - no luck
I tried looking at the UEFI boot volume and Windows system location, looked fine (may not have been can't really tell)
Tried various Linux boot recovery, - no luck.
Finally I did a full (BMR type) Lazesoft recovery and was able to recover a previous Windows 25H2 .7462 image, now works again.

Thinking back about the last good boot, I saw a new 25H2 update being applied on shutdown. It seems to be
related to an UEFI issue, because the system sort of boots, but then cannot find the Windows system files because the
drive letters were changed. Off line file explorer found Windows ok, just under a different drive letter.
Also, inserting and removing USB FD in Windows and even booting Ventoy live Linux does not cause the random problem
of Windows reassigning drive letters.

So if you have any insight as to what might of caused this and how to prevent it happening again, I would appreciate
some input.

Thanks

Try3 · Apr 2, 2026

PNWACE said:
Windows volume C gets assigned D, data drive volume D gets assigned C, 2nd data volume drive gets assigned F and so on

How did you boot?
Into a USB such as an installation USB?

Windows can assign different drive letters [I once had a system that labelled its OS drive F:\, it was a dual-boot system yet showed F:\ even though booted into F:\'s OS] but I've never heard of one changing the OS drive letter when booting normally. So I don't think I can help if that's what you are referring to.
[Added later - I have reread the thread and now think you are indeed reporting non-standard OS drive letters.]

Denis

PNWACE · Apr 2, 2026

No to an installation USB boot. But I did use the Lazesoft recovery BMR ISO to recover. I always separate the bootable C: disk from any data drives and I try and mirror the boot drives. So normal boot is from the 256GB MVMe assigned C drive(s) Thing is even with the other drives disconnected I could not correct (persistantly) the correct drive volumes I assigned with diskpart, which should have worked. Windows or something somewhere kept changing the drive letters. And most of the time it boots fine from the NVMe C drive. Just every now and then I get this drive letter reassignment. Below is what is normal;

Drive C:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 236.65 GB (254,100,066,304 bytes)
Free Space 151.70 GB (162,890,162,176 bytes)
Volume Name WIN11 256GB raid PCIe
Volume Serial Number 26D0C860

Drive D:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 5.46 TB (6,001,156,681,728 bytes)
Free Space 2.41 TB (2,651,672,735,744 bytes)
Volume Name 6TB_HGST_refurb
Volume Serial Number CC821872

Drive E:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 9.10 TB (10,000,828,186,624 bytes)
Free Space 6.12 TB (6,726,578,765,824 bytes)
Volume Name Exos-X10GB
Volume Serial Number 0DE458D0

Drive Z:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 1.86 TB (2,048,386,920,448 bytes)
Free Space 1.65 TB (1,809,012,830,208 bytes)
Volume Name 2TB Leven SSD
Volume Serial Number 9E0504AC

Thanks for looking

Scannerman · Apr 2, 2026

There is a possibility that you could have a rogue partition on another drive. BTW Nice choice of spinners. I recognize some of those. You may be able to correct this in MiniTool Partition Wizard. Another approach would be to get an HBA card. They're relatively inexpensive these days if you know where to look. MiniTool will show you hidden partitions that you won't otherwise see in Disk Manager. Anyway, just a suggestion.

*edit* I don't recommend mirroring the OS. That could be your issue right there.

FreeBooter · Apr 2, 2026

Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.

Code:

Sfc  /Scannow   /OFFBOOTDIR=C:\   /OFFWINDIR=C:\Windows

Please replace partition letter C: with Windows installed partition letter. When the computer boots into Windows Recovery Environment (WinRE) environment, the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assigned any other drive letter, usually D: drive letter is assign to Windows installed partition. The Bcdedit | find "osdevice" command can be used to find out the drive letter of the Windows installed partition, the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

PNWACE · Apr 2, 2026

Hi. Thanks but I don't think mirroring the boot OS is an issue, I have other computers I have mirrored the OS and never had an issue like this. Did it all the time with servers. You may be right about a rogue partition. There are 2 unexplained 100MB 'disk drives' in Partition magic that I did not create but are in the 2 mirrored NVMe SSD's that appear to be outside of the mirror that the OS sees. I don't know how to delete these as they show up as drives not partitions.

PNWACE · Apr 2, 2026

To : Freebooter. Hi. I'll run the SFC commands when I can, the problem does not exist right now, so I'm not sure what the result will be.
I ran bcdedit the OP shows the OSdevice is partition c:.
You may be right about the WinRE being the cause, this OS has been upgraded many times so I'm not sure what the original Windows partition (disk) would have been. I'm assuming C: but maybe not. How to tell?
Why would WinRE change the volume drive letters, where does it get that information from that would tell it to change what is in the UEFI boot parameters? Something is happening ahead of WinRE that would kick it to WinRE during the boot process. I can see a normal boot start to happen, then WinRE kicks in with errors, I just can't see how to fix it. Only fix so far is, thank fully, is Lazesoft BMR, choose all partitions and recover the entire disk.

Sub note; ran sfc /scannow online it did find a repaired errors.

zbook · Apr 2, 2026

If the computer

PNWACE said:
To : Freebooter. Hi. I'll run the SFC commands when I can, the problem does not exist right now, so I'm not sure what the result will be.
I ran bcdedit the OP shows the OSdevice is partition c:.
You may be right about the WinRE being the cause, this OS has been upgraded many times so I'm not sure what the original Windows partition (disk) would have been. I'm assuming C: but maybe not. How to tell?
Why would WinRE change the volume drive letters, where does it get that information from that would tell it to change what is in the UEFI boot parameters? Something is happening ahead of WinRE that would kick it to WinRE during the boot process. I can see a normal boot start to happen, then WinRE kicks in with errors, I just can't see how to fix it. Only fix so far is, thank fully, is Lazesoft BMR, choose all partitions and recover the entire disk.

Sub note; ran sfc /scannow online it did find a repaired errors.

These AI links may be useful:

Google Search

Code:

The Windows Recovery Environment (WinRE) changes drive letters because it operates as a separate,
lightweight operating system that does not load the standard Windows registry,
causing it to assign drive letters based on physical disk order rather than saved configuration.
This is a normal behavior where the system partition may appear as C: and recovery partitions may be assigned letters unexpectedly.

Why WinRE Shows Different Drive Letters

1. WinRE runs in its own mini‑OS

Windows Recovery Environment is basically a lightweight Windows PE system. It does not load your normal Windows registry, which is where your usual drive‑letter assignments are stored.
Because of that, WinRE has to assign letters on the fly, based on what it detects.

2. WinRE assigns letters in a different order

WinRE scans disks and partitions in a simple, hardware‑level order:

Disk 0 → Partition 1 → Partition 2 → etc.
Then Disk 1 → Partition 1 → Partition 2 → etc.

It assigns letters as it finds partitions. This often results in:

Partition	In Windows	In WinRE
System Reserved / EFI	Hidden	C:
Actual Windows OS	C:	D: or E:
Recovery partition	Hidden	No letter or random letter

So your real Windows installation might show up as D: or E: in WinRE, which confuses a lot of people.

Microsoft Copilot: Your AI companion

Microsoft Copilot is your companion to inform, entertain and inspire. Get advice, feedback and straightforward answers. Try Copilot now.

copilot.microsoft.com

Best practice:
For each reboot into Windows RE > check the assignments as needed

bcdedit
bcdedit | find "osdevice"

Scannerman · Apr 2, 2026

Personally I don't think it is advisable to mirror the drive with the OS on it. This is not to say that it can't be done as I've done it several times. I love trying things out :zany:

. Perhaps this is well and good on an Enterprise OS but it has been my experience time and time again that mirroring Win 7, 8, "shoulda been 9", and 10 results in stability issues. I've always had better success mirroring my data drives only, which is partly why I currently run three different kinds of RAID. Again, user preference prevails. I was merely trying to discern the cause of the issue. I think zbook has it pegged.

Celery · Apr 3, 2026

FreeBooter said:
When the computer boots into Windows Recovery Environment (WinRE) environment, the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assigned any other drive letter, usually D: drive letter is assign to Windows installed partition.

This primarily applies to Legacy BIOS/MBR systems. In WinRE, the System Reserved partition is often assigned the C: drive letter because it is located before the Windows partition.

On UEFI/GPT systems, the system partition is the EFI system partition, which typically does not receive a drive letter in WinRE.

In WinRE, the Windows partition can be assigned any drive letter, depending on the disk and partition layout.

Try3 · Apr 3, 2026

PNWACE said:
Why would WinRE change the volume drive letters, where does it get that information from

Why are you now referring to WinRE?
I thought the problem affected normal booting.
WinRE labels the drives in sequence as it discovers them - it's not that it gets the information from somewhere else.

Denis

Windows changes boot drive letter

Member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Member

Attachments

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

Why WinRE Shows Different Drive Letters​

1. WinRE runs in its own mini‑OS​

2. WinRE assigns letters in a different order​

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

Why WinRE Shows Different Drive Letters

1. WinRE runs in its own mini‑OS

2. WinRE assigns letters in a different order

My Computer

My Computer

My Computers

My Computer