KB4556799 CU Win 10 v1903 build 18362.836 and v1909 build 18363.836 Win Update

sgage said:

Is it reasonable to expect the average Windows user to go through this incantation at every update? It is really unbelievable the rigmarole users are expected to go through just to keep an OS operating smoothly. Why can't it just work? There should not be ragged edges and loose ends after every update - Microsoft has trained people to put up with this nonsense. It makes it quite difficult to have great faith in the integrity of the rest of the system...

No one is obliged to run those command-lines right after a CU, but if you want to save some space, it is worth the trouble. Like in my case, after running "dism.exe /Online /Cleanup-Image /AnalyzeComponentStore", it is shown that I could save 5.29GB of space by running "dism.exe /Online /Cleanup-Image /StartComponentCleanup", which I did and it has been successful.

Now, keeping up with my promise in post #20, Here are the screenshots for Update History on both machines:
-Non-production machine:


-Production machine:


But in both cases (both machines) if I click on Uninstall updates, I will see that the update (KB4556799) has been installed in Control Panel

As @ddelo pointed out, it is just a minor hiccup and I am not going to allow myself not to sleep over this trivial hitch. As we all now the big Feature Update 2004 is just around the corner. I presume everything should be back in proper order after its release and has been installed on both of my machines.

- - - Updated - - -

ddelo said:

I agree 100%.
I should note, that the same result from the last two commands
dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
dism.exe /Online /Cleanup-Image /StartComponentCleanup
can also be achieved by running the Clear Temporary files in Settings ( Settings > System > Storage > Temporary files ) and selecting "Windows Update cleanup"

What can I say?. You are correct again.

Well One Freeze up on I7 Desktop for some reason while downloading the updates, after a hard shutdown, due to Explorer totally crashing, re ran Windows Updates, and it went thru fine after that.

Gonna shortly run sfc /scannow and those commands, then think should be fine

Winver shows 18363.836

Two done, no problems.

Regarding my posts #20, #32, I think the problem about my empty Update History on production machine had to do with my Disk Cleanup advanced options where in some recent past I had basically checked everything and forgot to uncheck some of them, namely: Update Package backup files, Windows Upgrade log files etc..

I have just put things more or less back to the way they used to be and I will see in the forthcoming days if things are back to normal in Update history. Definitely probably my bad, and not MS.

sgage said:

Is it reasonable to expect the average Windows user to go through this incantation at every update? It is really unbelievable the rigmarole users are expected to go through just to keep an OS operating smoothly. Why can't it just work? There should not be ragged edges and loose ends after every update - Microsoft has trained people to put up with this nonsense. It makes it quite difficult to have great faith in the integrity of the rest of the system...

I use Dism++ to do all my cleanings. Nice GUI and no need to type down a lot of lenghty commands.