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

@krzemien

This issue may or may not be MS fault. Most issues I've had, has been because of bad drivers, buggy or old UEFI and 3rd-party software interference, not because MS has been writing bad code. MS has however fixed many of these issues by taking a different route around the problem.

I never said that reinstalling is THE solution for everything. It's only a last resort when everything else fail.

Sure, there's always a reason why something break. But we can't be blaming MS for these issues until we can prove the root cause and point fingers at the exact bits causing the issue.

Plugging security holes created by others is a tricky and tough business.

I never suggest a re install as a default go to, it is time consuming and in probably 99% of cases (completely made up statistic) unnecessary. I would always suggest using DISM and SFC to check if maybe there is file corruption / missing files which can be repaired quite easily. Sometimes naughty app installers change files settings they should not and this can cause other issues later on.
An in place upgrade with the latest ISO is not a re install and does not take long (even on my i5 system with a mechanical HDD), and "can" clear up issues that stop Cu's and other updates from installing.
Of course it could be an issue with the CU or update itself and in these cases it is wise to wait for MS to correct the issue, but at times even MS get things wrong such as the RST issue recently, MS told people to upgrade the RST drivers to install Windows feature update, unfortunately the RST upgrade did not replace the one file causing the issue, it was a keen eyed fiddler that spotted the issue and the correct work around and posted the fix on a forum.
As I said in my post to the OP, try the DISM route first and if not comfortable with using any other method, wait for MS to fix it.

@Pejole2165

Yes, waiting for MS to fix an issue is fine and perfectly valid, but you asked why people are interested in trying to fix the issues themselves and called into question some of the advice posted.
If you don't want to follow the methods suggested here, that is fine, but as I said a repair install worked for me, so yes it may be an MS problem, but obviously it doesn't affect all systems and if like most people on this forum you are an insatiable fiddler then there are methods you can use to sort the issue yourself.
Since the method I used worked for me it is perfectly valid to suggest it as a fix....note the SUGGEST part.

I think you'll find those files were not corrupt, the issue I think is that the files are not verified and that is what throws up the error. if we are talking the same issue.