Fix: Java Platform SE binary has stopped working

Some users have been reporting receiving the “Java(TM) Platform SE binary has stopped working” error when running various Java-based applications. Typically, this error message is accompanied by general unresponsive periods that can be stopped by clicking the Close program button.

Note: The issue is not exclusive to Windows 10 and is frequently reported on Windows 8. There is no apparent link between the build number and this type of error.

Most of the time, the issue is occurring due to a video card driver conflict with the Java environment. However, this behavior will not happen with every Java-based application – only a handful of programs are reported by users to crash with the “Java(TM) Platform SE binary has stopped working” error. Minecraft is by far the most frequently reported application that crashes with this particular error message.

If you’re currently struggling with the same issue, this article will provide you with some troubleshooting strategies. Below you have a couple of methods that other users in a similar situation have used to resolve the “Java(TM) Platform SE binary has stopped working” error. Please follow the troubleshooting guides below in order until you encounter a repair strategy that takes care of the error. Let’s begin!

Method 1: Update GPU card drivers

The most common scenario in which the “Java(TM) Platform SE binary has stopped working” error occurs is when there’s a conflict between the Java Environment and your graphics card driver.

Since most video driver issues that we’re causing this issue have been fixed by GPU manufacturers, you can probably take care of the issue by simply updating your dedicated GPU drivers to the latest version.

Each major GPU manufacturer has some kind of software that will automatically detect your GPU model and install the latest version of the required graphics card driver. Here are the tools capable of doing this according to your GPU manufacturer:

Once your graphics drivers have been updated, reboot your computer and see if the issue has been resolved at the next startup. If you are still prevented from opening certain Java-based applications by the  “Java(TM) Platform SE binary has stopped working” error, move down to Method 2.

Method 2: Reinstall all Java SE Related applications

If the first method wasn’t effective in resolving the issue, let’s see if we’ll have better luck by reinstalling the whole Java environment. Some users have reported that the issue was automatically resolved one they uninstalled their current Java environment and then installed the latest Java version from the official download page.

Here’s a quick guide through the whole thing:

  1. Press Windows key + R to open up a Run box. Then, type “appwiz.cpl” and hit Enter to open the Programs and Features window.
  2. Scroll down through the application list and uninstall every Java entry that you can find by right-clicking on each entry and choosing Uninstall.
  3. Once every entry has been uninstalled, reboot your computer.
  4. At the next startup, visit this link (here) and click on the Free Java Download button to re-install the Java Environment. You’ll be prompted to restart again at the end of this process.
  5. Once your PC boots back again, see if you are able to open Java-based applications without the “Java(TM) Platform SE binary has stopped working” error. If you’re still seeing the same error message, move down to the final method.

Method 3: Running the application after a Clean Boot

Several users have managed to get their Java-based programs to start while performing a Clean boot. A clean boot will eliminate most software and driver conflicts since it starts the system with a minimal set of drivers and startup programs.

If you find that the “Java(TM) Platform SE binary has stopped working” error doesn’t occur after you do a Clean boot, it’s clear that some of the startup programs and services that were excluded by the Clean boot procedure are to blame for it. Once you confirm this, you should systematically uninstall each suspected software until you eliminate the conflict.

To make things clearer, here’s a quick guide on how to perform a clean boot and identify the startup program that is causing the issue:

  1. Press Windows key + R to open up a Run box. Next, type “msconfig” and hit Enter to open the System Configuration menu.
  2. Inside the System Configuration window, navigate to the Services tab and click the Disable all button. Then, hit Apply to save the changes.
  3. Next, move to the Startup tab and click on the Open Task Manager.
  4. In the Startup tab of Task Manager, select each startup item that has the Status set to Enabled and click the Disable button below.
  5. Once every unnecessary startup process has been disabled, close Task Manager and restart your computer.
  6. At the next startup, see if the applications open without the “Java(TM) Platform SE binary has stopped working” error. If everything is working normally now, continue with the next steps below.
  7. Systematically re-enable each startup item and service by reverse-engineering the steps above until the issue resurfaces. Once you identify your culprit, uninstall the application and restart the machine again.
  8. Use steps 1 to 3 to return to the Services and Startup tabs and re-enable the rest of the services that were previously disabled.

Method 4: Modify the Windows Error Reporting File

