KB4517211 causes VMware Workstation Pro 14.1.7 to fail

Anonymous
2019-10-01T10:37:08+00:00

Good morning,

I have discovered that my installation of three updates on Saturday September 28 2019 has caused the failure of VMware Workstation Pro 14.1.7 to start. On Sunday, when I attempted to run VMware Workstation, it produced a Notification that said "VMware Workstation Pro can't run on Windows". 

Luckily, I was able to find that, when I uninstalled the three updates, it was the uninstallation of KB4517211 that allowed VMware to run.

Now, this morning, KB4517211 has installed itself autonomously - I thought that should not happen any more - and VMware again "can't run".

So, once again uninstall KB4517211, restart and VMware can now run. Microsoft Updates now paused for 7 days.

I would like someone to tell VMware about this: I cannot find a way to do it myself. Even better if Microsoft and VMware can sort this out.

I hope that this post is not unnecessarily duplicating news from others: this is the first time I have posted anything, so don't really know where (or how) to do it.

Happy days, Guy

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

30 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-10-01T23:27:57+00:00

    This update also breaks VMWare 12.5.9 from running as well.

    VMWare 12.5.9 was the last version that supported older CPU's so upgrading VMWare is not an option.

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments
  2. Anonymous
    2019-10-17T18:26:46+00:00

    Reg fix for this - tested OK

    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

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2019-10-02T08:50:54+00:00

    Is there a workaround?

    Neither upgrading VMware nor disabling windows updates is an option for us - with about 100 licenses I would have to pay 13000 EUR for the upgrade to v.15.x.

    In case of doubt I have to switch off Windows updates in the whole company...

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  4. Anonymous
    2019-10-14T12:22:28+00:00

    For me helps just changing application vmplayer name

    C:\Program Files (x86)\VMware\VMware Player\vmplayer

    To

    C:\Program Files (x86)\VMware\VMware Player\vmplayer1

    Just that’s all

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments
  5. Anonymous
    2019-10-03T14:13:34+00:00

    Hi

    I also had the same problem. But yesterday I've found following article and tried to follow the instructions described there. In brief: this approach replaces current sysmain.sdb file with an older one. Read more in that article...

    https://www.tenforums.com/windows-10-news/141310-cumulative-update-kb4517211-windows-10-v1903-build-18362-387-sept-26-a-14.html#post1735768

    Now I can run Workstation 12 under latest Windows 10 i.e. including KB4517211 without problem.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments