rename the file sysmain.sdb to sysmain.bad grant Full Control permissions to Administrators, click OK rightclick on file sysmain.sdb, click Properties, Security, Advanced in File Explorer, navigate to C:\Windows\apppatch folder In other cases, manually replace the file C:\Windows\apppatch\sysmain.sdb restore single and only one file C:\Windows\apppatch\sysmain.sdb from backup taken before the toxic Cumulative Update was installedĥ. If you use a backup program which allows granular restore (on per-file basis) The following two methods are now obsolete.Ĥ. Sadly, this method does not work in my test environment, someone else can try it too. ( not working under some circumstances): Use Local or Group Policy to disable Application Compatibility components. Or - if you do not need to install it - extract the following zipfile.ģ. (quick and simple): Apply the following regfile to unblock VMware Workstation Player & ProĬode: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Application Compatibility Toolkit\Compatibility Administrator (64-bit)\Compatadmin.exe" To run VMware Workstation programs again, it is necessary to either override "Compatibility Assistant" default behavior or replace one of "Compatibility Assistant" database files with an older version (before Cumulative Update mentioned above was installed). VMware Workstation Player or Pro version 12 and 14, installed in Windows 10 version 1903.Īs part of Cumulative Update (SeptemOS 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.
VMware Workstation Pro can't run on WindowsĬheck for an updated version of this app that runs on Windows. Furthermore, the following message is displayed: After installing new Cumulative Update, VMware Workstation software cannot start.
0 kommentar(er)
