Another dumb block: MS induced “VMware Workstation Pro can’t run on Windows”

Topic

New Reply

I just hear about this from Office Watch, but checking around, it’s also described on Tenforums and on the VMWare blog. When you install any of the re
[See the full post at: Another dumb block: MS induced “VMware Workstation Pro can’t run on Windows”]

1 user thanked author for this post.

GreatAndPowerfulTech

Reply | Quote

Replies

Does anybody know if there’s a reason why VMWare versions prior to 15.5 are prohibited from running on post-September-updated versions of Win10 1903?

To force people to shell out for 15.5?

Reply | Quote

Thank you Woody.  Your solution also seems to work well for an older copy of vmplayer (which I need to run on my configuration).  Thank you again.

Reply | Quote

Old habits die hard!

Remind me of equally successful ‘try before buy’ approach when system date prior to the installation of something new was changed by several years forward…

Reply | Quote

[warrenrumak]

Apply the following .reg file to override the Appcompat database.  Better solution than renaming the .exe file since it can be rolled out by Group Policy or as part of an initial setup script…

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]
"{3d9912c3-cb54-4f34-ab71-1d429553bf96}"=dword:00000077
"{66f21bbc-149a-411b-8e11-880af7c1266c}"=dword:00000077

 

• This reply was modified 5 years, 7 months ago by warrenrumak.

2 users thanked author for this post.

Toa Of Justice, doriel

Reply | Quote

[gborn]

I’ve covered this issue within my blog post Windows 10: Update KB4517211/KB4522015 breaks VMware Workstation in the begin of October 2019.

The most simple solution, some people mentioned was to rename the vmware exe file to something like vmware1.exe. Then the block isn’t applied.

The reason for this compatibility block, I’ve heared is, that Microsoft has enabled some hyper-v based virtualization feature somewhere in Windows 10 and setzt a block with the recent patch (forgot the location with details). That may cause conflicts with older VMware workstation/player versions in some szenarios. But maybe I’m wrong – it was (as far as I remember) just a suspicion – and people who are using the workarounds was able to run VMware flawless.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

• This reply was modified 5 years, 7 months ago by gborn.

Reply | Quote