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.
Werner
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.