MCL-5528Can't use hard-linked .minecraft directory
ACTUAL LAUNCHER VERSION IS 2.0.760 - WEBSITE WONT LET ME ENTER IT.
I use a hard link (mklink /H) in my appdata folder to link my .minecraft folder to a different hard drive (as my primary drive has low space).
With the previous launcher, this was no issue and functioned fine, however my launcher has recently updated and now I receive the following:
Error details: The system cannot find the file specified
Filename on disk: .minecraft
Path: C:\Users[REDACTED]\AppData\Roaming\.minecraft
Exists: directory
Environment
Microsoft Windows 10
Created Issue:
Can't use hard-linked .minecraft directory
ACTUAL LAUNCHER VERSION IS 2.0.760 - WEBSITE WONT LET ME ENTER IT.
I use a hard link (mklink /H) in my appdata folder to link my .minecraft folder to a different hard drive (as my primary drive has low space).
With the previous launcher, this was no issue and functioned fine, however my launcher has recently updated and now I receive the following:
Error details: The system cannot find the file specified
Filename on disk: .minecraft
Path: C:\Users[REDACTED]\AppData\Roaming\.minecraft
Exists: directoryEnvironment
Microsoft Windows 10
- Unresolved
- Open
- Unconfirmed
- .minecraft directory file filesystem hardlink link
- 2.0.729 (Windows)
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
duplicates
relates to
Reading through issue MCL-5528 I applied the --workDir parameter to my Minecraft shortcut and it seemed to work as the original error went away:
The game directory is invalid or inaccessible.
Error details: The system cannot find the file specified
Filename on disk: .minecraft
Path: %USERPROFILE%\AppData\Roaming\.minecraft
Exists: directory
However, now I am receiving this error:
Unable to locate the Java runtime.
Error details: The system cannot find the file specified
Filename on disk: javaw.exe
Path: %USERPROFILE%\AppData\Roaming\.minecraft\runtime\jre-x64\1.8.0_25\bin\javaw.exe
Exists: file
(They don't actually display %USERPROFILE%, just making messages more succinct)
Is there a parameter for controlling the Java version that the Launcher uses?
The new launcher does not support appdata location change anymore. Use the --workDir argument instead.
See
MCL-5294.Thank you for your help, that appears to have resolved the issue.
I couldn't find that report when searching through already submitted reports, my apologies.