OK, I now seem to have a new way to prove that the problem is with the latest version of the Minecraft game, not the virtual machine. Before, when I played Minecraft, I had a habit of backing up the entire virtual machine for archiving. I was most afraid of this day. The last time I backed up the archive was on May 11, 2025. The game.ldbk, I reloaded the old backup archive and found that the old version of Minecraft v1.21.72 was normal without any problems. This strange situation only appeared after v1.21.81.
ok This problem has been solved
Thanks to "lollienl" for the feedback. I thought the problem I encountered had been ignored by Mojang officials, and I don't want to continue playing Minecraft recently. My current mood: Actually, this is what I feel
"I have done a complete test"
"I submitted a detailed bug report"
"I even helped Mojang confirm which version started to have problems"
"But the official has no response at all... Then why am I still playing this game?"