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

slicendice · 25 Aug 2019

ddelo said:

Sorry to say that, but that's the main Marketing idea:
EoL the old CPU, so they (the "suckers") will buy a new PC, with a modern CPU, new video card, new WiFi, new audio chip, so everybody will make money out of it (the OEM, intel/amd, nVidia, Realtek, Broadcom etc.), plus we (Microsoft) will sell a new Windows license, since the last one, as OEM, was only valid for the old PC and is not usable anymore!!

Heheh, that might be a shot in their own foot. Linux is on the rise and runs on pretty much anything. But I doubt this is what MS is doing on purpose.

EDIT: Just as an example arm64 version of Windows 10 runs very well on a Raspberry Pi3. Only the storage is a bit slow because of SD-card speeds and graphics acceleration is non existant. Other than that it performs acceptably well.

Pejole2165 · 25 Aug 2019

Unfortunately for Linux, Windows and Intel and Broadcom / Realtek etc are not just in the home, they all have a big presence in industry and business...and yes I know a lot of ISP's, Backbones, business servers etc have a Linux core but it is not mainstream.
Apart from the above and other niche uses it is only really supported in general use by a handful of enthusiasts and ship jumpers.
I'm not knocking Linux, far from it, I use it, but only as a secondary system.
It really is a shame that more people don't give it a go, the last real push into the market I think was RedHat, but you hardly ever hear of it now.
As to MS (and other software developers) and the hardware vendors conspiring to advance technology, well of course they do, that is their purpose (other than making money), and they should be doing so otherwise we would still be in the age of green CRT's and 640k RAM being more than anyone could need.
All this just my humble opinions...not meant to inflame anyone.

ThrashZone · 25 Aug 2019

Hi,
Yeah lord forbid ms simply not activating said incompatible features

Scottyboy99 · 30 Aug 2019

Looks like a new CU is out, KB4512941

Ita1 · 30 Aug 2019

Scottyboy99 said:

Looks like a new CU is out, KB4512941

right, same here (ITA)

Farvatten · 30 Aug 2019

Scottyboy99 said:

Looks like a new CU is out, KB4512941

Thanks for the early warning!.. ;o)

Brink · 30 Aug 2019

Update: Cumulative Update KB4512941 Windows 10 v1903 build 18362.329 - Aug. 30

Windowz10 · 09 Sep 2019

Now trying Slicendice's suggested steps of 2 weeks ago. Had decided to wait and try every few days to see if the problem self-corrected, or if a further release/update from Microsoft permitted things to go through properly. Now there are several updates from Microsoft failing, so trying Slicendice's steps.

Again, should be noted that in 2 years have never had any problems with updates. Always keep my system updated, including MS, Drivers and standard apps. Nothing weird added. Will report back when all steps completed.

- - - Updated - - -

slicendice said:

@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 wuaserv
(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)

Any guesstimate on how long the second step [DISM.exe /Online /Cleanup-image /Restorehealth should take?

I am watching the processes active in Task Manager, and not much is active. Even disk activity is less than 1% consistently.

Thus it *seems* like the DISM command isn't doing anything, just sitting idle.

slicendice · 10 Sep 2019

Step 2 can take a very long time. If it fails, skip to step 3, then step 2 and finally step 3 again.

EDIT: You might want to disable AV real time scan first. It may be interfering with the scans. @Windowz10

Windowz10 · 12 Sep 2019

Yes, it was indeed that step #2 took a long time. I wasn't thinking back to my DOS days, and didn't know that the command would create an actual log of things it was doing. So all the "output" happening was going right to the log file and the app didn't seem to be running. Once I saw that log, and the time stamps of the entries, I realized that (as you pointed out), it was taking quite a long time. I then redid that command and left it for many hours. It eventually completed. Took a gamble and then just rebooted and from then on the updates worked properly.

Note: There is a typo for step #3: wuaserv --> wuauserv

Thanks so much for your help!!