HDD Drive letters swapped!

On my main Windows10 system have two HDDs assigned
the letters R & S.

On my other instance of Windows10 on the same
motherboard' I have two other HDDs (bitlockered)
coincidently self assigned the drive letters R &
S.

Now the main Windows10 has swapped the two HDD
drive letters. How can this happen over two OSs,
and how do I prevent it in future?

Peter Jason wrote:
On my main Windows10 system have two HDDs assigned
the letters R & S.

On my other instance of Windows10 on the same
motherboard' I have two other HDDs (bitlockered)
coincidently self assigned the drive letters R &
S.

Now the main Windows10 has swapped the two HDD
drive letters. How can this happen over two OSs,
and how do I prevent it in future?


Isn't automatic assignment overridden by
manual assignment ? If you assigned a
drive letter to one of them, that might
be forcing the labeling in this case.

Paul

On Wed, 30 May 2018 19:53:08 -0400, Paul
wrote:

Peter Jason wrote:
On my main Windows10 system have two HDDs assigned
the letters R & S.

On my other instance of Windows10 on the same
motherboard' I have two other HDDs (bitlockered)
coincidently self assigned the drive letters R &
S.

Now the main Windows10 has swapped the two HDD
drive letters. How can this happen over two OSs,
and how do I prevent it in future?


Isn't automatic assignment overridden by
manual assignment ? If you assigned a
drive letter to one of them, that might
be forcing the labeling in this case.

Paul

Thanks, I guess then the solution is to assign
some remote letter such as X and Z

On Wed, 30 May 2018 20:08:56 -0400, Wolf K
wrote:

On 2018-05-30 17:56, Peter Jason wrote:
On my main Windows10 system have two HDDs assigned
the letters R & S.

On my other instance of Windows10 on the same
motherboard' I have two other HDDs (bitlockered)
coincidently self assigned the drive letters R &
S.

Now the main Windows10 has swapped the two HDD
drive letters. How can this happen over two OSs,
and how do I prevent it in future?



This may help:

http://multibooters.com/articles/win...e-letters.html

Thanks, it's all been working fine for months, but
now this happens. I'm going to reassign the drive
letters of the drives on this main OS yo X & Z and
se if this will fix it.

Peter Jason wrote:
On Wed, 30 May 2018 20:08:56 -0400, Wolf K
wrote:

On 2018-05-30 17:56, Peter Jason wrote:
On my main Windows10 system have two HDDs assigned
the letters R & S.

On my other instance of Windows10 on the same
motherboard' I have two other HDDs (bitlockered)
coincidently self assigned the drive letters R &
S.

Now the main Windows10 has swapped the two HDD
drive letters. How can this happen over two OSs,
and how do I prevent it in future?


This may help:

http://multibooters.com/articles/win...e-letters.html

Thanks, it's all been working fine for months, but
now this happens. I'm going to reassign the drive
letters of the drives on this main OS yo X & Z and
se if this will fix it.

Every *OS* maintains letters in its Registry files.

Two OSes can quite easily have different assignments.

As near as I can tell, when a given OS is booted, you
can manually assign drive letters (like R: and S: ).
If the user has never assigned drive letters, drive
letters will be automatically allocated in hardware
order. If you move two SATA drives between ports,
that changes their "position" on that particular
"hardware bus", so an automatic allocation could change.

But, when the second OS boots, it doesn't know anything
about the clever plan you were using in the first OS.
Thus, the process starts over again.

This is why, if you boot a Kaspersky offline scanning disc,
it quite frequently grabs the registry section from the
wrong OS and the drive letters you see in Kaspersky
then resemble that OS. And if you really wanted to
scan the other OS C: drive, maybe it ends up being
E: or something.

In addition, there can be conflicts between network
mounts and USB drives. That's why this program
exists.

http://www.uwe-sieber.de/usbdlm_e.html

It's all quite complicated. The end result is, you
shouldn't become "too attached" to your lettering
scheme, as there are always going to be little
surprises. Perpetually.

Paul

On Wed, 30 May 2018 21:20:49 -0400, Paul
wrote:

Peter Jason wrote:
On Wed, 30 May 2018 20:08:56 -0400, Wolf K
wrote:

On 2018-05-30 17:56, Peter Jason wrote:
On my main Windows10 system have two HDDs assigned
the letters R & S.

On my other instance of Windows10 on the same
motherboard' I have two other HDDs (bitlockered)
coincidently self assigned the drive letters R &
S.

Now the main Windows10 has swapped the two HDD
drive letters. How can this happen over two OSs,
and how do I prevent it in future?


This may help:

http://multibooters.com/articles/win...e-letters.html

Thanks, it's all been working fine for months, but
now this happens. I'm going to reassign the drive
letters of the drives on this main OS yo X & Z and
se if this will fix it.

Every *OS* maintains letters in its Registry files.

Two OSes can quite easily have different assignments.

As near as I can tell, when a given OS is booted, you
can manually assign drive letters (like R: and S: ).
If the user has never assigned drive letters, drive
letters will be automatically allocated in hardware
order. If you move two SATA drives between ports,
that changes their "position" on that particular
"hardware bus", so an automatic allocation could change.

But, when the second OS boots, it doesn't know anything
about the clever plan you were using in the first OS.
Thus, the process starts over again.

This is why, if you boot a Kaspersky offline scanning disc,
it quite frequently grabs the registry section from the
wrong OS and the drive letters you see in Kaspersky
then resemble that OS. And if you really wanted to
scan the other OS C: drive, maybe it ends up being
E: or something.

In addition, there can be conflicts between network
mounts and USB drives. That's why this program
exists.

http://www.uwe-sieber.de/usbdlm_e.html

It's all quite complicated. The end result is, you
shouldn't become "too attached" to your lettering
scheme, as there are always going to be little
surprises. Perpetually.

Paul

Another point. I had forgotten to turn off the
dock containing the two bitlockered HDDs before I
switched over to the main OS. Maybe this was the
cause? I'm changing the main OS drives to X & Z
just in case.