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

Worked but will it continue to work is the question with the OP's original method of replacing the sysmain file?

Thanks @Biohazard that worked like a charm for Workstation 14.1.

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.

Hey Biohazard, I have a question. So I did the "replace the entire sysmain.sdb file" because that was the instructions posted before you wrote your post. However, before I did that, I made a backup of the original sysmain.sdb file before I replaced it with the one posted here. Should I then restore the original file? Or should I leave it the way it currently is?

Thanks!

- - - Updated - - -

Kari said:

Thinking this realistically, Microsoft cannot be held responsible for keeping all older software functional in Windows. That would be an impossible task.

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

Kari

Illogical. Obviously Microsoft can't be held responsible for keeping all older software functional in Windows, however, that doesn't mean Microsoft needs to block older software from running in Windows. If a user wants to try to run older software in Windows, then the user should have the right to do that. It's not Microsoft's place to tell me I can't even try to run older software myself.

Second of all, don't you think it's just a little suspicious that Microsoft only blocks enterprise software from being run if it's an outdated version? For example, I can run Lords of the Realm 2 (a video game from 1996) just fine, and that isn't blocked. Same with Sid Meier's Pirates, Stronghold 2, Airline Tycoon Deluxe, etc. You've got to admit, it's quite shady that the only software Microsoft blocks is enterprise software such as VMware Workstation. Sounds like collusion to get you to pay for an upgrade to the latest version of VMware Workstation, and if that's the case, then why are you defending them?!?

My understanding is "A Hard Block means that the program is known to be incompatible and running the program could result in severe system errors - such as causing a system crash or a no-boot scenario."

I believe there were quite a few advisories about guests being able to execute code on the hosts and 15.5 specifically "Implemented DLL loading security improvements"

According to VMware Knowledge Base only 15.5 is compatible with 1903

The issue is theres been no official statement by VMWare why anyone who has purchased previous versions no longer be allowed to run them on 1903.

"The approval to create hard blocks or soft blocks for a non-Microsoft program must come from that program's ISV "

I've just joined Ten Forums after finding this discussion on an issue that I've just started experiencing, and many thanks for the suggestions on it. More on that shortly. I started writing a series of connecting QBASIC programs back in the 90s and have been using VWMare Workstation Player 12 to run them via MS-DOS 6.22 and QBASIC 1.1. It has been an ongoing series of additions and modifications and isn't finished yet - and I certainly didn't want to lose it all! This problem under discussion arose after a recent Windows 10 update, as others have already found.

The 'quick and simple' fix relating to modifying the Windows registry looks interesting but I'm a bit confused about how to go about doing it. (I have edited the Visual Basic 6.0 'Recent Files' keys on occasions so I am no stranger to modifying keys).

Are those two lines to be added to the main AppCompatFlags key - and why is part of them in green? (I have noticed that there are a considerable number of subkeys associated with that main key on my system and I've checked them all but couldn't find any similar code to that specified). If so, I presume they will be added after the three items that I've found there - or are two of them to be amended? I obviously don't want to corrupt the registry, as my computer is otherwise performing very well at present. I am, by the way, running Windows 10 1903 18362-418 there have been two updates in the last few days).

Thank you for assistance with this.

John Marchington

Hi John,

The 'quick and simple' fix relating to modifying the Windows registry looks interesting but I'm a bit confused about how to go about doing it.

It is a simple Registry file (a text file with .reg extension). Save it to your desktop and double-click on it. (It modifies Registry database the same way as Compatibility Administrator program.) Or you can download and apply that ready-to-use vmw.reg file from the article.

Are those two lines to be added to the main AppCompatFlags key - and why is part of them in green?

Yes, they are; of course you can add them manually too. Coloured text is a "feature" of Code box regardless of its ability to analyze syntax used.

I obviously don't want to corrupt the registry

You can always remove these two values manually if you want. (But the setting itself remains active in Session Manager AppCompatCache, no idea how long.)

muchomurka said:

Hi John,



It is a simple Registry file (a text file with .reg extension). Save it to your desktop and double-click on it. (It modifies Registry database the same way as Compatibility Administrator program.) Or you can download and apply ready-to-use vmw.reg file from the article.



Yes, they are; of course you can add them manually too. Coloured text is a "feature" of Code box regardless of its ability to analyze syntax used.



You can always remove these two values manually if you want.

Thank you muchomurka for your quick reply. I shall try and it and report back.

Regards,
John Marchington

- - - Updated - - -

The registry amendment worked brilliantly and I now have VMWare Workstation 12 running again and all my programs are back. I can't really thank you enough for your suggestion. Never in a million years would I have known what to do to effect that solution.

You're most welcome, John.

"One guy tries to make something to keep another guy out; there must be a way to beat it!"
Richard P. Feynman

i followed all steps and wmware15 still woudnt start. i've changed the registry from 0 to 1 and worked like a charm