Cumulative Update KB4512508 Windows 10 v1903 build 18362.295 - Aug. 13 Win Update

citrixscu · 21 Aug 2019

BrokenDaily said:

I was scrolling around in twitter to a few channels I was following, and I see this notice that some users that updated to this new CU for windows 10 1903 are experiencing random restarts. I saw through this article that also links to other forums having others experiencing this, and I would like to know before updating to 1903 if anyone else can confirm they're having this problem as well

I usually use NTLite to integrate the CU updates and other updates I need to my Win10 ISO file I download ONLY in the case of a version number jump (1709 to 1803, or 1803 to 1809 and so on), but if this is real, im not installing this until it gets fixed. I already had to reinstall my OS after I foolishly erased it with the wrong cmd command in with a win 10 install disk

Interesting to come across this. I was on x.10012 and began experiencing random hard reboots -- i.e. the PSU clicked and rebooted the system: no BSOD, no hard locks, etc. The only thing in Event Viewer was a Critical Kernel Power Error 41 with bugcheck codes 0x0.

The situation was random but I could reproduce it with some consistency by attempting to encrypt an external HDD with bit locker. The system would reboot nearly immediately or after some time ~30min. I could stress test the CPU and GPU for hours with prime95 and furmark and couldn't get the pc to crash.

Puzzled, I tore the computer apart, reseated all cables, got a new PSU, swapped everything I could and still had reboots. I ultimately ended up fresh installing from MCT and have not had an incident yet, but it's only been a couple of days.

ThrashZone · 23 Aug 2019

Brink said:

UPDATE: Cumulative Update KB4512941 Windows 10 v1903 Release Preview build 18362.325 - Aug. 21

Hi,
Release preview wth

Windowz10 · 23 Aug 2019

Is there an existing thread somewhere here, where users have discussed issues when this KB installation fails?

I see from various internet search hits, that there are such cases, and unfortunately for me for the first time ever on Windows 10 I am having a problem installing the Monthly update. Basically it seems to get to Installing 100% and then after some seconds of waiting, the message comes that the installation failed and to try again later. This seems to be similar to other hits in various web forums. (Rebooting, disabling antivirus and such doesn't help).

Hoping there is a specific thread in 10 Forums, since typically the information here is accurate.

slicendice · 24 Aug 2019

@Windowz10 Try this:

!NOTE! Save all your work before continuing forward !NOTE!

Open Elevated Command Prompt (Open as Administrator)
Run
DISM.exe /Online /Cleanup-image /Restorehealth
(this will fix your system image health)
Run
sfc /scannow
(this will fix any system file cache corruptions)
Run
net stop wuauserv
(this will stop the Windows update service)
Run
del /q "C:\Windows\SoftwareDistribution\Download\*"
(these are files used by WU and can be safely deleted)
Run
FOR /D %p IN ("C:\Windows\SoftwareDistribution\Download\*.*") DO rmdir "%p" /s /q
(same as previous step)
Run
shutdown /r /t 0
(this will reboot your system without delay)
After reboot Disable any AV real time scan temporarily (eliminating anything that can interfere with WU and corrupt files in the process)
Check for updates again

Hope this helps. If not, then there might be some incompatibility issues with this update and your system hardware and software configuration or there are corruptions in your system that are beyond repair. Only sensible thing you can do in this case is to wait for next update and hope MS fixed the issue somehow.

EDIT: Sorry for the messy edits. (There seems to be some issues with code blocks at this site at the moment that renders the text unusable)

krzemien · 24 Aug 2019

Windowz10 said:

Is there an existing thread somewhere here, where users have discussed issues when this KB installation fails?

No, but equally: it's acknowledged by Microsoft problem and if I were you I would await for an updated / next CU that resolves this.

Pejole2165 · 24 Aug 2019

You could try using the MMCT to download latest ISO with CU rolled in and perform a repair (in place) upgrade. This sorted the issue for me (can install and keep existing files and apps) and also cleared up a few other issues, but it is a Sledgehammer approach (full clean install being the NUKE option).
As always make a complete backup of personal files / apps etc and best to use Macrium Free to image your disk first and create a Macrium boot disk.
I would strongly advise following the above post first using DISM to repair any issues and then if you are not comfortable with the in place upgrade route just wait for MS to fix the patch.

krzemien · 24 Aug 2019

Could somebody tell me: what's so important in that CU that everybody seems to want to go to such great lengths (and at the same time fix deployment acknowledged issue created by Microsoft themselves) and spend a day or so reinstalling Windows? Is it really worth it?

Or it's an art for an art's sake only?

Genuinely interested.

Pejole2165 · 24 Aug 2019

For me it is a case of "this thing should work, why doesn't it, lets try this", I'm a persistent tinkerer....for others it may be they are genuinely concerned about the security fixes of these Cu's, others may just be asking "why doesn't this work, is it an issue?"
People are all different.

slicendice · 24 Aug 2019

krzemien said:

Could somebody tell me: what's so important in that CU that everybody seems to want to go to such great lengths (and at the same time fix deployment acknowledged issue created by Microsoft themselves) and spend a day or so reinstalling Windows? Is it really worth it?

Or it's an art for an art's sake only?

Genuinely interested.

There isn't really anything that exciting. But if an update fails, it may be caused by corrupt system files. This is however not always the case. I suggest doing the above steps when having issues, to eliminate as many variables as possible. If that does not help and the same issue persist from update to update, then it may be time to clean install or do an in place upgrade/repair.

krzemien · 24 Aug 2019

slicendice said:

But if an update fails, it may be caused by corrupt system files. This is however not always the case. I suggest doing the above steps when having issues, to eliminate as many variables as possible.

True, but you do understand that this issue is of Microsoft's own making?

https://docs.microsoft.com/en-us/win...903#634msgdesc

So really spending one's time fiddling for hours with OS rather than doing something else and more productive is not the best idea. Just my view, of course.

I am also tinker myself - hence me contributing here for example - but equally: I find the whole idea 'let's just reinstall' unpalatable and synonymous with bored and unimaginative bods from corporate IT Support.

Things do not break on their own - and if they do break because of incompetence of others, that does not mean that one needs to start from scratch.