Dang! My 64-bit VM image won't start after my host goes to sleep!

Here's a new one:

You unfortunately put your Windows 10 host computer to sleep - and it was running a few guest VMs that are 64-bit OS.

Upon awaking your computer, and restarting your VMs, you are greeted with an unfamiliar message:

Next step is to assess that your BIOS is actually set to accommodate Virtualization Technology (VT), right?

Rebooting your computer, you fiddle around to access your BIOS (it might be the F2 key, F8, F12... oh geez, they don't make these standard, do they?) - you finally get the interface to the BIOS.

You navigate to the "Device Configuration" or "CPU Settings" or similar language - to realize the VT is actually set to "Enable". What's up with this?...

Well, it turns out that "somewhere" VMware Workstation got confused. It does believe the VT setting read from the BIOS is NOT enabled.

To remedy to this, do as follows:

1. Toggle the "Enabled" VT value to "Disabled"
2. Save your BIOS settings (yes, trust me)
3. Restart the computer - so the "Disabled" flag is indeed read from VMware.
4. Open the VM image that generated the error you got earlier. Yes, you should still have the same error - please!
5. Once this has been demonstrated, shut down your applications and restart - again - your computer
6. Hit the BIOS maintenance button again - this time, we want to - you guessed it...
7. Enable the VT.
8. Once this is done, save and reboot the computer.
9. Start your VM with the offending error
10. Witness the error disappeared
11. If not - oh well, I guess the next step is to download a new BIOS firmware.

Why is this? As mentioned, my best guess is VMware Workstation server got confused when the system went to sleep. This is documented around on the web - and too lengthy to cover in this entry.