Solved Drive Letter is Already Taken, but I Can't See it or Change It

[KaiserSoze]

After a Reboot, while using Easeus Partition Master, my D drive disappeared. I assigned the D letter to it in Disk Management and when I rebooted again, the D letter was taken. I was forced to assign letter Z until I figure out what to do.

The device D letter is assigned to now, does not exist in either Registry of Disk manager (check screenshots)

The only place where I can see the culprit occupying D is in My Computer. I checked Deamon Tools or similar programs and neither of them uses such a drive. Can you please help me sorting this one out? I can't switch back to D: with any of the three possible methods (Disk Management, Regedit or diskpart command in CMD). This letter simply deosn't exist for the computer.

P.S.: I have 2 more partitions but the are containing Linux and they are not touched for quite a while. It can't be them.

 

[Berton]

Below is my section of the Registry, I show the A: floppy drive but there is no A: drive in the computer although it can be enabled in the BIOS. Most newer BIOSes don't list the A: and B: options although Windows reserves those 2 drive letters for floppy drives. A USB floppy drive will show differently, take an available letter.

Z: is usually assigned to the first Networked drive such as a NAS/Network Attached Storage drive, mine is although it's not showing on the list.

I do have several drives listed but not all show in Disk Management or Windows Explorer as they are memory card slots/card reader in the computer and won't show until a card is inserted and some are External USB drives.

 

[KaiserSoze]

Below is my section of the Registry, I show the A: floppy drive but there is no A: drive in the computer although it can be enabled in the BIOS. Most newer BIOSes don't list the A: and B: options although Windows reserves those 2 drive letters for floppy drives. A USB floppy drive will show differently, take an available letter.

Z: is usually assigned to the first Networked drive such as a NAS/Network Attached Storage drive, mine is although it's not showing on the list.

I do have several drives listed but not all show in Disk Management or Windows Explorer as they are memory card slots/card reader in the computer and won't show until a card is inserted and some are External USB drives.

Thank you for sharing that, but my issue has nothing to do with it. Z was just a random choice in a moment of irritation. The core of the problem is that letter D is occupied by some kind of virtual device (which is not a network drive or a USB drive), that does not appear in registry, thus it cannot be renamed.

 

[dsperber]

I don't understand how your drive got to look the way it looks. There are FOUR primary partitions defined, along with a LOGICAL partition (Z). The logical Z partition is correctly shown in bright blue, surrounded by a dark green outline which indicates the "extended partition" containing your one or more logical partitions inside of it.

But logical partitions exist inside of what's called an "extended partition", which is actually one of the four maximum primary partitions allowed on a BASIC drive which has been re-purposed into a "extended partition" (to support one or more logical partitions inside of it). Since it actually is a primary partition to begin with, re-purposing it to be an "extended partition" leaves only THREE remaining primary paritions possible.

That means a BASIC drive that has one (or more) logical partitions defined as you do MUST have an "extended partition" defined to hold those one (or more) logical partitions, as you do. And that also means a BASIC drive that has one (or more) logical partitions defined cannot have more than THREE primary partitions on it, since the required extended partition (which is one of the FOUR maximum primary partitions allowed) has been defined.

So your screenshot appears to show an impossible situation, with FOUR defined primary partitions along with an "extended partition". You mention Linux present, and it's likely this is somehow related to the mystery. But Windows DISKMGMT is definitely seeing a total of FIVE primary partitions (one of which is simply the re-purposed "extended partition" holding your logical partition).

This would seem to be impossible, and is no doubt causing the inconsistent presentations of your drive.

