New
#20
Updated.
+Net. framework 6.0.11 on 1 computer.
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.
Last edited by Anak; 09 Nov 2022 at 17:49.
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.
Last edited by smalltown; 10 Nov 2022 at 07:10. Reason: System now acting normal
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.
I have also been getting that MDM error since the November update. It is logged roughly 15-20 minutes after the computer is rebooted. It is on Win10 Home, 22H2, Build 19045.2251.
I posted about it on another forum, and there is one possible solution. Basically, MDM is something to do in an Enterprise setup, not home.
[WIN10] Event 2545 errors since November updates - Microsoft | DSLReports Forums