Windows 10: Update KB4522015 breaks VMware Workstation

[steven36]

It seems, that Update KB4522015 for Windows 10 Version 1903 breaks older Versions of VMware workstation. This virtualization software can’t launch after installing this patch.

 

 

Update KB4522015 for Windows 19 V1903

 

Update KB4522015 has been released on September 23, 2019 for Windows 19 V1903. This is a security update to Internet Explorer, release to mitigate a vulnerability in scripting. This update has been available only via Microsoft Update Catalog, but it is causing several issues (see the knows issues section of KB4522015 and link list below).

Issues with VMware workstation

Shortly after I’ve published the article Windows 10: Issues with Updates KB4522015, KB4522016 / KB4517211 (Sept. 2019) I got a user comment mentions issues with Vmware workstation. German blog reader Kay wrote:

old versions of VMware Workstation no longer work after KB4522015 update

There is a thread at reddit.com, where a user wrote ‘Cannot run VMware WS Pro 14 after KB4517211’. He posted the following screen shot.

 

One user wrote, that it has something to do with changes in Hyper-V and may be present since the release of Windows 10 version 1903. Other users has confirmed this issue. There is also a thread at VMware forum, where this issue has been discussed.

 

Windows 10 KB4517211 Stops VM workstation 12 From Starting

After installing this Windows update “KB4517211” VMWare workstation 12 no longer starts. Had to delete update….

Other users has confirmed this issue caused by Windows 10 V1903 update KB4517211:

We got the same issue but I don’t think that it is a good solution to just remove this update. Is there any other known fix for this issue?

It affects several versions of VMware workstation installed on Windows 10 Version 1903. At tensforum.com a user describes a workaround for VMware workstation 14. To do this, unzip the file sysmain.zip and copy it into the folder:

 

sysmain.sdb to C:\Windows\apppatch

 

Use the steps are described in the forum. This is because Microsoft can block the execution of applications or drivers via the sysmain.sdb file. The sdb file it provides does not block VMware. Update: See the comment below and use the Compatibility Administrator Toolkit to re-allow VMware workstation.

 

Affected software:

VMware Workstation Player or Pro version 12 and 14, installed in Windows 10 version 1903.

Cause:

As part of Cumulative Update (September 26, 2019; OS Build 18362.387 or newer) installation, database of programs prohibited by MS was updated, and invasive "Compatibility Assistant" component now prevents older VMware Workstation programs from run.

Resolution:

To run VMware Workstation programs again, it is necessary to replace one of "Compatibility Assistant" database files with an older version (before Cumulative Update mentioned above was installed). Use one of two following methods.

1. If you use a backup program which allows granular restore (on per-file basis)
- restore single and only one file C:\Windows\apppatch\sysmain.sdb from backup taken before the toxic Cumulative Update was installed

or

2. In other cases, manually replace the file C:\Windows\apppatch\sysmain.sdb
- in File Explorer, navigate to C:\Windows\apppatch folder
- rightclick on file sysmain.sdb, click Properties, Security, Advanced
- set Owner to Administrators, click OK
- grant Full Control permissions to Administrators, click OK
- rename the file sysmain.sdb to sysmain.bad
- unpack AllowVmware.zip file attached below to your desktop; it includes older sysmain.sdb file
- copy (not move) unpacked sysmain.sdb to C:\Windows\apppatch folder.

 downloaded here: AllowVmware.zip

Independently on method used, be prepared to apply this resolution again after some (not necessarily all) future Cumulative Updates.

Comments:

1. VMware Workstation 12.5.9 is the last version which can be run on processors belonging to Intel Core2 family, so upgrading to VMware version 15 (moreover expensive) isn't an option for some users.
2. The same symptom arises for many other installers, drivers and programs; sometimes it can be resolved either by renaming the installer, or by using five *.sdb files from the oldest versions of Windows 10 (1507 or 1511 without updates), or both.
3. Related thread: https://answers.microsoft.com/en-us/...f-fec7daec40d7

 

Sources  and more Info:

https://borncity.com/win/2019/10/03/windows-10-update-kb4522015-breaks-vmware-workstation/

https://www.tenforums.com/virtualization/141820-vmware-workstation-pro-cant-run-windows-message.html#post1737908

https://answers.microsoft.com/en-us/windows/forum/all/kb4517211-causes-vmware-workstation-pro-1417-to/aef3bcf9-0e44-4353-bc7f-fec7daec40d7

 

 

[ashish.k]

Woha... I just came here to look for a newer version just because of this issue but well it seems I have to wait for some time. I'm really not in favor of the workaround mentioned, thanks though.

[mymiabear]

thank god i run Win10 PRo LTSC.

 

What a POS windows 10 has because. Every update breaks something

[zanderthunder]

10 hours ago, mymiabear said:

thank god i run Win10 PRo LTSC.

 

What a POS windows 10 has because. Every update breaks something

In fact, LTSC versions support for 10 years so it's a bit safe.

[mymiabear]

That's why I am running it.

 

1) None of the existing bloat. None of the crap I don't want

2) None  of the new "features" (aka new stupid crap microsoft wants to push on its users) for at least 2-3 years

3) updates are tested first before pushing to LTSC machines. the vast majority of users are the"test dummies" for Microsoft

4) It 'feels' faster. This is subjective

5) REAL dark mode was enabled easily in LTSC while Pro wasn't able to do it.

 

Only drawback so far is i can't test the new sandbox feature but that's POS anyways compared to Sandboxie and VMware.  I am so glad Nsaneforumers convinced me to run LTSC.