Normal
Looking at the MySQL logging in the application event log:[collapse]"13/08/2015 09:34:08";"MySQL";"(0)";"Information";"The description for Event ID '-1073741724' in Source 'MySQL' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'Plugin 'FEDERATED' is disabled. '";"3221225572""13/08/2015 09:34:48";"ESENT";"General";"Information";"wuauclt (2348) The database engine 5.01.2600.5512 started.";"100""13/08/2015 09:34:48";"ESENT";"General";"Information";"wuaueng.dll (2348) SUS20ClientDataStore: The database engine started a new instance (0).";"102""13/08/2015 09:35:43";"SecurityCenter";"(0)";"Information";"The Windows Security Center Service has started.";"1800""13/08/2015 09:36:04";"MySQL";"(0)";"Information";"The description for Event ID '-1073741724' in Source 'MySQL' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'Event Scheduler: Loaded 0 events '";"3221225572""13/08/2015 09:36:04";"MySQL";"(0)";"Information";"The description for Event ID '-1073741724' in Source 'MySQL' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: ready for connections.Version: '5.1.38-community' socket: '' port: 3306 MySQL Community Server (GPL) '";"3221225572"[/collapse]...that's taking a very long time to start. Approximately 2 minutes in total. 40 seconds for the DB engine to start up and 76 seconds for the DB to come online. That's really unusual in my experience.As suggested above, I'd be auto-repairing again... checking the startup time after that... then checking the MySQL log if that is not sufficient.
Looking at the MySQL logging in the application event log:
[collapse]
"13/08/2015 09:34:08";"MySQL";"(0)";"Information";"The description for Event ID '-1073741724' in Source 'MySQL' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'Plugin 'FEDERATED' is disabled. '";"3221225572"
"13/08/2015 09:34:48";"ESENT";"General";"Information";"wuauclt (2348) The database engine 5.01.2600.5512 started.";"100"
"13/08/2015 09:34:48";"ESENT";"General";"Information";"wuaueng.dll (2348) SUS20ClientDataStore: The database engine started a new instance (0).";"102"
"13/08/2015 09:35:43";"SecurityCenter";"(0)";"Information";"The Windows Security Center Service has started.";"1800"
"13/08/2015 09:36:04";"MySQL";"(0)";"Information";"The description for Event ID '-1073741724' in Source 'MySQL' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'Event Scheduler: Loaded 0 events '";"3221225572"
"13/08/2015 09:36:04";"MySQL";"(0)";"Information";"The description for Event ID '-1073741724' in Source 'MySQL' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe: ready for connections.
Version: '5.1.38-community' socket: '' port: 3306 MySQL Community Server (GPL) '";"3221225572"[/collapse]
...that's taking a very long time to start. Approximately 2 minutes in total. 40 seconds for the DB engine to start up and 76 seconds for the DB to come online. That's really unusual in my experience.
As suggested above, I'd be auto-repairing again... checking the startup time after that... then checking the MySQL log if that is not sufficient.