Doesn't look like the problem is fixed yet.Updated to 19041.746 on Core 2 Duo test PC without issue.
sfc found/fixed corruption. dism AnalyzeComponentStore recommends cleanup to save 4GB.
Noticed dism version is now updated to 19041.746 from .572.
No Easter Eggs/Bugs found yet.
@kado897, @f14tomcat or anyone else who knows how to check Task Manager - Startup / C:\Windows\System32\WDI\LogFiles\StartupInfo, is the StartupInfo problem fixed / file updating with 20H2.746? Thanks
Ever since I downloaded the update, my CPU is up to 100 percent. My computer is about useless. Why is this happening for? Sometimes it goes down when I put task manager up, other times it says that system is hogging all of it.
It seems, for the moment, that everything is working.
The installation took time and stopping at 74% for a long time with no signs of life (if you can say so) of the hard drive, so much so that I feared the worst, but then everything went fine.
There were quite a few entries under Windows Logs/Setup for this one where Superseded KBs were being removed (KB4586781, 4552925, 4565627, 4562899, 4569745, 4570721, 4576428, 4576945, 4578968, 4580419, 4562830) before everything got rolling on the install of the MSR tool. Those KBs were mostly .NET updates from 2020 except two.
But everything went smoothly although it was slow at times on the desktop. Which isn't really uncommon.
Updated to 19041.746 on Core 2 Duo test PC without issue.
sfc found/fixed corruption. dism AnalyzeComponentStore recommends cleanup to save 4GB.
Noticed dism version is now updated to 19041.746 from .572.
No Easter Eggs/Bugs found yet.
@kado897, @f14tomcat or anyone else who knows how to check Task Manager - Startup / C:\Windows\System32\WDI\LogFiles\StartupInfo, is the StartupInfo problem fixed / file updating with 20H2.746? Thanks
The only thing I have that works right is Insider Dev @ 21286 (?). Insider Dev has work right for StartupInfo for months, and the fix has not trickled down. All my OS's are 20H2 or Higher.
One of my machines got this (0x800f0988) error via WU.
Manual download will not install too.
Thanks to you and sir @kado897 for checking. Hopefully M$$$ will eventually fix this in 20H2. Still works in 2004 - just for completeness.
ESENT 642 warnings in Event Viewer: They seem to have stopped on 19041.746. Are you still seeing them on 20H2.746 as one poster reported earlier? Thanks
UPDATE: I was mistaken - the 642 warnings have not stopped on 19041.746 : KB4598242 CU Windows 10 v2004 build 19041.746 and v20H2 19042.746
Last edited by steve108; 12 Jan 2021 at 21:07.
Yes, but I've never paid too much attention to them. Are they more of the MS foo-foo warnings?Thanks to you and sir @kado897 for checking. Hopefully M$$$ will eventually fix this in 20H2. Still works in 2004 - just for completeness.
ESENT 642 warnings in Event Viewer: They seem to have stopped on 10941.746. Are you still seeing them on 20H2.746 as one poster reported earlier? Thanks
Updated 3 computers. Two updated without problems. Had to do a repair installation on one.
Surprisingly (at least to me) a SFC /scannow found and fixed problems on 2 of the 3 after the update. One was the computer that I did a repair installation on. I had checked these computers before the update and there were not any problems.
Quote
