Cumulative Update KB4497093 for Windows 10 Insider 1903 build 18362.86 Insider

I am on the RP and WU gave me CU KB4497093. The servicing stack update (SSU) - KB4498524 shows in Installed Updates but not in WU history. Seen this before on other updates that required a new SSU before installing. All is well.

jimbo45 said:

this build does look really good but there are zillions of people who use VMWare for running VM's /servers etc -- so the issue isn't a "Mickey Mouse " one.

yeah, but 1903 is not GA, either. I got hit with the VMware Workstation black VMs issue, but it's my fault for installing an OS update that technically hasn't been declared final yet.

kjlkjadfasdfasd said:

yeah, but 1903 is not GA, either. I got hit with the VMware Workstation black VMs issue, but it's my fault for installing an OS update that technically hasn't been declared final yet.

Hi there.

Doesn't therefore seem sensible to KEEP pushing out windows releases that ignore a major product that loads of "serious" users are using daily for all sorts of things. OK I know it's not a "Final release" so VMware doesn't have to be at fault until the planning for Windows final releases becomes known. That said though it's obviously a major problem which I really hope the people at VMWare internals are working on together with Ms.

If you just want people to browse a couple of websites, try a few EXCEL spreadsheets or send an email or two -- then you don't really need a slew of updates or any sort of robust testing methodology.

Surely the whole point in having these rings is just that -- usually the more experienced people are on them doing all sorts of things which should decently test stress the OS -- if you've got a major product out there which has been failing for a long time then how in the world can this release be even thinking about RP or RTM. Not only that - Ms could easily clearly state in the release notes that this is a known defect -- and either VMWare will fix it or they will wait until Ms has released the next Windows as an official general release.

I don't want to keep installing these releases and then see the same defect hasn't been fixed or even commented on.

I'm sure we all understand that using these types of releases are prone to bugs etc - that's why they are sent out for test and we (should) accept that or don't use them -- but just to ignore major known defects for several of these releases - including the 20H1 cycles as well seems to me just plain BONKERS.

Cheers
jimbo

jimbo45 said:

Hi there.
I'm sure we all understand that using these types of releases are prone to bugs etc - that's why they are sent out for test and we (should) accept that or don't use them -- but just to ignore major known defects for several of these releases - including the 20H1 cycles as well seems to me just plain BONKERS.

If they are aware of it I am sure they are trying to work on a fix, sometimes a fix can be quite complicated and takes some time before it's ready to be released. Should they halt all releases until every known bug is fixed? People here would be quite upset if they didn't get a new build for months.