I would like to see a screenshot of what Partition Wizard thinks of your drive. Please install (if you don't already have it) and post a screenshot.

 

[jumanji]

Hi KaiserSoze,

Open Device Manager, and find out which program's Virtual CDROM drive is listed under DVD/CDROM drives.

Run that program, get into its Settings, and disable creation of Virtual CDROM drive.

That should release your drive letter D.

[In the screenshots here, it is my Elby CloneDrive (Slysoft ) and I have set it to run one drive always. My "Computer" always shows it as BDROM Drive ( X: ) apart from the two physical optical drives Y: and Z:]

 

[KaiserSoze]

Unfortunately this drive is not listed in my Device Manager. I only have the physical one available.

 

[jumanji]

OK, I was expecting this but wanted to make sure that it was not one of your Virtual drive creating programs. You told you have many apart from Daemon Tools.

Now get going with the drive cleanup schedule.

Download v 0.8.1 of the drivecleanup.zip from Drive Tools for Windows.

Unzip it to a folder, say drivecleanup.

You will have two folders Win32 and x64 each containing DriveCleanup.exe for 32 bit and 64 bit respectively.

Remove all USB storage devices from your system (except your Keyboard and mouse) and reboot.

Right click on the DriveCleanup.exe and run as administrator. (Use the DriveCleanup.exe file appropriate for your bit version of Windows.).

After the clean up act, reboot and check whether your system still shows the Virtual D drive.

The drive cleanup will erase all non-existent drives from Windows memory alongwith the drive letters and the associated registry entries and now you will be starting with a new slate. As you plug-in your USB drives those will be installed afresh. Your phantom drive holding drive letter D should be gone.

Let us know if it did indeed.

EDIT: This is end of the day post. I shall be retiring now and will check only after another 10hours. So do not keep waiting for me. In case my suggestion does not work, it will be for other sxperts to indulge in. My quiver is empty.

 

[KaiserSoze]

OK, I was expecting this but wanted to make sure that it was not one of your Virtual drive creating programs. You told you have many apart from Daemon Tools.

Now get going with the drive cleanup schedule.

Download v 0.8.1 of the drivecleanup.zip from Drive Tools for Windows.

Unzip it to a folder, say drivecleanup.

You will have two folders Win32 and x64 each containing DriveCleanup.exe for 32 bit and 64 bit respectively.

Remove all USB storage devices from your system (except your Keyboard and mouse) and reboot.

Right click on the DriveCleanup.exe and run as administrator. (Use the DriveCleanup.exe file appropriate for your bit version of Windows.).

After the clean up act, reboot and check whether your system still shows the Virtual D drive.

The drive cleanup will erase all non-existent drives from Windows memory alongwith the drive letters and the associated registry entries and now you will be starting with a new slate. As you plug-in your USB drives those will be installed afresh. Your phantom drive holding drive letter D should be gone.

Let us know if it did indeed.

EDIT: This is end of the day post. I shall be retiring now and will check only after another 10hours. So do not keep waiting for me. In case my suggestion does not work, it will be for other sxperts to indulge in. My quiver is empty.

The tool cleaned up about a dozen of drives, but that sucker is stubbornly appearing several seconds after each reboot. I mean, the physical CD ROM is there and the faulty D appears a few seconds after that.

MiniTool Partition Wizard Free is also clueless about this drive and it doesn't exist for it.

Thank you for the tips, though.

[Resolved]: I ran a resizing of the problematic patrition, moving some bits here and there and the letter was freed. It got even better since I managed to take some free Gigs, moving them to the C drive.

 

[jumanji]

OK, your problem got resolved by manipulating the problem partition and removing some data from it. So it could make one believe that there was something in it that was creating a virtual CDROM drive that was starting with Windows. That would also explain why that VCD drive was not a non-present leftover that could have been eliminated by the drive cleanup.

Without examining the contents in that partition and knowing what exactly you removed from that partition, there is no clue of what it is.

As dsperber noted in his post#4, four primary partitions and one extended is indeed surprising and you should investigate it. Notably the two primary partitions do not have a drive letter in Windows nor do they show NTFS. Perhaps those two are in a different format and Windows is not counting those. His desire to see the drive with Partition Wizard is relevant and could have thrown more light perhaps.

 

[KaiserSoze]

OK, your problem got resolved by manipulating the problem partition and removing some data from it. So it could make one believe that there was something in it that was creating a virtual CDROM drive that was starting with Windows. That would also explain why that VCD drive was not a non-present leftover that could have been eliminated by the drive cleanup.

Without examining the contents in that partition and knowing what exactly you removed from that partition, there is no clue of what it is.

As dsperber noted in his post#4, four primary partitions and one extended is indeed surprising and you should investigate it. Notably the two primary partitions do not have a drive letter in Windows nor do they show NTFS. Perhaps those two are in a different format and Windows is not counting those.

Those two are used by my Ubuntu (swap and OS) and they have always been fine. My Windows did not have any conflict with them. My best guess is that there must have been some bytes left out as unallocated and resizing has moved them to the good partitions.