News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Another dumb block: MS induced “VMware Workstation Pro can’t run on Windows”

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

    Tagged: 

    This topic contains 5 replies, has 6 voices, and was last updated by  gborn 1 week, 5 days ago.

    • Author
      Posts
    • #1995422 Reply

      woody
      Da Boss

      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.
    • #1995466 Reply

      anonymous

      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?

    • #1995516 Reply

      waynebialas
      AskWoody Plus

      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.

    • #1995690 Reply

      krzemien
      AskWoody Lounger

      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…

    • #1995977 Reply

      warrenrumak
      AskWoody Plus

      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 1 week, 5 days ago by  warrenrumak.
      2 users thanked author for this post.
    • #1996037 Reply

      gborn
      AskWoody_MVP

      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.

      • This reply was modified 1 week, 5 days ago by  gborn.

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

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

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.