Accepted answer

ok so i figured it out. go to yourworkspace/.metadata/.plugins and delete everything in there. eclipse will start and repopulate the folder.


i tried the option above of moving the plugins but it didn't work. my solution was to delete the entire .metadata folder. this meant that i lost my defaults and had to import my projects again.


read my answer if recently you have been using a vpn connection.

today i had the same exact issue and learned how to fix it without removing any plugins. so i thought maybe i would share my own experience.

my issue definitely had something to do with spring framework

i was using a vpn connection over my internet connection. once i disconnected my vpn, everything instantly turned right.


definitely a network/proxy thing. i connect via wifi and a corporate gateway. deleted workspace, reinstalled ggts - still hangs. turn off the network - launches fine.


i have same problem but i solve it by adding environment variable (run --> run configuration --> environment variable ) as

variable : java_ipv6
value :


i moved workbench.xmi located at workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi to a backup folder. then started eclipse and waited for all background processes to finish. then i closed eclipse and moved my backup copy of workbench.xmi back (overwriting the one created with the last launch). eclipse launched fine and i got all my settings back.


if you deleted all data in .metadata directory. there is a quick way to import all your projects again. try this:

file --> import --> general: select existing projects into workspace --> select root directory: browse to old workspace folder (the same with the current workspace folder is ok) --> finish.


i tried several of the options posted in this article, but it worked for me using this option in eclipse.ini:



maybe worth mentioning that when i had this problem i followed bia.migueis's advice - move everything out of the plugins folder - and the workspace would open again, minus a lot of my configuration. but then after that, i copied/overwrote all the original files back into the plugins folder and opened the workspace again: it still worked and the settings i'd had before seemed to be intact.


today, i had the same problem. my eclipse refused to start. when i double clicked on eclipse icon i was able to see splashscreen for a second and then nothing happen. tried most of the solutions here: removed lock file, renamed workspace, tried to start eclipse with different clean parameters. i even put a new copy of eclispe and tried to start with a new workspace. nothing!

my logs were showing bunch of errors from yesterday when my workstation was rebooted at 17:45.

!entry org.eclipse.ui.workbench 4 2 2014-12-17 17:45:12.178
!message problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
!stack 0

in the end this very simple change (look below) saved my eclipse together with my workspace!


i edited eclipse.ini and added following line:

c:\program files\java\jdk1.6.0_26\bin\javaw.exe

eclipse has started again with all my projects inside! i hope this can help.


i deleted the workbench.xmi in the folder workspace/.metadata/.plugins/org.eclipse.e4.workbench/.

i got this error because a build hung and then i tried to quit. however, i had unsaved changes. this prompted the following errors in logfile about unsaved changes and jobs that are not finished.



$ rm your_project_dir/.metadata/.plugins/org.eclipse.core.resources/.snap

original source: job found still running after platform shutdown eclipse


this works like champ on mac os or windows.

remove workbench.xmi located at workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi. then start your eclipse or adt. this will not erase your workspace or repository.

remove workbench.xmi cmd:

rm workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi.


removing workbench.xmi under workspace/.metadata/.plugins/org.eclipse.e4.workbench/ worked for me. it did not remove the existing projects.


i used eclipse -clean -clearpersistedstate and that worked for me. you will lose your window layout configuration, but that seems minor to me.

for linux systems try: ./eclipse -clean -clearpersistedstate

see eclipse juno doesn't start

Related Query

More Query from same tag