When setting up this environment, it is recommended to use the installation instructions directly.
There is also a video, you can refer to: Video operation Click to open the link
In addition, the above settings, you may be unable to start the MySQL situation, when we go to check the MySQL log, there will be the following problems
[ERROR] innodb:attempted to open a previously opened tablespace. Previous tablespace Isaactest/wp_usermeta uses space id:2 at filepath:. \isaactest\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space id:2 at filepath:. \mysql\innodb_index_stats.ibd
InnoDB:Error:could not open single-table tablespace file. \mysql\innodb_index_stats.ibd
Innodb:we do not continue the crash recovery, because the table may become
Innodb:corrupt If we cannot apply the log records in the InnoDB log to it.
Innodb:to Fix the problem and start mysqld:
INNODB:1) If There is a permission problem in the file and mysqld cannot
Innodb:open the file, you should modify the permissions.
INNODB:2) If The table is not needed, or can be restore it from a backup,
Innodb:then you can remove the. ibd file, and InnoDB would do a normal
Innodb:crash recovery and ignore that table.
Innodb:3) If the file system or the disk is broken, and you cannot remove
Innodb:the. ibd file, can set innodb_force_recovery > 0 in MY.CNF
Innodb:and force InnoDB to continue crash recovery here.
This problem has occurred several times, every time the problem is to re-get MySQL.
I used Xampp 1.83, and today I finally found a solution.
Add the My.ini in the D:\xampp\mysql\bin below
Innodb_force_recovery = 1
XAMPP DVMA Build Penetration test environment (Windows)