Bug #76068 Workbench crashes on start on Windows 7
Submitted: 26 Feb 2015 17:46 Modified: 5 Apr 2015 17:40
Reporter: Facundo Segovia Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.2.4 OS:Windows (Windows 7)
Assigned to: CPU Architecture:Any

[26 Feb 2015 17:46] Facundo Segovia 
Description:
I've installed Workbench 6.2.4 on Windows 7.
When I try to execute the program, it crashes on the start.

I tried to solve it installing the pre-requisites mentioned in the MySQL website:
. Microsoft .NET Framework 4 Client Profile
. Visual C++ Redistributable for Visual Studio 2013

But the same thing happened. The error message is the following (in spanish).
Firma con problemas:
  Nombre del evento de problema:	APPCRASH
  Nombre de la aplicación:	MySQLWorkbench.exe
  Versión de la aplicación:	6.2.4.12437
  Marca de tiempo de la aplicación:	5462a5c4
  Nombre del módulo con errores:	MSVCR120.dll
  Versión del módulo con errores:	12.0.21005.1
  Marca de tiempo del módulo con errores:	524f83ff
  Código de excepción:	c000001d
  Desplazamiento de excepción:	0000000000092bc3
  Versión del sistema operativo:	6.1.7600.2.0.0.256.1
  Id. de configuración regional:	11274
  Información adicional 1:	1d77
  Información adicional 2:	1d779894dfdbd81f28a677b11517b9d9
  Información adicional 3:	c144
  Información adicional 4:	c144def566404c2192c58b42f02357d3

Later, I've downloaded a dll file mentioned their (MSVCR120.dll) from a dll website. Tried again, but the error is still happening, but this time with the file KernelBase.dll.

What can I do?

How to repeat:
Starting the application
[5 Mar 2015 17:40] MySQL Verification Team 
Please check http://bugs.mysql.com/bug.php?id=76145:

 [4 Mar 16:03] Patrick Remy

Problem solved:

My env var Path was empty.
Put again c:\windows\system32 in path var and everything is ok.
[6 Apr 2015 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".