KB5019959 Windows 10 19042.2251, 19043.2251, 19044.2251, 19045.2251 Win Update

Sys#2 and the ol' gateway dsktp updated on their own ovrnite, sys#1 took 45minutes. I had all but the bottom one in @Brink 's first post, all 3 are now:



Had a curious event with sys1.
All three run f.lux . Sys1 finished and when it got back to the dsktp I was presented with a red screen similar to the night effect on a planetarium program.
I checked in display but no luck, then checked f.lux and here the setting went to ember:1200K, a deep red. Moved the setting back to a comfortable setting and the display has been okay ever since. I imagine there's a 1st time for anything.

Updated to 22H2 version 19045.2251 no problems.
SFC ran clean.
DISM seemed odd only runs for about 2 seconds and reports no component store corruption detected.

P.S. This morning I noticed KB502694 was waiting. After installing and reboot everything is working as it should.
Not sure if this KB did anything to cure my DISM running oddly or simply another boot, but my DISM now runs as it should.

DISM causes a blue screen after restarting. Before restarting everything runs fine even created an Macrium image but it blue screened too. Had to restore a backup from October.

I just did a repair installation, tweaked some default settings and did another image backup. I am afraid to run an DISM even though a quick image restore will fix it.

reddice said:

DISM causes a blue screen after restarting. Before restarting everything runs fine even created an Macrium image but it blue screened too. Had to restore a backup from October.

I just did a repair installation, tweaked some default settings and did another image backup. I am afraid to run an DISM even though a quick image restore will fix it.

If you did an In-Place upgrade (repair install), you should be able to run DISM with no problems.

Ghot said:

If you did an In-Place upgrade (repair install), you should be able to run DISM with no problems.

Does not matter. I will never run that useless DISM again. I stopped running sfc/scannow because it was useless in fixing problems. So, I gain a couple of GB running DISM. I have a 1TB SSD and I have all my games on my 1TB SSD D drive.

reddice said:

Does not matter. I will never run that useless DISM again. I stopped running sfc/scannow because it was useless in fixing problems. So, I gain a couple of GB running DISM. I have a 1TB SSD and I have all my games on my 1TB SSD D drive.

That's your choice obviously. But as I said, an In-Place upgrade should fix any problems with DISM.
It should fix any Windows problems.