Windows 10 Cumulative Update KB4103721 Version 1803

Well it is wider spread than their updated kb suggests (i.e. they claim it is related to a couple models of Intel series SSD's) though I've seen this problem occur on spinning disks & my own day to day system has a Crucial SSD so it is clearly wider spread than a couple of Intel series SSD.

 I am saying of all the 1709's we successfully updated to 1803, not one had an issue until this patch came out. Many are finding reasons / work arounds however IMHO, the issue is that this patch introduced issues that did not occur 1803 straight up or anything running previously.

 So they should pull this until they identify what within this patch is causing so much grief for a VARIETY of cfg's & systems. I do not have ASC11, no Intel SSD no Syncovery or whatever & I am seeing this on a disproportion number of PCs & laptops having boot issues after this patch. Yes some are fine, good, but clearly something is causing this for so many systems.

 It clearly isn't related to one type of software or one type of SSD / vendor.

 IMHO until you (MS) "know", pull the f&*(^n thing out of circulation.

 Now some of us with Enterprise contracts & abilities to delay patches or omit them from release are not as bit as those that rely on MS to roll out stable updates.

 So we are affected but minimally as once we identified there was an issue we (in managed environments) could block this update post 1803 as we only have a small percentage running the 1803 as we trial it before we unleash it en mass.

 We have stopped because of this patch, now other issues may be preventing 1709 systems going to 1803, I have two of those also we're trying to ascertain why they won't go but that issue is not in line with this topic of why a running system on build 1803  breaks after this KB is installed.

 Morale of the story is this, already told  MS we're done with this nonsense, next stable LTSB build of Windows 10 (I hear delayed from fall 2018 to spring 2019 now) is we're moving ALL system to Windows 10 LTSB and future images, we are so done with this crap. I know MS is really trying to dissuade us ENT customers from going widespread LTSB but after this, no more nonsense, this is a huge time suck & $ cost to manage their mistake.

It does not help people solve the problems. I agree with you! But it may motivate the world company "MICROSOFT" in the future to work more carefully, the Windows users are not facing almost unsolvable problems. Microsoft should rather offer solutions and not rely on the few capable people in a community.

A public apology would be appropriate!

But then Microsoft would have to admit yes mistakes and that is definitely not!

Frank

Hello Poomba_1,

I don't believe I understood your reply, as you also did not specifiy in which part of my conclusion you disagree.

Let me again try to clarify :

In 16299.xxxx (Windows 10 1709) every next boot after having done an AMD driver update or having run "CCleaner" was fine.

Starting with 17134.1 (Windows 10 1803), every next boot after having done an AMD driver update or having run "CCleaner", and now after

attempting to install KB4103721, was resulting in a "black screen" (before logon) and the only way to solve/bypass was to boot to "safe mode" (necessary once after having done the AMD driver update or having run "CCleaner", necessary twice after KB4103721, which furtheron was leading to a rollback of KB4103721).

For MY particular situation I was able to find out, that disabling the "Syncovery VSS helper service" allowed any further boot (after above mentioned "maintenance tasks") to complete without any issue (as in 16299.xxxx).

So again, KB4103721 (the update from 17134.x to 17134.48) is NOT causing the problem, but at the end of the day suffering from an issue already introduced with 17134.1 (Windows 10 1803 final).

Of course I did never state, that every Windows 10 user will run in that problem, as obviously not every Windows 10 user is using "IoBit Advanced System Care" or "Syncovery" (known at the moment to cause the "black screen" situation) ... it is now up to Microsoft to find out, why those (or maybe other) products are causing (kind-of) compatibility issues in the Windows 1803 boot process.

I'm calling it good for now and not changing anything else until the dust settles on these issues.