Whenever a Windows application crashes, a WER file is created, which contains valuable information that can help you analyze why the crash happened. While software vendors have to sign up for Microsoft’s Winqual service to access the crash data from their customers, admins can access it by opening the .wer files, which are simple text files that Windows stores at different locations. In some cases, the problem description will help you to understand why an application crashed. However, it is often only the developer who will really understand the contents of the .wer file. But, you can’t go wrong having a look at these files before you decide whether you want to enable or disable Windows Error Reporting (if you are worried that confidential data will be sent to third parties). Furthermore, you can also send the files to the support service of your software or hardware vendor in the hope that they can figure out what went wrong.

In Windows 7, Windows Error Reporting files can be stored in a subfolder somewhere deep down in the ProgramData or User directory. The name of the subfolder is simply WER, and the file extension is .wer. You can use Windows Search or another desktop search tool to locate them all. However, the information in these .wer files can also be accessed through the Windows Action Center (Control Panel\System and Security\Action Center).

The Java(TM) Platform SE binary has stopped working error can be rectified by tweaking these Windows Error Reporting files and for doing so proceed to the steps indexed below to get rid of this issue:

  1. Locate the Windows Event Reporting log it is usually located in the following location.
  2. Right-click on the “.WER” file and select “Open With”. After that, open it with “Wordpad” or “Notepad”.
    Opening file with Notepad
  3. Navigate to the end of the file to AppPath. It displays the location of the Java.exe file that caused the error. (For example – D:\myapp\subfolder\ocx\jre\bin).
  4. Navigate to this location and isolate the file that was listed to be the cause of the error.
  5. Right-click the java.exe file, and select Properties to open the properties for this application.
  6. Click the “Compatibility tab”, and select the “Change Settings for all Users” option if it is available.
  7. Clear the “Compatibility mode” checkboxes and select the “Run this program in compatibility mode for:” option and from the dropdown menu choose another version of Windows, preferably older than your current one.
    Running the program in compatibility mode
  8. Click OK to close the JAVA Properties window.
  9. Log out from Web Interface or from the services site and log-on again.
  10. Try to launch the application that you were trying to launch beforehand and check to see if it works correctly.

Method 5: Launch Sessions with Java Web Start

If the solution stated above does not resolve the issue, users can work around the error by launching sessions with a system-installed version of Java Web Start rather than the Blackboard Collaborate Launcher application. Instructions to do so are listed below, but users are also encouraged to contact Collaborate support for further assistance.

Windows 7 / 8 Users:

  1. Press the “Windows” + “R” to open the Run prompt and paste the following command inside it, press “Enter” to execute it, and open the associate file.
    control /name Microsoft.DefaultPrograms /page pageFileAssoc
    Opening Run Prompt

Note: This will start the Associate a file type or protocol with a program.

  1. Select the entry for .collab from the list and click the Change program button.
  2. The “Open with” window will appear and from there you will see a listing for Java(TM) Web Start Launcher in this window, select it and click “OK”.
  3. Afterward, proceed to step number 7 and if there is no listing for Java(TM) Web Start Launcher in this window, proceed to step number 3.
  4. Click the “More Apps” link and scroll to the bottom of the list and click on the “Look for another app on this PC”.
  5. Navigate to the Java directory on your computer and remember that for most systems, this will be one of the following:
C:\Program Files\Java\jre1.8.0_111\bin
C:\Program Files (x86)\Java\jre1.8.0_111\bin
*Note that the number following "jre" above will vary depending on your installed version of Java.
  1. Now, select the “.exe” file and click on the “Open” button
  2. Lastly, launch a Collaborate Web Conferencing session and test the application sharing feature and hopefully, the issue would’ve been resolved by now.

Windows 10 Users:

  1. Close any Collaborate session or recording windows.
  2. Press “Windows” + “R” to open the Run prompt.
  3. Type in “Control Panel” and press “Enter” to launch the classic control panel interface.
    Accessing the Classic Control Panel interface
  4. Inside the Windows Control Panel, click on the “Program and Features” option.
  5. Check the list of programs to ensure that “Java” is already installed on the system. If it isn’t installed, please download and install Java from before proceeding.
  6. Download a new Collaborate meeting or recording file but don’t launch the file yet.
  7. Locate the meeting or recording “.COLLAB” file in your Downloads
  8. Right-click on the file and choose “Open with” then click “Choose another app”.
  9. If you see Java (TM) Web Start Launcher in this list (you may need to click More apps to expand the list), select it and check the box that says “Always use this app to open .collab files” then click the OK
  10. If Java (TM) Web Start Launcher is not in the list, check the box that says Always use this app to open .collab files then click Look for another app on this PC.
  11. Navigate to the following location:
