Bug #106282 MySQL Workbench >= 8.0 crashed at startup
Submitted: 25 Jan 2022 16:40 Modified: 26 Jan 2022 8:58
Reporter: Timo Frenzel Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:>= 8 OS:Windows (10)
Assigned to: CPU Architecture:x86 (128 GB RAM, 14 Cores / 28 Threads)

[25 Jan 2022 16:40] Timo Frenzel 
Description:
Workbench does not start. via the CLI I get the following

Unbehandelte Ausnahme: System.AccessViolationException: Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist.
   bei wb.WBContextUI.init(WBContextUI* , WBFrontendCallbacks* , WBOptions* )
   bei MySQL.Workbench.WbContext.init(WbFrontendCallbacks callbacks, WbOptions options, VoidStrUIFormDelegate create_main_form_view)
   bei MySQL.GUI.Workbench.Program.Main(String[] Args)

How to repeat:
# & 'C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe' -help
[25 Jan 2022 17:38] MySQL Verification Team 
Thank you for the bug report. Please re-install WorkBench with repair optio, if the issue continues provide the wb.log file using the Files tab.
[26 Jan 2022 6:10] Timo Frenzel 
Little informations...

I have now deleted the Workbench folder under "C:\Users\xxxx\AppData\Roaming\MySQL". Now i can start workbench.
[26 Jan 2022 8:58] MySQL Verification Team 
Thank you for feedback.