Renaming Virtual Drive in Mountain Duck Creates Duplicate Phantom Drive
Posted: 18 Sep 2025 22:23
Hi,
I want to report an issue I'm facing with XY and phantom virtual drives mounted with Mountain Duck.
Background
I used Mountain Duck to mount my Cryptomator, Google Drive and pCloud drives. The first thing I noticed is that in XY, the volume label for the drives are an alphanumeric string.
When you open it up from Mountain Duck, the normal Windows Explorer shows the human-friendly volume label defined in Mountain Duck. But when you open it in XY, it shows what appears to be machine-friendly names, even though I defined human-friendly labels in Mountain Duck. Example:
628ea44c-5f38-45c2-883f-7d7d8872c243
932a7afb-c2e1-4c2f-a660-cd36a8b4b058
9194f3c6-fc6f-4a13-b069-a80ad9602825
So I renamed them to a more human-friendly name to make it easier to browse and do work in.
Issue
After renaming a Mountain Duck virtual drive's volume label from its GUID (628ea44c-5f38-45c2-883f-7d7d8872c243) to "pCloud" using XY's rename function (F2), a phantom/ghost folder entry persists in the tree panel even after the drive was unmounted. The phantom shows outdated folder contents and cannot be deleted. The real mount (with GUID name) and the phantom "pCloud" both appear under C:\Users\john\Mountain Duck\.
Now I'm left with "two" pCloud drives - one human-friendly one properly named 'pCloud', but seems like a cached version because new folders/files aren't reflected in it, and the "active" GUID one that seems to be in sync with the real pCloud drive online.
What I tried
First I tried to delete the human-friendly pCloud drive, but when it started queuing up a ton of files to be deleted, I got concerned if I'm making a mistake and somehow the wires might get crossed, and I end up accidentally deleting the "real" pCloud files. So instead I tried the following ways:
1. Unchecked "Remember state of tree" in Configuration > Tree and List - No effect
2. Renamed all .dat files in %APPDATA%\XYplorer folder (action.dat, fvs.dat, ks.dat, lastini.dat, tag.dat) - No effect
3. Edited XYplorer.ini with Find & Replace to remove all "pCloud" references (found and removed 15 instances) - No effect, phantom still appears
4. Used script command ::text get("tree"); - Successfully showed tree data containing phantom entry
5. Attempted tree cleanup via ::$tree = get("tree"); $tree = replace($tree, "C:\Users\john\Mountain Duck\pCloud\|", ""); - Successfully displayed cleaned tree but couldn't save it
Tried to use these commands, but it didn't work:
::edittree - "not a valid script command"
::tree - "not a valid script command"
::treepath - "not a valid script command"
::drives - "not a valid script command"
::load "tree", [data] - Script file 'tree.xys' not found
::set "tree", [data] - "Not a valid variable name"
What I've noticed is the phantom "pCloud" entry appears in 15 different places within XYplorer.ini (LastTargetReal, MiniTreePaths, TreeSectionColors, mruBrowse sections, mruOpenedItems) but removing all references doesn't eliminate the phantom from the tree, which seems to suggest the tree data is cached elsewhere beyond the INI and DAT files?
I have no idea what to do going from here. Any help would be greatly appreciated.
Thank you.
I want to report an issue I'm facing with XY and phantom virtual drives mounted with Mountain Duck.
Background
I used Mountain Duck to mount my Cryptomator, Google Drive and pCloud drives. The first thing I noticed is that in XY, the volume label for the drives are an alphanumeric string.
When you open it up from Mountain Duck, the normal Windows Explorer shows the human-friendly volume label defined in Mountain Duck. But when you open it in XY, it shows what appears to be machine-friendly names, even though I defined human-friendly labels in Mountain Duck. Example:
628ea44c-5f38-45c2-883f-7d7d8872c243
932a7afb-c2e1-4c2f-a660-cd36a8b4b058
9194f3c6-fc6f-4a13-b069-a80ad9602825
So I renamed them to a more human-friendly name to make it easier to browse and do work in.
Issue
After renaming a Mountain Duck virtual drive's volume label from its GUID (628ea44c-5f38-45c2-883f-7d7d8872c243) to "pCloud" using XY's rename function (F2), a phantom/ghost folder entry persists in the tree panel even after the drive was unmounted. The phantom shows outdated folder contents and cannot be deleted. The real mount (with GUID name) and the phantom "pCloud" both appear under C:\Users\john\Mountain Duck\.
Now I'm left with "two" pCloud drives - one human-friendly one properly named 'pCloud', but seems like a cached version because new folders/files aren't reflected in it, and the "active" GUID one that seems to be in sync with the real pCloud drive online.
What I tried
First I tried to delete the human-friendly pCloud drive, but when it started queuing up a ton of files to be deleted, I got concerned if I'm making a mistake and somehow the wires might get crossed, and I end up accidentally deleting the "real" pCloud files. So instead I tried the following ways:
1. Unchecked "Remember state of tree" in Configuration > Tree and List - No effect
2. Renamed all .dat files in %APPDATA%\XYplorer folder (action.dat, fvs.dat, ks.dat, lastini.dat, tag.dat) - No effect
3. Edited XYplorer.ini with Find & Replace to remove all "pCloud" references (found and removed 15 instances) - No effect, phantom still appears
4. Used script command ::text get("tree"); - Successfully showed tree data containing phantom entry
5. Attempted tree cleanup via ::$tree = get("tree"); $tree = replace($tree, "C:\Users\john\Mountain Duck\pCloud\|", ""); - Successfully displayed cleaned tree but couldn't save it
Tried to use these commands, but it didn't work:
::edittree - "not a valid script command"
::tree - "not a valid script command"
::treepath - "not a valid script command"
::drives - "not a valid script command"
::load "tree", [data] - Script file 'tree.xys' not found
::set "tree", [data] - "Not a valid variable name"
What I've noticed is the phantom "pCloud" entry appears in 15 different places within XYplorer.ini (LastTargetReal, MiniTreePaths, TreeSectionColors, mruBrowse sections, mruOpenedItems) but removing all references doesn't eliminate the phantom from the tree, which seems to suggest the tree data is cached elsewhere beyond the INI and DAT files?
I have no idea what to do going from here. Any help would be greatly appreciated.
Thank you.