Bug #547 MySQL 4.0.xx crashes on Windows XP Pro systems
Submitted: 30 May 2003 8:09 Modified: 30 Jun 2003 10:49
Reporter: [ name withheld ] Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Installing Severity:S1 (Critical)
Version:4.0.xx OS:Microsoft Windows (Windows XP)
Assigned to: CPU Architecture:Any

[30 May 2003 8:09] [ name withheld ]
Description:
When installing the MySQL 4.0.12 or .13 on Windows XP it crashes on next restart.

How to repeat:
 How to repeat it:

a) on a new fresh system I downloaded mysql zip file
b) extracted on the c:\windows\temp
c) executed the setup.exe and select all next (defaults)
d) run c:\mysql\bin\winmysqladmin
e) enter a username/password

it runs the mysql server without problems

now,

a) reset the system

when windows starts it displayes the winmysqladmin form.
This form normally minimizes but it doesn't. MySQL crashes.
I request mysql service stop (by services console or command
line) but It doesn't respond. I try to run mysql.exe from
command line, it doesn't respond. No messages like (unable
to connect, no servers installed/running etc.). Nothing at all.
I can only kill the process with ctrl+alt+del

I found it on 4 windows xp systems with 4.0.13 and .12
One system has been formated and reinstalled everything from
the ground. The same problem.

Suggested fix:
Test MySQL on Windows XP
[30 May 2003 10:49] Miguel Solorzano
I did some tests on XP without to find the problem reported, however
seem to me that the behavior reported maybe is the effect of the
action from a firewall tool.
Can you verify in the advanced network properties if your firewall
is active taking a look in its log file for any events reported
and even nothing reported to make a test disabling the firewall.
[9 Jan 2005 20:24] Tomi Jaskari
This crash is still there. I installed essential pack and it crashed when connected with MySQL Query Browser. Tried also with firewall off. No effect.

This is Windows XP Professional with SP2
[14 Feb 2005 22:51] 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".