I recently added a new data drive to replace an old data drive. I proceeded to copy files from the old drive to the new drive, and then I swapped the drive letters so that the new data drive will have the same drive letter as the old drive. I do not have the old drive available to me anymore, only the new drive is connected.
Ever since then, I've noticed that I am unable to open a folder through explorer.exe in the command line. That is, if I run
it will launch a window perfectly fine. However if I run
it does not do anything. I see the process appear, but I do not see anything show up. The process seems to stay around for a bit, then closes.
I've tried searching across the web, but nothing seems to have been specific to this issue. I'm pretty sure it must have been me swapping the drive letter.
I've looked through the registry to see if there are any indication of any non-existant drive letter references, but I've only found information within VolumeInfoCache in Windows Search.
Resolved: (I will post an answer later due to inability to answer my question as a newbie).
I resolved the issue. Classic case of forgetting exactly what I did after swapping the drives.
In addition to swapping out the drives and assigning new drive letters. I also moved where some of the personal documentation libraries were pointed. Unfortunately, I didn't do it correctly for one of the folders (Personal folder, to be specific). It was still pointed at a path that no longer was valid.
I ended up using ProcMon to monitor the process and saw that explorer kept on failing to read something within the registry in ShellFolder. Looking through ShellFolder I saw that I missed one of the changes and changed it to the appropriate path. This seemed to have fixed the issue and explorer launches folders correctly now.
Thanks for your help Lee, Karan, and luchosrock.