MySQL stops in windows VM and shows innodb error log sequence number is in future

2020-08-28 16:46:02 d64 InnoDB: Error: page 1 log sequence number 23113680
InnoDB: is in the future! Current system log sequence number 3181581.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.

I’m using VM and OS is Windows Server 2016 and Uniform Server.
MySQL stops upon this error and doesn’t work until it is restarted.
After restarting, it runs for some hours and stops again.
I have tried moving ib_logfile but still it didn’t help.
How to overcome this?

Go to Source
Author: Anushree Bharadwaj