KB4571756 Cumulative Update Windows 10 v2004 build 19041.508 - Sept. 8 Win Update

IcarusLSC said:

I still can't get it to install.

sad. I wonder why...?
what are you using for anti-virus if other then the default M$ built in anti-virus?

magilla said:

Might try running again, being sure it is run in an elevated command (administrative) and see what happens. It takes several minutes to run. Also try running SFC /scannow also in elevated command (administrative) and see if anything is reported.
I would try restoring your backup next. It might then let you go on and try windows update again. Certainly you will not likely be worse off than now.

Thank you for your continuing help. I have previously tried SFC /scannow, without success, however I have just run both of your first two suggestions again. Here is the result:

DISM scannow by Philip Mock, on Flickr


When I ran a Command Prompt a couple of weeks ago in an attempt to install the cab file, I posted the result of the failure here - see #202:

KB4566782 Cumulative Update Windows 10 v2004 build 19041.450 - Aug. 11

You'll see that member Diceman2037 added this:

"Your system date is wrong, or you have a damaged root authority, run this in cmd prompt

certutil.exe -generateSSTFromWU roots.sst

then in powershell
$sstStore = ( Get-ChildItem -Path C:\ps\rootsupd\roots.sst )
$sstStore | Import-Certificate -CertStoreLocation Cert:\LocalMachine\Root

You can also use the STL in https://aka.ms/CTLDownload and certutil -addstore -f root authroot.stl"

It was at this point that I had to walk away from trying to update, as those instructions are a step too far for me to consider. I'm sure my lack of competence must be frustrating when giving advice.

To try and clarify my situation, perhaps I should say that I don’t want to update my computer, as it suits my use and needs as it is. I would prefer to leave my computer in its’ current state, as I don’t require any new features, and I loathe any sort of change to something that has taken me a long time to get accustomed to. I assume however that there are superior security features included with any new Quality or Features Updates - I still don’t understand the difference between the two types! Those apparent security features are the only reason for pursuing these updates.

It frustrates and disappoints me that a Windows 10 operating system requires me to elevate my P.C. skills to a level that should not be necessary to merely use a home computer. - That's my view anyway.

Pip

CountMike said:

Just noticed some problems after installation.
... In all browsers clicking on a .jpg and some other formats always asks what to open it with or to download it although old Windows Photo Viewer is specified as default.

Exit mbam and retry if this work properly.

magilla said:

So your results on DISM and SFC are great. If you don’t want updates, why not just stop receiving them ? You will get security and anti malware updates without being an insider.

Thank you for your response.

I have indeed come to that conclusion before - see #202 in the thread v2004 build 19041.450 - Aug. 11 linked below:

As I have highlighted, my only concern is that I will be ignoring any valuable new security features of each new build version, which is the only reason that I have pursued these updates.

KB4566782 Cumulative Update Windows 10 v2004 build 19041.450 - Aug. 11


Many thanks for your perseverance in this thread.

Pip.

downloaded and installed on my desktop
ran sfc /scannow and had a few corrupt files which were corrected
so no other problems

Yesterday's strange "update", quotes intentional: Having not updated Version 1909 for at least a few weeks, I decided to bypass the delay setting and see if there were any files to update. There were three, NET Framework, Malicious Software, and a KB Feature Update. I did not expect that latter file, but as Windows Update presented it, the three proceeded to download and install. When that was done, I restarted the computer, which I found shortly afterwards was already at the log-on screen. I said to myself that was too fast, and something must have failed. I returned to Update History in Settings, and found out what had failed to install and why it had failed: It was indeed the Feature Update, which was for Windows 10 2004! Rather strange that Windows Update presented and tried to install that on a computer using Windows 10 1909.