Accepted answer

specify the latest available java vm in your eclipse.ini. i.e.:

  1. make sure they are on separate lines
  2. anything after the "vmargs" is taken to be vm arguments

(more info)

or alternatively add the java bin folder to your windows path before the "windows32" folder, because otherwise eclipse uses "javaw.exe" in the win32 folder instead of the jdk one.


recently timo kinnunen has pinpointed the problem

edit eclipse.ini find the line:


and change it to

--launcher.appendvmargs:-vm <path_to_java>/jdk1.8.0/jre/bin/server/jvm.dll

this causes the jvm to be launched in the same process as eclipse.exe rather than as a child process and avoids the intricacies of host processes with appusermodelids.

and it works !!!


i think it's important to mention that at least for me it was important to add the path to the vm in the eclipse.ini with forward slashes, even though i'm working with windows (7, that is). eclipse didn't start when i used backslashes.


the solutions offered here on stackoverflow so far, don't have an easy fix for running multiple eclipses while each having their own application id, and making grouping of icons work as expected. the answer here does provide a reference to the underlying property.

here's a quick howto:

  1. do the -vm setting as plenty of people here have mentioned
  2. run the eclipse app
  3. right click on the running taskbar icon, pin this program to taskbar
  4. navigate to %appdata%\microsoft\internet explorer\quick launch\user pinned\taskbar
  5. copy the newly created shortcut to another location. it will be named eclipse, eclipse (2), or eclipse (3) and so on
  6. right click on the running taskbar icon, unpin this program from taskbar
  7. use the shortcut properties dialog to copy all individual fields (target + parameters, workdir, icon, anything else) to the new shortcut
  8. rename the new shortcut
  9. drag the new shortcut to the windows taskbar
  10. done

here's an extended howto, helpful if you want icon grouping separated per individual eclipse instance (if you have multiple instances running):

  1. find out what your startup plugin is, for example org.eclipse.epp.package.java_2.0.1.20130919-0803. open the plugin.xml file of that folder.
  2. edit the following xml location in that file: /plugin/extension/product/property[@name="appname"], set attribute value to something else. don't use spaces, keep length below (up until) 40.
  3. optionally also set the window title: /plugin/extension/product/property[@name], set attribute name to something else.
  4. in your existing eclipse shortcut, append -clean and run it once. you will notice the //product/property[@name] attribute being used in the eclipse window title. afterwards, you can remove -clean again.
  5. follow the quick howto above

a quick explanation on what's going on here:

  1. inside the .lnk file, an attribute is stored, which can't be entered by using the windows shortcut property dialog. if you copy a .lnk file, the attribute will copy with it.
  2. windows groups by identical property, appid for short
  3. eclipse does not have an appid at startup. first the jvm is started, then the eclipse core/platform is started, and then the startup plugin is loaded. in this last stage, an api call is done to set the appid to the value inside a plugin.xml file. see above: extended howto item 2
  4. when you drag a manually created shortcut .lnk file to the taskbar, it makes sense that windows can't put this appid into the new 'pinned' version of the .lnk file. it can only be detected at runtime.
  5. when you start an eclipse application, right click on the running taskbar icon, pin this program to taskbar -> then windows will detect the appid and store it in the 'pinned' .lnk. but, partly because of the jvm process redirection, windows does not detect the command-line parameters, environment, working folder (at startup at least), and the icon path + icon index. so you have to:
    1. do a file copy of the .lnk file and fill in the missing gaps yourself
    2. or, use a shortcut creation tool that understands properties (there are plenty)
    3. or, use the windows api directly

sincerely hope this will reduce the amount of haywire eclipse taskbars icons on the workstations around me,

cheers, tw


i just want to add this for the win10 users.

edit eclipse.ini to add these lines at the end before the line --launcher.appendvmargs:

-vm c:/program files/java/jdk1.8.0/jre/bin/server/jvm.dll

you need set the compatibility to windows vista as well in order for it to work.


setting eclipse.exe to compatibility mode works


riccardo's solution from the eclipse bug report worked for me, but i don't get recently opened projects, etc. from the task bar. is anyone experiencing that these workarounds restore that behavior?

i have the same problem on windows 7 x64 with helios x64, but for me the following workaround works with the option "always combine, hide labels" for taskbar buttons.

  • check your "eclipse.ini" for the specified vm and make sure the path points to the bin directory of your jdk or jre (and not to javaw.exe). for me the argument is "d:/development/languages/java/development kit/bin/" without quotes.
  • unpin eclipse from the taskbar or delete the shortcut
  • run "eclipse.exe" from the explorer and choose your workspace
  • pin eclipse to the taskbar after the splash screen was loaded and when the main window is shown

Related Query

More Query from same tag