Known issues: V3.2.0 & V4.0.0 Beta

I wanted to address some known issues with the current build. One of which has a workaround, the other only affects people using the new launcher.

Issue #1: Older Intel HD graphics and Windows 10.

On some older Intel graphics cards, the Minecraft launcher will output an error that mentions updating graphics drivers, even with proper ones installed. This can also show up when using Microsoft provided drivers on some systems. Thankfully I have discovered a workaround for this issue at least on the two devices I tested with this issue.

The fix involves one of two things. If using a locally installed version of Java you will have to downgrade it to an older version. This of course comes with added security risk for your system. If locating by hand look for "Java SE Runtime Environment 8u51". It is available from the Oracle Java Archive here. This version was released before Windows 10, and therefor will think it is running under Windows 8. For some reason this makes the game run just fine, or as good as you can get on Intel HD graphics.

Official download links from Oracle's Java Archive:

Java 8 Update 51; Windows x64
Java 8 Update 51; Windows x86

Option #2: jPortable

Older versions of PortableApps.com's jPortable can be found on their SoureForge here. This has a little less security risk as the only program running on the system that will use it is MCPLA and the Minecraft launcher. Unless of course you use it with other Java apps and the PortableApps.com Platform.

Official download links from the PortableApps.com SourceForge:

jPortable 8 Update 51: Rev2; Windows x64
jPortable 8 Update 51; Windows x86

To install these older versions simply delete the "Java" and "Java64" folders in the CommonFiles folder. Then, install this older version in its place. If using the PortableApps.com Platform, it will try to update these to a newer version. I highly recommend using the latest version unless this workaround is required for increased security. If you end up needing these older versions frequently, keeping a copy of the installer around may come in handy.

Issue #2: Launcher fails to start after copying over a local install.

This problem is caused by using the latest version of the launcher seen here, and also using this function in MCPLA. The layout and configuration of files in the new launcher aren't compatible with the older version seen here. If you are still using the older launcher, then this function should work fine. If you are using the new one, you're better off saying No and starting with a fresh install, or copying over a few files as needed. In an upcoming update (sometime in the near future) I will add a warning message to this prompt.

If you have any questions about these two problems, please leave a comment below. Thanks!

Edit: Issue #1 cannot be corrected in a way that doesn't require this workaround, and is out of my control. Issue #2 is an issue caused by the conflict of launchers, and therefor also cannot be corrected by me. V4.0.0 Beta now displays a warning regarding this issue before the game asset copy menu appears.