New
#20
This week I upgraded my original 750 GB HDD's (2) to two 1 TB Samsung SSD's on an HP i7-2600, WIN 10 Pro x64 machine. Cloning worked fine, everything operational with no problems. Disk Mgmt shows everything as it should be. However, when I went into Windows Explorer to reorganize my working files a "mysterious" Local Disk (F) has appeared. My PC also shows Drive 'F'. When I click on it I get Location Not Available, etc. When I right click to view properties Windows Explorer shuts down - NOTHING.
While exploring this forum I found Administrator Brink had helped someone remove Drive 'F' in May 2019. I have tried the recommended solutions, Diskpart, etc but Drive 'F' does not show this so the solution cannot be applied. SOOOOOO, HELP. Thx.
Hello @finwiz00, and welcome to Ten Forums.
Please go ahead and post a screenshot showing your full Disk Management layout to see if anything may stand out.
How to Upload and Post Screenshots and Files at Ten Forums
Could this be a mounted virtual drive by chance? If you right click on the "F" drive, do you see an "Eject" option?
OPTION ONE
To Remove Drive Letter in Disk Management
OPTION TWO
To Remove Drive Letter in Command Prompt using Diskpart
OPTION THREE
To Remove Drive Letter in Command Prompt using Mountvol
OPTION FOUR
To Remove Drive Letter in PowerShell
The above commands may work temporarily or permanent.
What determines whether the command result is or is not permanent?
What information is available on the usefulness of the how these commands differ?
A drive letter was assigned to the EFI partition using diskpart assign letter=W
Chkdsk was ran.
The drive letter was removed using option two.
This worked but only temporarily.
The newly assigned drive letter later returned.
In the thread option three was just suggested.
Does each option alter the registry in a way that is different from the other?
If all 4 command methods are available what information is available about when would one work better than the other?
https://docs.microsoft.com/en-us/win...mands/diskpart
https://docs.microsoft.com/en-us/win...mands/mountvol
https://docs.microsoft.com/en-us/pre...ectedfrom=MSDN
https://docs.microsoft.com/en-us/win...ath-to-a-drive
https://docs.microsoft.com/en-us/win...isk-management
This is the link with the assigned drive letter:
Macrium Image Failure - Error Code 6
It appears that the drive letter removal commands may have different impacts on the registry?
This is another link where the command results differed (temporary vs permanent):
Unwanted drive letter for 2nd EFI partition: How to get rid of it?
Something is happening during the reboot?
Hi,
Despite the long list of available tools, none seems to work for me to remove a letter U:. The set-up here is with two computers named SingleXeon and DoubleXeon. The first is the "working" PC and the latter is attached via a wireless network. The drive-letter U: is assigned to one drive in the DualXeon. I fail to remove the U: following the various methods presented.
Most methods only show the drives of the local computer. DiskPart explicitly says it considers SingleXeon. I found no way to tell it to consider the DualXeon. The MountVol answered "No mount point".
Could I have misunderstood how to proceed in the suggested methods? If not, then does anyone have a suggestion how to remove the drive-letter from a drive of another PC attached with WiFi to the network?
I no longer remember how I was able to assign a drive letter to that networked PC. It might have given a clue.
Regards,
Ch
I have attached a screen-shot from the Windows Explorer as a pdf image to this post.
tenwindows.pdf