Crash loop on startup after installing Office plugin

Dbeaver CE on Win10x64, installed with Chocolatey. I’ve had v5.2.3 installed for about a month, zero issues with it (awesome program!) until I installed Extension Office today. Install went through all it’s steps without any apparent problem.

At end when prompted to Restart I said yes. The splash screen shows, then disappears, then shows again, then disappears, then shows… forever. I had to use pskill dbeaver from Sys Internals to stop it (in Task Manager it’s a whack-a-beaver game to nab and press delete on the process before it disappears).

I upgraded to v5.3.0.201812092025 using choco upgrade dbeaver. After this dbeaver launched normally, and asked if I wished to also import and uprade the Office extension. I said yes and checked the box to fetch latest. At end I said no to automatic restart and closed dbeaver manually.

On next launch the crash looping resumed. While looping the .log and dbeaver-debug.log files under %USERPROFILE%\.dbeaver4 are not updated.

I renamed .dbeaver4 to something else, and then .dbeaver-drivers: No difference in either case.

I finally managed to get Dbeaver back again my renaming %USERPROFILE%\.eclipse\org.jkiss.dbeaver.product_5.3.0_1535670467_win32_win32_x86_64 and then cancelling the plugin install/upgrade procedure.

((Note: issue template says to read contributing first, but that document is empty))

[mk1tools]

Same problem. After each DBeaver upgrade, I install Office plugin. Then DBeaver start to loop on splash screen. I install DBeaver for “anyone” on Windows 10. I found this workaround.

1. upgrade Dbeaver
2. Start Dbeaver and install Office plugin, without automatic restart. Close Dbeaver.
3. Start DBeaver “as administrator” and install Office plugin, without automatic restart. Close Dbeaver.
4. Start DBeaver “as administrator”. Close Dbeaver.
5. Start DBeaver normally

[Rich28]

I’ve also ran into this problem, which forces the needed to restart Windows. Not good, though in my case I was able to get dbeaver working again by deleting the ‘plugin’ folder located in %USERPROFILE%.eclipse\org.jkiss.dbeaver.product_6.0.3_1535670467_win32_win32_x86_64. Hopefully there will be a fix to this issue.