MC-144010Minecraft stays in background and don't start if Junction Point is used for C:\Users
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.
Environment
Windows 10 x64 Pro Build 1809
i9-9900k
RTX 2080
32 GB DDR4
Java 8 Update 201 x32/x64
Minecraft msi installer/legacy installer
Userfolder follows a Junction Point from C to another drive.
Linked Issues
MCL-5436
Created Issue:
Minecraft stays in background
Afterthe msi installer unpack the launcher, Minecraft stays in background with 2 processes, 1 with 0 cpu time and ram and one idling with 10% cpu time and 9 mb ram.
Shutting down the task and restart the launcher doesn't have an affect.
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:
https://bugs.mojang.com/browse/MCL-5569Is my Junction Point the reason for this problem?
Seems weird because the install folder for the game is in a root directory of my gaming ssd and only the worlds are supposed to be written into my user profile.
Would like to know, please try out the install with a junction point.
Environment
Windows 10 x64 Pro Build 1809
i9-9900k
RTX 2080
32 GB DDR4
Java 8 Update 201 x32/x64
Minecraft msi installer
Userfolder follows a Junction Point from C to another drive.
After the msi installer unpack the launcher, Minecraft stays in background with 2 processes, 1 with 0 cpu time and ram and one idling with 10% cpu time and 9 mb ram.
Shutting down the task and restart the launcher doesn't have an affect.
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:
https://bugs.mojang.com/browse/MCL-5569Is my Junction Point the reason for this problem?
Seems weird because the install folder for the game is in a root directory of my gaming ssd and only the worlds are supposed to be written into my user profile.
Would like to know, please try out the install with a junction point.
After the msi installer unpack the launcher, Minecraft stays in background with 2 processes, 1 with 0 cpu time and ram and one idling with 10% cpu time and 9 mb ram.
Shutting down the task and restart the launcher doesn't have an affect.
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:
https://bugs.mojang.com/browse/MCL-5569Is my Junction Point the reason for this problem?
Seems weird because the install folder for the game is in a root directory of my gaming ssd and only the worlds are supposed to be written into my user profile.
Would like to know, please try out the install with a junction point.After the msi installer unpack the launcher, Minecraft stays in background with 2 processes, 1 with 0 cpu time and ram and one idling with 10% cpu time and 9 mb ram.
Shutting down the task and restart the launcher doesn't have an affect.
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:
https://bugs.mojang.com/browse/MCL-5569Is my Junction Point the reason for this problem?
Seems weird because the install folder for the game is in a root directory of my gaming ssd and only the worlds are supposed to be written into my user profile.
I just did test it our myself on a Virtual Machine.
Minecraft Launcher is unable to
After the msi installer unpack the launcher, Minecraft stays in background with 2 processes, 1 with 0 cpu time and ram and one idling with 10% cpu time and 9 mb ram.
Shutting down the task and restart the launcher doesn't have an affect.
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:
https://bugs.mojang.com/browse/MCL-5569Is my Junction Point the reason for this problem?
Seems weird because the install folder for the game is in a root directory of my gaming ssd and only the worlds are supposed to be written into my user profile.
I just did test it our myself on a Virtual Machine.
Minecraft Launcher is unable to
After the msi installer unpack the launcher, Minecraft stays in background with 2 processes, 1 with 0 cpu time and ram and one idling with 10% cpu time and 9 mb ram.
Shutting down the task and restart the launcher doesn't have an affect.
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:
https://bugs.mojang.com/browse/MCL-5569Is my Junction Point the reason for this problem?
Seems weird because the install folder for the game is in a root directory of my gaming ssd and only the worlds are supposed to be written into my user profile.
I just did test it out myself on a Virtual Machine.
Minecraft Launcher is unable to start in foreground if the Users folder on C: is following a Junction Point.
An installation on a normal setup windows 10 works fine and starts the launcher normally.
After the msi installer unpack the launcher, Minecraft stays in background with 2 processes, 1 with 0 cpu time and ram and one idling with 10% cpu time and 9 mb ram.
Shutting down the task and restart the launcher doesn't have an affect.
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:
https://bugs.mojang.com/browse/MCL-5569Is my Junction Point the reason for this problem?
Seems weird because the install folder for the game is in a root directory of my gaming ssd and only the worlds are supposed to be written into my user profile.
I just did test it out myself on a Virtual Machine.
Minecraft Launcher is unable to start in foreground if the Users folder on C: is following a Junction Point.
An installation on a normal setup windows 10 works fine and starts the launcher normally.After the msi installer unpack the launcher, Minecraft stays in background with 2 processes, 1 with 0 cpu time and ram and one idling with 10% cpu time and 9 mb ram.
Shutting down the task and restart the launcher doesn't have an affect.
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:
https://bugs.mojang.com/browse/MCL-5569Is my Junction Point the reason for this problem?
Seems weird because the install folder for the game is in a root directory of my gaming ssd and only the worlds are supposed to be written into my user profile.
I just did test it out myself on a Virtual Machine.
An installation on a normal setup windows 10 works fine and starts the launcher normally.If there is a Junction Point in use for the users folder the Minecraft Launcher is unable to start in foreground.
But funnily it still creates the .minecraft folder in %appdata%
Minecraft stays in background and don't start if Junction Point is used for C:\Users
Windows 10 x64 Pro Build 1809
i9-9900k
RTX 2080
32 GB DDR4
Java 8 Update 201 x32/x64
Minecraft msi installer/legacy installer
Userfolder follows a Junction Point from C to another drive.
After the msi installer unpack the launcher, Minecraft stays in background with 2 processes, 1 with 0 cpu time and ram and one idling with 10% cpu time and 9 mb ram.
Shutting down the task and restart the launcher doesn't have an affect.
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:
https://bugs.mojang.com/browse/MCL-5569I
s my Junction Point the reason for this problem?
Seems weird because the install folder for the game is in a root directory of my gaming ssd and only the worlds are supposed to be written into my user profile.
I
just did test it out myself on a Virtual Machine.
An installation on a normal setup windows 10 works fine and starts the launcher normally.If there is a Junction Point in use for the users folder the Minecraft Launcher is unable to start in foreground.
But funnily it still creates the .minecraft folder in %appdata%
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:
https://bugs.mojang.com/browse/MCL-5569I 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.
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
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:
https://bugs.mojang.com/browse/MCL-5569I 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.
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-5569I 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.
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
duplicates
Does
MCL-5294orMCL-5436describe your issue?Also note that you might be able to use --workDir.
MCL-5436--workDir solved the problem.Minecraft Launcher now starts as a single process in foreground.
Thx for the help.