Lost internal F drive when using docking station

I have Model USB3-SATA-U3 docking. Today when I plug in a HD that was named “G” my computer lost my internal HD named “F”. I rebooted and the F drive was back, until I again plugged in the G drive to the docking station. The USB 3.0 port is on a 2 port PCI Card

I also have a StarTech USB 3.0 docking station plugged in (Drive “N”). I wanted to copy from one docking station (G to N) to the other. Is there a conflict with StarTech and Plugable?

Hi Norman,

Thanks for posting. I’ll be glad to assist.

I think a good place to start will be to determine a bit more about the drives in use - what they are named, vs. what their assigned drive letter is. There’s a difference between what a drive is named, and what letter Windows assigns it.

You should be able to right-click on the drive letter, and select “Rename”. This will allow you to rename it whatever you’d like (“Norman’s 1TB Drive”, etc), though this is independent of what drive letter Windows will give the device.

Windows should be able to run many drives simultaneously without having additional drives cause existing drives to go offline, so tough to say what’s causing that. If both have been assigned the same drive letter, then only one drive will be visible. So it might be worth trying to manually set the drive letters of the various drivers.

Changing the actual drive letter requires a more involved process, which is covered step-by-step here:

You probably won’t want to change the drive letters of internal drives, since programs that are installed on those drives will need the drive letter to remain constant. But manually changing the drive letters of the external drives will be a good starting point.

If that doesn’t help matters, please email support@plugable.com and we’ll have a look at some log files to see if we can determine any other potential causes of this behavior.


I think I have found the problem. I had a old copy of EaseUS Partition Manager. I have upgraded to current version and I have not had the problem since. Thus I am declaring this problem solved. Thanks for your input.

Hi Norman,

Interesting - surprised the EaseUS would affect things that way, but glad to hear you got it sorted out and appreciate you following up to post the solution you found.

All the best,