VMware Communities
ntaylor0
Contributor
Contributor
Jump to solution

Latest Windows 10 update won't install over VMWare Workstation 12

When I try to install the latest Windows 10 updates I get a warning message for the Windows 10 updates installer:

"VMWare Workstation Pro

This app can't run because it causes security or performance issues in Windows. A new version may be available. Check with your software provider for an updated app that runs on this version of Windows."

Has anyone else encountered this and does anyone know if upgrading to the latest VMWare Workstation 15 will fix this issue?.

Thx

1 Solution

Accepted Solutions
RDPetruska
Leadership
Leadership
Jump to solution

Workstation version 12 is way past end of life, and not supported with the latest Windows 10 versions.

Workstation 15.x supports the latest Win 10 hosts.

However, Workstation 14 and newer require newer CPU hardware - so download and install/test the trial version before committing!

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

View solution in original post

0 Kudos
14 Replies
RDPetruska
Leadership
Leadership
Jump to solution

Workstation version 12 is way past end of life, and not supported with the latest Windows 10 versions.

Workstation 15.x supports the latest Win 10 hosts.

However, Workstation 14 and newer require newer CPU hardware - so download and install/test the trial version before committing!

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

0 Kudos
kbulgrien
Enthusiast
Enthusiast
Jump to solution

VMware Workstation Pro 14.1.7 build-12989993 also appears to be doing this.

0 Kudos
asajm
Expert
Expert
Jump to solution

Hi ntaylor0

Look

https://stackoverflow.com/questions/50374506/vmware-workstation-cannot-run-on-windows-10-after-recen...

If you think your queries have been answered
Marking this response as "Solution " or "Kudo"
ASAJM
0 Kudos
bikeman48
Contributor
Contributor
Jump to solution

I have the same problem with Workstation 14.

0 Kudos
ntaylor0
Contributor
Contributor
Jump to solution

Upgrading to Workstation 15 fixed the problem for me.

0 Kudos
bikeman48
Contributor
Contributor
Jump to solution

Upgrading to version 15 seems to have resolved the issue. Would be nice if VMware could have released a patch for my version 14 so I didn't have to buy an upgrade but you have to keep increasing sales, I guess. You think they are working with Microsoft to help each others software sales?

ntaylor0
Contributor
Contributor
Jump to solution

Agree totally. That's why I was on version 12 before I had this problem and was forced to upgrade. The upgrades are expensive if you're going to upgrade every time a new version comes out which is why I usually don't upgrade until forced to. The new features that VMWare add into each new version do little for me in the application our company uses.

0 Kudos
rolandats
Contributor
Contributor
Jump to solution

Hi to the community,

I think it is ludicrous to force people to upgrade from 14 pro to 15 pro. I bought my Licence for VMware Workstation 14 last year and I think that VMware shouldn't charge people for making their software compatible (to the exact User System) by buying the upgrade. I am quiet sure that this can't actually be legal forcing (because if we don't upgrade our OS will have security wholes because we can not update our OS) users to pay for this upgrade. Rather than doing this, VMware should release a patch to fix that.

It is a sad picture for a big company (and until now also an Company with a good reputation) like this to engage in such tactics.

I have been in this industry since the beginnings and spend over the time enough money on software (with the money I spend in the last 30 years just for my private consume on software one could buy a house) let alone the millions spent in the cooperate environment.

I have no problems paying for an upgrade on end of life circle (which should be after a new OS version)

Best regards!

rolandats

RDPetruska
Leadership
Leadership
Jump to solution

I have no problems paying for an upgrade on end of life circle (which should be after a new OS version)

The problem here is that the new Windows 10 *IS* a new OS version!  It just doesn't appear to users that it is.

And, Workstation 14 was EOL'd earlier this year, I believe.

0 Kudos
solanumnum
Contributor
Contributor
Jump to solution

I have upgraded to 15.0 -  but still I get the same error message.   I have also tried to disable all the VMware services running  (stop  and set to manuai)  - Not running when I'm trying to run Windows Update.   Any solutions to this ?

0 Kudos
solanumnum
Contributor
Contributor
Jump to solution

I found the reason -  it has to be upgraded to 15.1  or above - - a bug fix in 15.1.   Installed 15.5   and then I could proceed with Windows update 1903. 

0 Kudos
TheQuestion
Enthusiast
Enthusiast
Jump to solution

I think it is ludicrous to force people to upgrade from 14 pro to 15 pro. I bought my Licence for VMware Workstation 14 last year and I think that VMware shouldn't charge people for making their software compatible (to the exact User System) by buying the upgrade. I am quiet sure that this can't actually be legal forcing (because if we don't upgrade our OS will have security wholes because we can not update our OS) users to pay for this upgrade. Rather than doing this, VMware should release a patch to fix that.

And now for my rant. Yeah, understand that this is a VMWARE ISSUE NOT A MICROSOFT ISSUE!!! And what I mean by that is that there isn't anything wrong from the Windows end, but from the VMware end! VMware developers intentionally program this into all older versions of VMware in an attempt to force you to purchase another version of VMware!!! That kind of shady programming should be illegal! Fortunately, this can be bypassed using the Readiness Tool instructions in my previous post, but understand this will never be "patched" because the VMware developers intentionally put this into the code to begin with!!!​ So much for their "good" reputation, am I right? :smileyangry:

0 Kudos
waqasalisha
Contributor
Contributor
Jump to solution

if you are still stuck in this issue after latest windows updated in oct 2019 you can watch this video and solve your issue.

Solved Solutions from Tek Consultancy Technical youtube channel.

https://youtu.be/PZ47gQj450c

0 Kudos
Opie1
Contributor
Contributor
Jump to solution

To The Question-

Could you re-post the Readiness Tool instructions you referenced?

0 Kudos