[Bug 47647] New: Laragon hangs while "Initializing data"

https://bugs.winehq.org/show_bug.cgi?id=47647

Bug ID: 47647
           Summary: Laragon hangs while "Initializing data"
           Product: Wine
           Version: 4.14
          Hardware: x86-64
               URL: https://github.com/leokhoa/laragon/releases/download/4
                    .0.15/laragon-full.exe
                OS: Mac OS X
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]

$ openssl sha256 laragon-full.exe 
SHA256(laragon-full.exe)=
55f1c421a6631755da5de30dcdc72c361b8dbf688fc8b773bdd5a10f36dd2f73

When trying to start the server in Laragon, it yields the following error
message:

Steps to reproduce:
1. Download and install Laragon from the provided URL.
2. Start the program from the default location (mine was C:/laragon)
3. Click the "Start all" button in the bottom left hand corner.

Laragon hangs while "Initializing data"... C:\laragon\data\mysql

[Bug 47647] Laragon hangs while "Initializing data"

https://bugs.winehq.org/show_bug.cgi?id=47647

Fabian Maurer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
           Keywords|                            |download
                 CC|                            |[e-mail]
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Fabian Maurer  ---
Confirming. However, on second start of laragon it claims that mysqld is
started, it doesn't work however. Separate bug?
Part from the log:
> 003b:err:eventlog:ReportEventW L"Do you already have another mysqld server running on port: 3306 ?"

[Bug 47647] Laragon hangs while "Initializing data"

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47647

--- Comment #2 from Tobias (:Tobbi) Markus  ---
Currently, because of https://bugs.winehq.org/show_bug.cgi?id=56387 I cannot
figure out whether this bug still occurs or not.