Cumulative Update KB4517211 Windows 10 v1903 build 18362.387 Sept. 26 Win Update

Faith said:

Is this the 'last' cumulative update until 1909 comes out? I have heard a rumor that it comes out on October 3rd. If so I will just wait until patch tuesday, or if the rumor is true, October 3rd.

1903/1909 get the same patch files. Only a tiny enablement package turns on the 1909 bits in the OS.

bosman said:

KB4517211 stops VMWare 12 and 14 from starting at all - Get "please check for updated version"
Older CPU's couldn't upgrade beyond VMWare 12 which wasn't an issue for me.

same here.. i was using vmware player 12.0 and after .387 update it won't start
updated to vmware workstation player 15.5 and now it works again

question is: WHY?

ninja750 said:

same here.. i was using vmware player 12.0 and after .387 update it won't start
updated to vmware workstation player 15.5 and now it works again

question is: WHY?

Hi there
VMWare had several issues with the earlier 19H1 and 1903 Windows builds - but everything seems to be fixed now - so earlier releases of VMWare software can't be expected to work on current Windows builds. Actually rel 15.5 also works on the skip ahead builds too.

The latest updates to Windows etc have more security etc built into the windows kernel plus a load of other changes at system level which makes running specialised programs like VMWare much more problematical unless you use the latest compatible version.

Older software of this type is highly unlikely to continue working --just look at problems such as Anti Virus software from 3rd party suppliers or even simple hardware drivers get at times with a new Windows build. --

Simple bog standard application type programs which don't make specialised requests to the OS should continue to run for a while yet though so not everything needs to be updated.

Workstation version 12 was the last version that runs on 32 bit software so if you are using that release it most certainly won't even "think of working" on current Windows releases especially if (as I think 99% of Windows 10 users on 1903 releases are running on 64 bit hardware). Not all 32 bit software will work reliably on current W10 x-64 bit releases.

As for V14 I think I've answered your question.

Cheers
jimbo

jimbo45 said:

Workstation version 12 was the last version that runs on 32 bit software

VMWare 12 was the last version that supported older CPU's and hence why allot of people still using it due to CPU age. Upgrading VMWare isn't an option for me and others with older CPU's.
Upgrading hardware looks like the only option..

bosman said:

VMWare 12 was the last version that supported older CPU's and hence why allot of people still using it due to CPU age. Upgrading VMWare isn't an option for me and others with older CPU's.
Upgrading hardware looks like the only option..

Hi there
@bosman

I understand that --and it's fine if you've got older hardware -- but remember older hardware won't always support newer windows releases either so sooner or later you might have to "bite the bullet" and upgrade.

My remarks were actually attempting to give an answer to a previous poster's question ( I think it was ninja750) as to why VMWare rel 14 failed to work recently after some W10 updates.

Cheers
jimbo

jimbo45 said:

As for V14 I think I've answered your question.

Cheers
jimbo

jimbo, I fully understand what your thoughts are and it would have sense if VMWP stopped working upgrading from 1809 to 1903, but not after a minor build upgrade since nothing is clearly written in the microsoft changelog (https://support.microsoft.com/it-it/...date-kb4517211) so again MS have done changes in the o.s. without specify them

in a normal world, if windows installs .387 build and I found that VMW12 does not work anymore, I should go to the windows update page (link above) and read what is going on regarding the issue, then ok, upgrade to 15.5

in this world, I have customers angry on the other side of the telephone and I have to google as fast as I can searching why that program does not work anymore. worst thing is that first pages of google's results are not linking microsoft sites, but tenforums etc..

my opinion.

ninja750 said:

jimbo, I fully understand what your thoughts are and it would have sense if VMWP stopped working upgrading from 1809 to 1903, but not after a minor build upgrade since nothing is clearly written in the microsoft changelog (https://support.microsoft.com/it-it/...date-kb4517211) so again MS have done changes in the o.s. without specify them

in a normal world, if windows installs .387 build and I found that VMW12 does not work anymore, I should go to the windows update page (link above) and read what is going on regarding the issue, then ok, upgrade to 15.5

in this world, I have customers angry on the other side of the telephone and I have to google as fast as I can searching why that program does not work anymore. worst thing is that first pages of google's results are not linking microsoft sites, but tenforums etc..

my opinion.

Hi there

@ninja750

"Please don't shoot the messenger ..."

I was only trying to answer your query.

I can't be held responsible as to how Ms or VMWare run their businesses or attempt to tell them what they should do.

Of course if you have customers responsible to you when things don't go the way they should then yes it's not always the best -- however as a suggestion - probably --especially if dealing with external (or even internal) users it's probably best to install an update on a test machine and if it doesn't work then inhibit a roll out to users if possible.

What you should always do (IMO) though is get a proper system of image backups taken.

So get customers to install and use say Macrium Free which is FREE software and it works brilliantly and simply so if an update fails just revert back from a previous backup.

Probably not so easy in the real world but should be "do-able" for quite a few customers -- would save them and you a lot of time and aggro. !!!

Cheers
jimbo