17.6.2 - Three errors - no clue how to solve them

[thewul]

(1)

This virtual machine's snapshot is expecting graphics features that VMware is unable to provide on this host.
Restoring the VM might be possible, but could cause serious problems if the guest OS is relying on any of the missing features.
Select one of the following options:
Cancel - Do not resume the VM.
Continue - Attempt to resume the VM despite the missing graphics features. This might lead to problems such as a VM failure.

(2)

An error occurred while restoring the virtual machine state from file "D:\Virtual Machines \Windows 10 x64\Windows 10 x64-Snapshot42.vmsn\
An error caused the restore operation to fail.
Cancel the restore operation and correct the error, or discard the snapshot's state and power off.
The saved snapshot will not be affected.

(3)

No 3D support is available from the host. The 3D features of the virtual machine will be turned off.
Failed to start the virtual machine.

Any suggestions?
Thanks.

[Ian Forbes]

Did you copy this VM from another host machine or change the host's hardware?

[thewul]

Thanks for the response.

Nothing has changed.

However, just now I tried to reproduce the issue, launched WS and things went fine.
Windows (in VM) launched fine as well.
Closed everything and relaunched WS and Windows, fine again.

Beats me ...

That said, the "3D"error  (#3 in my earlier post), I got that one on earlier occassions, but just closed it, not knowing what I am supposed to do.

Anyway, right now, the issue has miraculously been solved...

Thanks again.

[RaSystemlord]

I assume now that you get all this when starting a single VM. If not, let us know.

If this is a copy
- do NOT make a copy from an unclear situation, but after a proper shutdown and NOT having the Pro version Window open, which is showing that particular VM in a tab. Unclear situation is suspended, hibernated or in the middle of a snapshot resuming. Windows can confuse you, be clear that it is shut down.
- check the copy that it is a proper copy. If you copy over networking, do NOT rely in Windows GUI. Use robocopy

- take use 3D acceration OFF since it complains about it. Try only later what it does if it is ON

- use "I copied it", if you have a copy from another computer. The hardware architecture might not renew in the fly and thus you need to say "I copied it" (previously, it was always failing if the architecture changed and you said "I moved it"