C:\program files\java\jreXXX\bin

XXX represents a number that will vary based on the version of Java installed on the computer, for example: jre1.8.0_221.

  1. Select the file named “.exe” and click Open.
  2. Going forward, all “.COLLAB” files will open using Java Web Start rather than the Blackboard Collaborate Launcher
  3. Launch a Collaborate session or recording to test the application sharing functionality.

Method 6: Run System In Safe Mode

Some users have reported that they were able to fix this issue after re-starting their system in Safe Mode. They reported that the problem was caused by a monitor process that was corrupting installation files while the installation process was executed. The problem is in the monitoring tool called “Logitech Process Monitor” (lvprcsrv.exe). Please make sure that you are not running this or any other processes monitoring tool. Hence, running in safe mode will disable all of the processes that could interfere in the running of Java. Follow the steps stated below to run your system in a Safe Mode:

  1. Click the Start button and select the Power icon.
  2. Hold down the Shift key and click Restart.
  3. A menu will appear. Select Troubleshoot > Advanced Options > Startup Settings.
    Startup Settings in Advanced Options
  4. Click the Restart button and your computer will reboot, presenting you with the menu shown below.
  5. Now, press 4 to select Enable Safe Mode (or 5 to select Enable Safe Mode with Networking if you need to use the Internet).
  6. Your computer will then boot in safe mode.

To start in safe mode (Windows 7 and earlier):

  1. Turn on or restart your While it’s booting up, hold down the F8 key before the Windows logo appears.
  2. A menu will appear. You can then release the F8 key. Use the arrow keys to highlight Safe Mode(or Safe Mode with Networking if you need to use the Internet to solve your problem), then press Enter.
    Selecting the “Safe Mode With Networking” option
  3. Your computer will then boot in safe mode.

To start in safe mode on a Mac:

  1. Turn on or restart your computer. While it’s booting up, hold down the Shift key before the Apple logo appears. Once the logo appears, you can release the Shift key.
  2. Your computer will then boot in safe mode.

Method 7: Re-Install Minecraft

Most of the people fixed this issue by re-installing Minecraft on their respective systems because an incompatible version or any glitch of Minecraft can cause this error.

  1. Press “Windows” + “R” to open the Run prompt.
  2. Type in “appwiz.cpl” and press “Enter” to open the App Manager Window.
    Type appwiz.cpl and Press Enter to Open Installed Programs List
  3. Inside the app manager, scroll down and right-click on the “Minecraft” application.
  4. Select “Uninstall” from the list and then follow the on-screen instructions to remove the application from your computer.
    Uninstalling Using Application Manager
  5. Repeat the process above for any instance of the application.
  6. Afterward, to install the game, navigate here to download the game client. You can download the game client even if you don’t own the game, but you will only be able to play the demo mode. After downloading the client, double-click the icon to run it.
  7. Follow the on-screen instructions to fully install this application on your computer.

Please note that a Minecraft purchase is tied to your account (email address) and not a device. As such, you can download and install Minecraft: Java Edition on as many computers as you want. To log in, use your email address and password (or username and password if you have an older account). Please make sure that you are connected to the internet, as the game will automatically download additional files the first time. After you have installed Minecraft and stored your account credentials, it’s possible to play with or without an internet connection.

Method 8: Configure Environmental Variables

Many operating systems use environment variables to pass configuration information to applications. As properties in the Java platform, environment variables are key/value pairs, where both the key and the value are strings. After the latest Windows update, a glitch might arise that provokes the Java(TM) Platform SE binary has stopped working issue. Therefore, in this step, we will be resetting the Environmental Variables.

  1. Press “Windows” + “R” to open the Run prompt.
  2. Type in “Control Panel” and press “Enter” to open the classical control panel interface.
  3. In the control panel, click on the “View By:” option and select the “Large Icons” option from the list.
    Viewing Control Panel using Large Icons
  4. Click on the “System” option and select the “Advanced System Settings” from the list of available options in the next window.
  5. Select the “Advanced” tab from the top and then click on “Environment Variables” on the bottom of the screen.
    Click on Environmental Variables
  6. Next, click the “New” button under “System variables” option to open the next window.
  7. Enter “_JAVA_OPTIONS” in the Variable name text box.
  8. Type “-Xmx256M” in the Variable value box.
  9. Save your changes and click on “OK” to exit the system variables window.
  10. After doing so, click on the “OK” button again to exit out of this window entirely.
  11. Now that the process is completed, check to see if the error message still persists.

