Open stefanunz opened 6 years ago
My instinct would be try running "subst /d X:" with X being the unwanted drive letter, but I can't say from experience.
My instinct would be try running "subst /d X:" with X being the unwanted drive letter, but I can't say from experience.
I had this issue and tried using subst
but got an error about X:
being an invalid parameter. I also tried using diskpart
but the offending drive did not show up there either.
I ended up just switching the drive letter I was using so the work around is easy. Maybe ShadowSpawn was running during a recent windows update and that got things in a weird state?
When shadowspan fails the drive letter seems to be blocked (Error: device allready exists)
Is there a way to release / unmount that drive letter? Maybe by killing a task?