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

Updated the other day without issue, but have been too busy to post -- or visit -- here at TF. This one went up without a hitch.
--Ed--

pipmeister said:

I've tried Shawn’s bat Update Reset, I've tried installing the standalone MSU file, I've tried CAB file using cmd prompt, I've tried Disc Clean-up / Restore Health, and Microsoft Troubleshoot on each of the .388, .423, .450 & now .508.

Pip

looks like you’ve done Just about everything outside of a clean install——which I hate to do Personally because of all the programs I have to install. When you run DISM, you don’t get any corrupt file messages?

magilla said:

looks like you’ve done Just about everything outside of a clean install——which I hate to do Personally because of all the programs I have to install.

Or a repair install.

pipmeister said:

Which brings me back to the advice that I have received regarding each of these versions that have failed to install, and sadly highlighting my trepidation that I posted previously, and also #65 on this thread.

Pip

I understand you reluctance it is a big step to take.

pipmeister said:

Which brings me back to the advice that I have received regarding each of these versions that have failed to install, and sadly highlighting my trepidation that I posted previously, and also #65 on this thread.

Pip

- - - Updated - - -


I sorry, but I don't know what that means.

Pip

In frame 81, you mention ‘restore health’ so I thought you had used DISM /online /cleanup-image /restorehealth So what did you do to cleanup image and restore health?

pipmeister said:

I apologise for not being familiar with the terminology, but you are correct that I did indeed copy and paste DISM.exe /Online /Cleanup-image /Restorehealth into Command Prompt after reading about it following a Google search. I was merely quoting from a previous post, where I hadn't used the term DISM. I don't recall seeing any corrupt file messages.

Pip

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.