"VMware Workstation Pro can't run on Windows" Message

Microsoft cannot be held responsible for keeping all older software functional

No complaints against the following dialog:

VMware Workstation Pro isn't guaranteed to run on current Windows
Check for an updated version of this app if possible.
Compatibility Assistant
Run it anyway - Check for updates

Small but significant difference.

In this case, it is up to VMware to fix it, to provide an update.

No way, VMware forces customers to buy an upgrade.

Does anyone knows of an email address that I can email sales instead of filling out some form where I need to provide info that I don't think is needed?

Danielx64 said:

Does anyone knows of an email address that I can email sales instead of filling out some form where I need to provide info that I don't think is needed?

Hi there

You could try the phone line then ask for sales: US phone nr :

1-877-486-9273

Cheers
jimbo

There is no need to replace the entire sysmain.sdb and fiddle with the ownership.
Doing that could cause a lot more issues down the road.
Instead I suggest using the Compatibility Administrator tool.

You can get it from here: https://docs.microsoft.com/it-it/win...ed/adk-install
(Download the Windows ADK for Windows 10, version 1903)
Make sure you select the tool (1st checkbox, it was unchecked by default for me) when you start the installer .

Once you have Compatibility Administrator installed, run it and find VMware entries under: System Database -> Applications
Disable entries that say "HARDBLOCK".


All done.

Biohazard said:

There is no need to replace the entire sysmain.sdb and fiddle with the ownership.
Doing that could cause a lot more issues down the road.
Instead I suggest using the Compatibility Administrator tool.

You can get it from here: https://docs.microsoft.com/it-it/win...ed/adk-install
(Download the Windows ADK for Windows 10, version 1903)
Make sure you select the tool (1st checkbox, it was unchecked by default for me) when you start the installer .

Once you have Compatibility Administrator installed, run it and find VMware entries under: System Database -> Applications
Disable entries that say "HARDBLOCK".


All done.

Hi there
BUT having done that can you run VMWare (rel 14 as the OP wants --- please post a screenshot of a VM running with VMWare rel 14 with a 19.XX or 20.XX Windows Host).

It's not a question of "Theoretically --this *should* work -- but DOES it actually work and solve the OP's problem.

AFAIK VMWare 14 doesn't work on latest (19.XX or 20.XX) releases of Windows --If it does could someone please post a screenshot. !!

I'm always willing to learn and accept information if it works -- however if VMWare itself says the program won't work then IMO if you CAN get it working --great stuff but in general you are probably wasting your time.

Cheers
jimbo

There is no need to replace the entire sysmain.sdb and fiddle with the ownership.

Biohazard: Very helpful, thank you.

Tested for VMware Workstation 12.5.9 & Daemon Tools 4471 Installer & Lenovo Power Manager Installer, all work without problems. Unfortunately I did not find entry for blocked amdacpksd.sys driver from Radeon Suite 16.3.2 so I still rely on drvmain.sdb file from Win10 version 1511.

Main article updated.

jimbo45 said:

Hi there
BUT having done that can you run VMWare (rel 14 as the OP wants --- please post a screenshot of a VM running with VMWare rel 14 with a 19.XX or 20.XX Windows Host).

It's not a question of "Theoretically --this *should* work -- but DOES it actually work and solve the OP's problem.

AFAIK VMWare 14 doesn't work on latest (19.XX or 20.XX) releases of Windows --If it does could someone please post a screenshot. !!

I'm always willing to learn and accept information if it works -- however if VMWare itself says the program won't work then IMO if you CAN get it working --great stuff but in general you are probably wasting your time.

Cheers
jimbo

Windows 10 host (version 1903, build: 18362.388).
VMware Workstation 14 Player running Ubuntu 19.04 (needed it to build OpenWrt firmware for my home router, non-commercial use).

It does work, tried and tested solution (sorry If that was unclear from my previous post).

As for what VMware says... I take everything with a grain of salt from people that have a business to run .

All the best.

muchomurka said:

Biohazard: Very helpful, thank you.

You are most welcome.

Biohazard said:

There is no need to replace the entire sysmain.sdb and fiddle with the ownership.
Doing that could cause a lot more issues down the road.

Disable entries that say "HARDBLOCK".


All done.

Thank you so much for this. it works like charm. A little advice when downloading the ADK, Only check the one you need and uncheck the rest, saves you a lot of time

Biohazard said:

There is no need to replace the entire sysmain.sdb and fiddle with the ownership.
Doing that could cause a lot more issues down the road.
Instead I suggest using the Compatibility Administrator tool.

Thanks Biohazzard - worked perfectly on a test VM I created.
Like somebody else said, uncheck all install options and only install the "Application Compatibility Tools"
Another thing I did which worked was rename the vmware.exe in C:\Program Files (x86)\VMware\VMware Workstation to vmware1.exe

muchomurka said:

tfwul: The sequence must be Ownership - Permissions - Rename, nothing else works.

I simply followed your steps and it worked out fine. VMware Workstation Pro v14.1.x was running without problems.
Compliments!
To avoid future problems I upgraded to 15.5 though

- - - Updated - - -

- - - Updated - - -

jimbo45 said:

AFAIK VMWare 14 doesn't work on latest (19.XX or 20.XX) releases of Windows --If it does could someone please post a screenshot. !!
Cheers
jimbo

Regretfully I can't provide you with a screenshot anymore as I just upgraded to 15.5 but I do confirm that, after following the steps of muchomurka, VMware Workstation Pro v14.1.x worked fine on Windows 10 x64 1903 (18362.388). At least with me. I don't know about v12.
Note: the VM's were also Windows 10 x64 1903 (18362.388).

FWIW...
(weird, I replied to two different posts and my replies are merged...)