"VMware Workstation Pro can't run on Windows" Message

I cannot reproduce the problem. Installed 2004, fully patched, installed vmplayer 12.5.9, it runs OK even without shim database patch or file renaming.


------------------------------------------------------
This dialog


is completely different from


...the first is of course harmless, non-blocking.

bosman said:

I had an issue when upgrading to Win10 2004 with VM12 during the actual upgrade. I had the compatibility fix but couldn't run and actual upgrade.
for me, I just renamed the vmplayer.exe and vmware.exe - just put a my_ infront of the filenames...

Tnxs this worked for me .

- - - Updated - - -

muchomurka said:

I cannot reproduce the problem. Installed 2004, fully patched, installed vmplayer 12.5.9, it runs OK even without shim database patch or file renaming.


------------------------------------------------------
This dialog


is completely different from


...the first is of course harmless, non-blocking.

The problem was on my host 12.5.9 already was installed and then the update to 2004 halted, telling me to remove vm-player or update it to 15. But 15 will not run on my host due to cpu issues . So i got afraid 12.5.9 couldn't run on the 2004 update.

But after renaming the player exe the install was finished with no faults.
Renaming the player exe again . run it and then got the first dialog you described and no everything workes again on a updated system.



Greetings Willem

So the problem is installing 2004 update, not running vmware wksta/player. Glad you resolved it.

My problem has been solved

Does anyone know why the 'compatibility administrator' is in 'Read only' mode in 2004?

bird333 said:

Does anyone know why the 'compatibility administrator' is in 'Read only' mode in 2004?

Anybody?

bird333 said:

Does anyone know why the 'compatibility administrator' is in 'Read only' mode in 2004?

Ok now my 1909 win pro machine wants to update to 20H2. Anybody know how I can keep vmware running?