Method 9: Remove Older Java Versions (Using Script)

Keeping old versions of Java on your system presents a serious security risk. Uninstalling older versions of Java from your system ensures that Java applications will run with the latest security and performance improvements on your system. Copy the code present below and save it as Remove_old_java_versions.ps1 at the {PackageShare}\Scripts folder.

Note: This package checks for both 32-bit and 64-bit installed versions of Java, and silently uninstalls any old versions leaving behind only the newest and as this is just a simple Powershell script, it can also be run on its own. Keep one thing in mind that the script is a little slow as enumerating the WMI class Win32_Product takes a long time.

#This script is used to remove any old Java versions, and leave only the newest.

#Original author: mmcpherson

#Version 1.0 - created 2015-04-24

#Version 1.1 - updated 2015-05-20

#            - Now also detects and removes old Java non-update base versions (i.e. Java versions without Update #)

#            - Now also removes Java 6 and below, plus added ability to manually change this behaviour.

#            - Added uninstall default behaviour to never reboot (now uses msiexec.exe for uninstall)

#Version 1.2 - updated 2015-07-28

#            - Bug fixes: null array and op_addition errors.

# IMPORTANT NOTE: If you would like Java versions 6 and below to remain, please edit the next line and replace $true with $false

$UninstallJava6andBelow = $true

#Declare version arrays

$32bitJava = @()

$64bitJava = @()

$32bitVersions = @()

$64bitVersions = @()
#Perform WMI query to find installed Java Updates

