Nativelog.txt:
Set run directory to ...\Minecraft
Native Launcher Version: 1665
Operating System: Windows 10 Enterprise
Application Hash: c9b11bc96b23ea3e08c45e9e04fa9d3d6ae47fe7
Application Data directory: C:\...\AppData\Roaming/.minecraft
Executable Path: MinecraftLauncher.exe
App Directory dir: ...\Minecraft
Start dir: C:/.../AppData/Roaming/.minecraft
Launcher dir: .../Minecraft/game
TmpDir dir: .../Minecraft/tmp
(Optional) Java Launcher hash:
Java Version: 1.8.0_51
x64: 1
LauncherConfiguration from: [http://launchermeta.mojang.com/mc/launcher.json]
Downloaded config
Native launcher is current
Native launcher is current
C:/.../AppData/Roaming/.minecraft/launcher_profiles.json doesn't exist, new user?
Using new launcher as a launcher.dll is on disk.
Launcher library is up to date with hash 6c87deea578c0d3d9206c0cd0f611c0ff45e7cec
Check to see if we can run the launcher
Native launcher is current
Starting launcher.dll with ...\Minecraft\runtime\jre-x64\1.8.0_51\bin\javaw.exe
Found SetDllDirectoryW in kernel32.dll!
Added ...\Minecraft\game to DLL search path
Running launcher!
Also found this blog, it's the same to me with the Junction Point: MCL-5569
I just did test it out myself on a Virtual Machine.
An installation on a normal setup windows 10 works fine and the launcher starts normally.
If there is a Junction Point in use for the users folder the Launcher is unable to start in foreground and stays as a zombie process in background.
Funily it still creates the .minecraft folder in %appdata% and uses resources off from my system.
Hope you can fix it. I wanna play Minecraft without being forced to push my Userfolder back to drive C: just for one game.
Linked issues
Comments 3
MCL-5436 --workDir solved the problem.
Minecraft Launcher now starts as a single process in foreground.
Thx for the help.
Does MCL-5294 or MCL-5436 describe your issue?