[SOLVED] Windows 10 - Updates since KB4512508 (Aug CU) end up with 0xe0000100

I'm not against patching the system and thus keeping it secure, don't get me wrong. My perseverance to get this issue addressed is a good proof.

What I'm against is Microsoft's messy and 'don't care' attitude to their patch releases. That is all.

Also, based on the above experience I daresay that there seems to be some serious flaw in Windows maintenance tools / worked out approach which even allows for the situation as mine to occur: Regardless of the source of this issue - and seemingly uncorrectable one, which normally necessitate in-place upgrade just to get repositories reset (sic!) - my OS remained stable and perfectly fine.

Another funny thing is that I moved to 1903 only on 13/07 and was actually quite happy with the whole process, as evidenced below:

How to get the Windows 10 May 2019 Update version 1903

Which literally must mean that the first update that got deployed on my PC (KB4505903) and/or subsequent component clean up broke it. How's that?

Also, I just checked the system image I made on 03/08 (I make them monthly) and this image exhibits the same problem. Which only further proves the above.

As I mentioned earlier Microsoft seems to be aware of this situation and the resolution is pending:

Windows 10, version 1903 and Windows Server, version 1903 - Windows Release Information

Lastly: I realised overnight that the fact that I deployed KB4512508 now does not mean that I will be able to to the same with KB4512941 as I might encounter further installation issues. I will therefore probably do this later today.
 
Just deployed it on my PC and without any issues. As I did not tweak registry to disallow Bing & Cortana, I probably will be fine.

Alas! I will refrain from creating system image now, and will defer any maintenance (component clean up) activities either.
 
Any more issues that the ones identified so far - as reported elsewhere?

Frankly, had none of it (I did not disable any of it: Bing or Cortana), but had not powered up my PC since last Sunday either.

Also, apart from System Restore checkpoint made prior to installing it, I had not run Component Clean Up afterwards this time, so can always uninstall it.
 
Well, I will, obviously - perhaps not on Tue though as I'm trying to avoid being a guinea pig.

And yes, should I experience more fun then (or earlier), I will get back to this thread with an update.
 
Quick follow-up here: Just decided to install Sep CU (KB4515384) despite seeing yet another carnage introduced by MS... The upside is that none of these so-called side-effects (I can see MS updated KB article with known issue as we speak) should impact me.

And: all is well so far, and although deployment took some time - as opposed to the swift installation witnessed by others - CU installed & system updated without issues.


1568454147841.png​

Casual post-deployment check confirms that all is well either:

Code: 
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.356

No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>sfc /verifyonly

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>

What I'm reluctant to do is:
  • Perform any component store clean up
  • Update system image (the latest one I have is a faulty one, created post 26/07, so after non-security CU installation that assumingly broke update processes and prior to me raising this issue here and resolving it). But I may do it quite soon assuming that all will be well
What I'm still really eager to know though is what exactly broke it. I trust Microsoft will advise on this one at some stage - updates failure issue is still under investigation.

Windows 10, version 1903 and Windows Server, version 1903 - Windows Release Information
 
True that - and with that in mind just decided to create (update) system image.
 
Just to put some final comments / thoughts here.

I did manage to get OS updates throughout Sep / Oct until now without any issues - installing required OS patches (updates) [First Tue] only and skipping optional ones [last Tue/Fri etc.].

I just deployed Nov patch (KB4524570) successfully:

KB4524570 CU Windows 10 v1903 build 18362.476 & v1909 build 18363.476

And with some hesitation just upgraded to 1909 successfully as well:

KB4524570 CU Windows 10 v1903 build 18362.476 & v1909 build 18363.476

All seems good and I will be performing the casual checks now.


Regarding reported issue with updates as indicated by Microsoft from around Aug '19:

Windows 10, version 1903 and Windows Server, version 1903 - Windows Release Information

They seem to be resolved on their own according to Microsoft:

Resolution: This issue has been resolved for most users. If you are still having issues, please see KB4528159.

Uhmm, I remain unconvinced as I've seen surge of people having to resort to in-place upgrade to get it fixed.


In either case: many thanks again for helping me to get this pickle sorted.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top