I am not able launch JNLP applications using "Java Web Start"? [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.

This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.

Closed 7 months ago .

Up until recently, I was able to launch/open JNLP files in Firefox using Java web start. Don't know what happened all of a sudden JNLP files stopped launching, a splash screen appears saying Java Starting. and then nothing happens. Even the Java Console in the browser and javacpl.cpl applet doesn't open. Tried all possibilities: removed all older version and installed the latest JRE (java version "1.6.0_17"), still it doesn't work. Done some googling for this problem, people suggested to start javaws.exe with -viewer option but same behavior (a splash screen appears saying "Java Starting. " and then disappears) The problem is that I don't know any place (logs etc.) to look for to see what is causing the problem. I am using WinXP SP3, and some of the screenshots below shows further info about my system. I can provide any other detail if required but please help me solve this problem.

786 10 10 silver badges 26 26 bronze badges asked Dec 16, 2009 at 6:18 1,827 3 3 gold badges 21 21 silver badges 35 35 bronze badges I see this problem too -- really annoying. Commented Jul 10, 2013 at 17:33

17 Answers 17

i had the same problem here. go to your Java Control Panel and Settings. Uncheck 'Keep temporary files on my computer'. Apply changes and try again your .jnlp

Java Control Panel - Keep temporary files on my computer

Note: Tested on different machines; Windows Server 2012, Windows Server 2008 and Windows 7 64bit. Java Version: 1.7++ since my jnlp app is built on 1.7

Please let me know your feedback too. :D

3,572 2 2 gold badges 37 37 silver badges 37 37 bronze badges answered May 20, 2014 at 7:28 474 1 1 gold badge 6 6 silver badges 9 9 bronze badges

Magically working also under Sonoma 14.6.1, Java(TM) SE Runtime Environment (build 18.0.2.1+1-1), Java HotSpot(TM) 64-Bit Server VM (build 18.0.2.1+1-1, mixed mode, sharing)

Commented Aug 26 at 12:37

Java web start should be enabled.
Check if javaws (Java web start is enabled for your system), Use below command in console to open java control panel.

javaws -viewer 

Image for your refrence

answered Aug 25, 2020 at 7:30 Ravindra Yadav Ravindra Yadav 171 1 1 silver badge 6 6 bronze badges

This helped me, as all other options like associate file system modification in control panel, java security enable site lists are added etc, one thing pending for me was this!

Commented Mar 22, 2023 at 8:37

I know this is an older question but this past week I started to get a similar problem, so I leave here some notes regarding the solution that fits me.

This happened only in some Windows machines using even the last JRE to date (1.8.0_45).

The Java Web Start started to load but nothing happened and none of the previous solution attempts worked.

After some digging i've found this thread, which gives the same setup and a great explanation.

So, in conclusion, it was a memory problem in x86 JRE and since our JNLP's max heap was defined as 1024MB, we changed to 780MB as suggested and it was fixed.

However, if you need more than 780MB, can always try launching in a x64 JRE version.

answered Jun 13, 2015 at 9:38 121 3 3 silver badges 7 7 bronze badges

Great, that works. In our case, -Xms in the JNPL file must be equal to the -Xmx set in _JAVA_OPTIONS.

Commented Dec 6, 2016 at 15:07

If javacpl does not open and gives you Could not find the main class:, it could be that Java is confused because of changes in deployment.properties (can be found in C:\Users\\AppData\LocalLow\Sun\Java\Deployment on Win7 ). Delete that file and everything's fine.

This bug seems to be 6 years old, cf. An app should be able to ignore properties that have become obsolete over time, shouldn't it?

1 1 1 silver badge answered Mar 25, 2011 at 15:46 31 1 1 bronze badge

Although this question is bit old, the issue was caused by corrupted ClearType registry setting and resolved by fixing it, as described in this ClearType, install4j and case of Java bug post.