While using an older version of the launcher I first did let it create the .minecraft folder in the Roaming directory then I moved it to the root directory of my D: Drive that is an 1TB HDD off of my 240GB SSD. After that I launched CMD with administrator rights and used "cd %appdata%" to enter the Roaming directory. There I used "mklink /D .minecraft D:\.minecraft" to create the symbolic link. And everything worked and I could move the .minecraft folder off of my SSD that way. But yesterday when I lauched the Laucher it showed me the update screen but when it was done with it it simply refused to start. Manually starting the launcher after that that had the same result so I tried reinstalling java different downloads of the Launcher present on minecraft.net. But nothing worked except removing the symbolic link but that should only be a temporary workaround, cause it is very important to me to have minecraft on my HDD not my SSD which right know I am unable to do.
Linked issues
duplicates 1
Comments 4
This also happens even if you change the work directory of the launcher with the start-up arguments --workDir to a different directory.
See MCL-5294.
I have the same problem as described above.
Laucher updated itself and it doesn't work anymore…
It just exits instantly with code 0 without showing any dialog messages.
To reproduce, run cmd.exe as an administrator.
Go to %appdata% with: cd %appdata%
Use: mklink /D .minecraft "D:\.minecraft"
Optionally create folder on that path (mkdir?).
Make fresh install of launcher… and it won't work.
Please fix it, because I am unable to play. :C