[MCL-3983] nativelog.txt appears on Desktop

Moderator Note

This issue seems to appear when a desktop shortcut to the launcher is already set on the desktop, before it is updated to 1.6.44. Deleting and re-creating the shortcut seems to correct this issue.

I wanted to play Minecraft today, but when I started the launcher, something unusual happened. I saw that a file called "nativelog.txt" had appeared on my desktop. I don't know if other people have encountered this issue yet.

Linked issues

is duplicated by 7

MC-97924 nativelog.txt is created on desktop Resolved

MC-120591 minecraft is stuck and creates a nativelog when starting Resolved

MCL-3990 Nativelog And Launcher bug Resolved

MCL-3993 Opening a Minecraft Launcher creates a file "nativelog.txt" Resolved

MCL-4151 Nativelog shows up on your desktop Resolved

2 more links

Attachments

probleem opstarten minecraft screenshot.doc

Comments 17

CubeTheThird 2015-09-12T14:52:12Z

If you use the exe launcher, it will generate files such as nativelog and a few others in the same location as where you put the launcher.

marcono1234 2015-09-12T15:21:54Z

You should rather use a shortcut to the .exe file

migrated 2016-01-18T13:05:05Z

It seems that the .msi installer does not set the working directory of the desktop shortcut correctly; on Windows 10, viewing its properties gives a blank 'Start In' field.
Changing this to the Minecraft installation directory solves the problem.
Also, I uninstalled and reinstalled the launcher, and the same thing happened.

CubeTheThird 2016-01-18T15:17:44Z

@@unknown, the .msi launcher does not create a desktop shortcut (only one in the start menu). Any shortcut you have would be pre-existing.

migrated 2016-01-19T04:08:30Z

@CubeTheThird, then what did? There was no pre-existing desktop shortcut.

7 more comments

CubeTheThird 2016-01-30T03:46:43Z

Hmm it seems I was mistaken. I wasn't aware the installer gave the option to create a shortcut on the desktop. It shouldn't cause this issue though.

galaxy_2alex 2017-02-13T13:14:25Z

Is this still a concern in the current Minecraft Launcher version 2.0.805 / 2.0.806? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.

Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. It will be reopened it as soon as the requested information has been delivered.

migrated 2017-02-13T13:26:28Z

This issue is still present.

galaxy_2alex 2017-02-13T13:29:58Z

With the new launcher as well?

migrated 2017-04-23T10:35:44Z

Yes the problem still exists with the new launcher. I just installed Minecraft on a fresh Windows 10, and the issue appeared.
The problem is the Desktop shortcut which is being generated by the Installer. It is caused by the "Start in" property filled which is empty.

To solve this issue for clean installs you need to make sure the Desktop shortcut (generated by the Installer) has the "Start in" property filled with the install directory. "C:\Program Files (x86)\Minecraft" for example. This solves the issue.

I was using version 2.0.847.

nathanv 2017-09-09T18:08:02Z

I tried it but it doesn't works. Not the nativelog only but also 3 maps named 'tmp' , 'runtime' and 'game' comed to the desktop. At the screenshot in the attachment you see the maps.

[media]

violine1101 2017-09-10T17:13:20Z

@unknown, simply move the launcher and the four folders into a seperate folder and create a link to the launcher executable on the desktop.

nathanv 2017-09-11T19:56:03Z

Did it, but didn't work

violine1101 2017-09-14T18:18:33Z

This is not a support forum, please use the Community Support link below to get further help (IRC would be best I guess).

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki

galaxy_2alex 2018-04-26T12:19:41Z

Is this still a concern in the current Minecraft Launcher version 2.0.1003 / 2.0.1004 / 1.6.84-j? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.

migrated 2018-04-27T08:02:51Z

The issue still exists with the current .msi installer as of 2018-04-27. It isn't relevant to the Java launcher.

petr.mrazek 2018-08-31T09:03:49Z

Found where this is coming from – we are blindly initializing the log before we know where things should go in the launcher bootstrap.