MCL-9119Volume Mount Points do not work in 2.x launcher
Accidentally started the launcher through shortcut in the main menu.
It went on update rage and present me with an unsorted list of my profiles with a flashing, like an exalted idiot, advert.
Well, advert wasn't quite the biggest problem. The biggest problem was that it thoroughly destroyed every profile I had saved. Every attempt to start the game ended up with failure and investigation had shown that each profile I've tried to start had its custom profile folder set to empty string.
Every attempt to correct this misbehavior ended in the same result - empty string set as custom profile directory, no matter how exactly I choose it - copy-paste the full path or use dialog to select it.
Note that parent of MC profiles' base directory is a volume mount point.
If you are attempting to resolve it by hands instead of using OS API functions, you will end in the void between disks.
Created Issue:
Native launcher reset custom profile directory.
Accidentally started the launcher through shortcut in the main menu.
It went on update rage and present me with an unsorted list of my profiles with a flashing, like an exalted idiot, advert.
Well, advert wasn't quite the biggest problem. The biggest problem was that it thoroughly destroyed every profile I had saved. Every attempt to start the game ended up with failure and investigation had shown that each profile I've tried to start had its custom profile folder set to empty string.
Every attempt to correct this misbehavior ended in the same result - empty string set as custom profile directory, no matter how exactly I choose it - copy-paste the full path or use dialog to select it.
Accidentally started the launcher through shortcut in the main menu.
It went on update rage and present me with an unsorted list of my profiles with a flashing, like an exalted idiot, advert.
Well, advert wasn't quite the biggest problem. The biggest problem was that it thoroughly destroyed every profile I had saved. Every attempt to start the game ended up with failure and investigation had shown that each profile I've tried to start had its custom profile folder set to empty string.
Every attempt to correct this misbehavior ended in the same result - empty string set as custom profile directory, no matter how exactly I choose it - copy-paste the full path or use dialog to select it.Note that parent of MC profiles' base directory is a volume mount point.
If you are attempting to resolve it by hands instead of using OS API functions, you will end in the void between disks.
Legacy: Native launcher reset custom profile directory.
Legacy: Native launcher reset custom profile directory.Updating to 2.x launcher using volume mount points corrupts profiles
Updating to 2.x launcher using volumemountpointscorrupts profilesVolume Mount Points do not work in 2.x launcher
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Any news? I'd like to play the game I purchased.
What do you mean by "legacy"? Did you release a third version of your launcher already?
I may have misunderstood your ticket - did you accidentally open the old launcher, and this action deleted all the other profiles? If that is not the case, please explain what versions of the launcher were involved in the problem.
Please also confirm for us that this is still an issue with the latest version of the launcher. The old legacy one (1.6.x) is no longer supported.
You misunderstood a clearly mentioned launcher version?
I accidentally let the 1.6 launcher upgrade. Which led to a loss of paths in all profile configurations and inability to set paths back to their location. Every time I try to fix the profile to point to its directory, clicking "Ok" saves empty path. Each time.
Had to restore 1.6 launcher from backup to actually be able to run the game.
Alright, sorry about that. Looks like the problem is actually that the new launcher does not recognise volume mount points as valid profiles, which is potentially intended behavior. Changed the ticket accordingly.
You're kidding?
It's not the application role to determine the underlying hardware structure of a given path. Unless you are writing a file manager, use given path literal.
Could you give us the paths that were not working for you?
The path to all profiles is C:\Games\Minecraft\<profileName> C:\Games is a reparse point \\?\Volume{6833c424-2223-11e4-b07d-806e6f6e6963}\Games mountvol \\?\Volume{6833c423-2223-11e4-b07d-806e6f6e6963}\ C:\dev\sdc1 \\?\Volume{80006d80-c2bb-4297-93c1-2f6d1a2a8acb}\ C:\ C:\dev\sda1\ \\?\Volume{6833c424-2223-11e4-b07d-806e6f6e6963}\ C:\dev\sdd1 \\?\Volume{9d412aba-0e54-4628-9c6b-b84fb18d062a}\ C:\dev\sdb1 \\?\Volume{51810762-adac-11e4-9801-902b3437d8e4}\ W:\ \\?\Volume{152b5e11-3180-11e4-9bb8-806e6f6e6963}\ R:\ P.S. I would really appreciate, if your bug tracker would stop mangling the messages.