if ($UninstallJava6andBelow) {

    $32bitJava += Get-WmiObject -Class Win32_Product | Where-Object {

        $_.Name -match "(?i)Java(\(TM\))*\s\d+(\sUpdate\s\d+)*$"


    #Also find Java version 5, but handled slightly different as CPU bit is only distinguishable by the GUID

    $32bitJava += Get-WmiObject -Class Win32_Product | Where-Object {

        ($_.Name -match "(?i)J2SE\sRuntime\sEnvironment\s\d[.]\d(\sUpdate\s\d+)*$") -and ($_.IdentifyingNumber -match "^\{32")


} else {

    $32bitJava += Get-WmiObject -Class Win32_Product | Where-Object {

        $_.Name -match "(?i)Java((\(TM\) 7)|(\s\d+))(\sUpdate\s\d+)*$"


#Perform WMI query to find installed Java Updates (64-bit)

if ($UninstallJava6andBelow) {

    $64bitJava += Get-WmiObject -Class Win32_Product | Where-Object {

        $_.Name -match "(?i)Java(\(TM\))*\s\d+(\sUpdate\s\d+)*\s[(]64-bit[)]$"


    #Also find Java version 5, but handled slightly different as CPU bit is only distinguishable by the GUID

    $64bitJava += Get-WmiObject -Class Win32_Product | Where-Object {

        ($_.Name -match "(?i)J2SE\sRuntime\sEnvironment\s\d[.]\d(\sUpdate\s\d+)*$") -and ($_.IdentifyingNumber -match "^\{64")


} else {

    $64bitJava += Get-WmiObject -Class Win32_Product | Where-Object {

        $_.Name -match "(?i)Java((\(TM\) 7)|(\s\d+))(\sUpdate\s\d+)*\s[(]64-bit[)]$"


#Enumerate and populate array of versions

Foreach ($app in $32bitJava) {

    if ($app -ne $null) { $32bitVersions += $app.Version }


#Enumerate and populate array of versions

Foreach ($app in $64bitJava) {

    if ($app -ne $null) { $64bitVersions += $app.Version }


#Create an array that is sorted correctly by the actual Version (as a System.Version object) rather than by value.

$sorted32bitVersions = $32bitVersions | %{ New-Object System.Version ($_) } | sort

$sorted64bitVersions = $64bitVersions | %{ New-Object System.Version ($_) } | sort

#If a single result is returned, convert the result into a single value array so we don't run in to trouble calling .GetUpperBound later

if($sorted32bitVersions -isnot [system.array]) { $sorted32bitVersions = @($sorted32bitVersions)}

if($sorted64bitVersions -isnot [system.array]) { $sorted64bitVersions = @($sorted64bitVersions)}

#Grab the value of the newest version from the array, first converting

$newest32bitVersion = $sorted32bitVersions[$sorted32bitVersions.GetUpperBound(0)]

$newest64bitVersion = $sorted64bitVersions[$sorted64bitVersions.GetUpperBound(0)]

Foreach ($app in $32bitJava) {

    if ($app -ne $null)


        # Remove all versions of Java, where the version does not match the newest version.

        if (($app.Version -ne $newest32bitVersion) -and ($newest32bitVersion -ne $null)) {

           $appGUID = $app.Properties["IdentifyingNumber"].Value.ToString()

           Start-Process -FilePath "msiexec.exe" -ArgumentList "/qn /norestart /x $($appGUID)" -Wait -Passthru

           #write-host "Uninstalling 32-bit version: " $app




Foreach ($app in $64bitJava) {

    if ($app -ne $null)


        # Remove all versions of Java, where the version does not match the newest version.

        if (($app.Version -ne $newest64bitVersion) -and ($newest64bitVersion -ne $null)) {

        $appGUID = $app.Properties["IdentifyingNumber"].Value.ToString()

           Start-Process -FilePath "msiexec.exe" -ArgumentList "/qn /norestart /x $($appGUID)" -Wait -Passthru

           #write-host "Uninstalling 64-bit version: " $app




Method 10: Clear Java Cache

One of the things that can cause this error is the Java cache that stays on your computer even after you removed and reinstalled the software. The first thing we would recommend would be to delete these temporary files via your Java Control Panel which you can get to by following the steps stated below:

Find the Java Control Panel – Java 7 Update 40 (7u40) and later versions:

Starting with Java 7 Update 40, you can find the Java Control Panel through the Windows Start menu.

  1. Launch the Windows Start menu
  2. Click on Programs(All Apps on Windows 10)
  3. Find the Java program listing
  4. Click Configure Java to launch the Java Control Panel

Find the Java Control Panel – Versions below 7u40:

Windows 10:

  1. Press “Windows” + “R” to open the Run prompt and type in “Control Panel”.
  2. In the Windows Control Panel, click on Programs.
  3. Click on the Java icon to open the Java Control Panel.

Windows 8:

  1. Press “Windows” + “R” to open the Run prompt and type in “Control Panel”.
  2. Press Windows logo key + W to open the Search charm to search settings
    Drag the Mouse pointer to the bottom-right corner of the screen, then click on the Search
  3. In the search box enter Java Control Panel
  4. Click on the Java icon to open the Java Control Panel.

Windows 7, Vista:

  1. Press Windows + R to open the Run prompt.
  2. Type in “Control Panel” in the run prompt and press “Enter” to launch it.
    Accessing the Classic Control Panel interface
  3. In the Control Panel, search for “Java Control Panel”
  4. Launch the control panel from the list of searches.

An alternate method of launching the Java Control Panel:

  1. Press “Windows” + “R” to open the Run prompt.
    Opening Run Prompt
  2. Type in the following lines in the Run prompt depending upon your system.
    Windows 32-bit OS: c:\Program Files\Java\jre7\bin\javacpl.exe
    Windows 64-bit OS: c:\Program Files (x86)\Java\jre7\bin\javacpl.exe
  3. This should launch the Java Control Panel.

Clear Cache:

Now that you have launched the Java Control Panel, we will be moving on towards actually clearing the Cache. For that:

  1. Click on the “General” tab and then select the “Settings” option under the “Temporary Internet Files” heading.
  2. Click on the “Delete Files” button in the next window that appears.
  3. Check all the options in the next window to make sure that all the cache gets cleared.
    Checking all Options
  4. Click on “OK” to start the clearing process.

Bill Wilson

Bill is a certified Microsoft Professional providing assistance to over 500 remotely connected employees and managing Windows 2008 to 2016 servers.