Bug #79720 MySQL Workbench is not opening in Windows 10
Submitted: 21 Dec 2015 11:56 Modified: 21 Jan 2016 19:34
Reporter: Mithilesh Kumar Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.6.0 OS:Windows (Windows 10)
Assigned to: CPU Architecture:Any

[21 Dec 2015 11:56] Mithilesh Kumar
Description:
I hope that I am not spamming. I recently upgraded my windows to windows 10 from windows 7. I re-installed MySQL Workbench. But I am not able to open it, there is no error message as well.

I also upgraded mysql community server pack to latest version. I am able to use mysql odbc connector to connect to remote server. But MySQL workbench is not working.

Error log
---------
Faulting application name: MySQLWorkbench.exe, version: 6.3.6.0, time stamp: 0x56698b0d
Faulting module name: KERNELBASE.dll, version: 10.0.10586.0, time stamp: 0x5632d1de
Exception code: 0xe0434352
Fault offset: 0x0000000000071f08
Faulting process id: 0x85c
Faulting application start time: 0x01d13bdf2049ff98
Faulting application path: C:\Program Files\MySQL\MySQL Workbench 6.3 CE\MySQLWorkbench.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: b4d23999-f7f8-4a23-a770-085904b014f6
Faulting package full name: 
Faulting package-relative application ID: 

How to repeat:
Whenever I open workbench it don't open without any error message.
[21 Dec 2015 12:00] Mithilesh Kumar
I also followed this bug report and updated the suggested dll but error is still there:

https://bugs.mysql.com/bug.php?id=75673
[21 Dec 2015 19:34] MySQL Verification Team
I couldn't repeat on Windows 10 Pro. Please attach here the wb.log file which you can find at a path like below:

C:\Users\here_your_user_name\AppData\Roaming\MySQL\Workbench\log

Also print here the path above (just to check if the user has accents or symbols non English characters).
[22 Jan 2016 1:00] Bugs System
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".