MySQL Bugs: #78136: MySQL Workbench 6.3 CE

Bug #78136	MySQL Workbench 6.3 CE - Error while loading image
Submitted:	19 Aug 2015 14:39	Modified:	30 Nov 2015 0:33
Reporter:	Vignesh S	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	MySQL Workbench 6.3 CE	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Whenever I click on the MySQL Workbench Icon, "Error while loading image' pops up, and when I try to open a connection, It says
"Parameter is not valid"
"We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. 

Please make sure to include a detailed description of your actions that lead to this problem.

Thanks a lot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team"

I am having this problem after I restarted my computer today.

How to repeat:
Whenever I click on the MySQL Workbench Icon, "Error while loading image' pops up, and when I try to open a connection, It says
"Parameter is not valid"
"We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. 

Please make sure to include a detailed description of your actions that lead to this problem.

Thanks a lot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team"

This happens when I try opening workbench 6.3. 

Application: MySQLWorkbench.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
Stack:
   at MySQL.GUI.Workbench.Program.Main(System.String[])

Please try version 6.3.5. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".