There is nothing wrong in your workflow, just the "I Moved It" is wrong.
There is a primarily thing and a secondary thing in this:
Foremost
When moving a VM between different system architectures, you need to say "I copied it". Then VM will update itself when starting and may ask for a reboot, too. (It was so ALWAYS, not sure if they have done something which works in some cases.) Anyway, what you see is what happens (I gather, not sure about your error messages, nevertheless it doesn't work how you did it.)
I just a couple of days ago copied a VM between different Intel architectures, from Win11 to Kubuntu, from 17.5.2 to 26H1u1 - there was no problem and this is how it always has been.
SECONDARY:
Windows GUI copying can fail without telling that it fails. Use a reliable way, like robocopy for copying. You need to redo your exercise, at least I don't know how to fix a VM after a wrong answer. I hope you have a backup or something.
TERTIARY:
If you have the VMware Workstation GUI open and in its TAB there is your VM, while copying, it is wrong, too. There are files open in your VM directory if you have that. OR if you even start the GUI while copying there are files changing in the VM directory, which is even worse.