Launcher is unable to unpack natives because they are in use by another process

Update; I closed it and it still showed the message, but this time twice. I will reboot and only launch the new launcher and post results here after.

Upon reboot, it launched fine, but this is an incredibly annoying bug.

This is because of how Windows operates (and every developer HATES this feature), whenever it has files in use (for reading) you cannot write to them. We have to unpack the natives before we start the game and thus if a game is already running this causes an issue.

We'll look into unpacking it to a unique folder so multiple instances can run next to eachother.

If the natives are already unpacked, because the game is already running, why not just use the existing files rather than attempting to unpack them again?

Thanks Grum, it's nice to see some kind staff here. @Torabi hmm- I understand the basics of what you are saying. But from what i can infer I believe you are saying that The game is already running, (the launcher was, I closed the game before than tried to launch it again) But i am certain it was not. @Torabi could you explain a bit more thoroughly? I am on a scale of one to ten in knowledge of natives 0.0001 . Thanks

That may be because of ghost javaw.exe processes - you've closed the game, but invisible processes are running and still accessing the game files. To avoid having to restart open Task Manager (using Ctrl+Alt+Del) and kill javaw.exe when this problem occurs.

What if the processes refuses to stop? Every time my Minecraft crashes this happens, I try and try to kill javaw.exe and it will not die. I just can not understand why this happens.

i have same problem. Someone please help!!!