Error: MySQL shutdown unexpectedly.

Hi,
I am running my WP site on localhost using XAMPP.
Today, aftter initiating XAMPP and Apache server, tried to start MySql and I got this error message:

Error: MySQL shutdown unexpectedly.
19:49:59 [mysql] This may be due to a blocked port, missing dependencies,
19:49:59 [mysql] improper privileges, a crash, or a shutdown by another method.
19:49:59 [mysql] Press the Logs button to view error logs and check
19:49:59 [mysql] the Windows Event Viewer for more clues
19:49:59 [mysql] If you need more help, copy and post this
19:49:59 [mysql] entire log window on the forums

If I look at the log file entries for this start I find:

2023-03-22 19:49:58 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-03-22 19:49:58 0 [Note] InnoDB: Uses event mutexes
2023-03-22 19:49:58 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-03-22 19:49:58 0 [Note] InnoDB: Number of pools: 1
2023-03-22 19:49:58 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-03-22 19:49:58 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-03-22 19:49:58 0 [Note] InnoDB: Completed initialization of buffer pool
2023-03-22 19:49:58 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-03-22 19:49:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-03-22 19:49:58 0 [Note] InnoDB: Setting file ‘D:\xampp\mysql\data\ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
2023-03-22 19:49:58 0 [Note] InnoDB: File ‘D:\xampp\mysql\data\ibtmp1’ size is now 12 MB.
2023-03-22 19:49:58 0 [Note] InnoDB: Waiting for purge to start
2023-03-22 19:49:58 0 [Note] InnoDB: 10.4.27 started; log sequence number 887527925; transaction id 272974
2023-03-22 19:49:58 0 [Note] InnoDB: Loading buffer pool(s) from D:\xampp\mysql\data\ib_buffer_pool
2023-03-22 19:49:58 0 [Note] Plugin ‘FEEDBACK’ is disabled.
2023-03-22 19:49:58 0 [Note] InnoDB: Buffer pool(s) load completed at 230322 19:49:58
2023-03-22 19:49:58 0 [Note] Server socket created on IP: ‘::’.

where no error message can be found.
I read somewhere thta this issue may be due to the Db being closed improperly.
If this is the problem, what can be done to fix de database?