Now Have Two KB4023057 Updates That Show "In Progress"

They are not the same update.
KB4023057 gets re-issued once or twice a year using the same KB number.
Your two entries are two different KB4023057s - their dates form part of their names as your diagram shows.
There is no fault in Windows.

My guess is that the newer one is actually altering the earlier one to tell it who's boss and that alteration is triggering the old one's In progress indicator.

All the best,
Denis

Glad to help.

I notice that your diagram is from NirSoft Windows Updates History Viewer.
Do you have an opinion about its relative usefulness compared to Control panel, Progs & features, View installed updates?
I use several other NirSoft tools but have never tried this one.


Thanks for the rep,
All the best,
Denis

Homer,

I think that NirSoft Windows Updates History Viewer has a problem working with KB4023057.

NirSoft Windows Updates History Viewer says that several KB4023057 are in progress ...

... but Event viewer tells me that the 27/01/2023 13:43:05 entry completed correctly, and

Event viewer only retains that one, none of the earlier ones.

... Control panel, Progs & features shows it by its installed names 'Microsoft update health tools' & 'Windows PC health check' with an installation date [which also implies completion].

KB4023057 does not produce an entry in the 'View installed updates' list.

So NirSoft Windows Updates History Viewer might provide a convenient display of updates but its data cannot be relied upon.


All the best,
Denis

Homer712 said:

Windows 10, 20H2 (OS Build 19042.928)

Homer,

Version 20H2 is no longer supported - Windows 10 Home, Pro EoS - MSDocs
Newly discovered security vulnerabilities will never get patched.
Only KB4023057, Defender & MSRT updates will continue [as shown in your diagram]. And the KB4023057 ones are in some doubt but they are useless anyway so they are not worth worrying about either way.

You ought to be able to update using the In-place update [aka Repair install] procedure - Repair Install - TenForumsTutorials
Make a new system image first - there is some guidance in my ditty - File backup vs imaging, imaging utilities, backing up drivers [post #3] - TenForums but do note that Macrium reflect is changing to offer only paid-for editions & free 30 day trials rather than permanently-free editions.

Or, since January's CU is listed in your diagram, perhaps it's just your TenForums system specs that haven't been changed yet.
At the top of the page, you can click on Quick links then Update system spec.


All the best,
Denis

I use several different Event viewer, Custom views to monitor updates.
I can certainly provide my view definitions along with instructions for importing them if you are interested.

I reported this thread's discoveries to NirSoft support.

Denis

Homer,

These are zipped copies of each of my Event viewer, Custom view definitions relating to Windows update.
WU - Setup log.zip {I always regard this one as being the main one}
WU - System log incl Apps.zip {Other records do not seem to include updates to Windows apps}
WU - downloads - Windows log.zip {I'd probably only use this in investigating a repeated WU install failure}
WD updates.zip {Defender definition updates. I cannot remember whether or not Defender platform updates get listed since the last one was in December & that has dropped out of Event viewer's mysterious time-frame for each log - but these platform updates do get listed in 'WU - downloads - Windows log' so we get two goes at investigating them.}

To import any Event viewer, Custom view from its [zipped] definition see Import Event viewer, Custom views - Power state transitions - my post #4 - TenForums


And do please bear in mind that the Event logs exist for Windows' benefit not ours.
- Event log entries might be recorded merely as triggers for other Windows processes to refer to and successful completion of those other processes might well not be reflected in an Event log entry that can be recognised as being related to the first [trigger] entry.
The existence of an entry in an Event log is not really a sufficient indicator that there is a problem worth using your time & effort to investigate.
Conversely, if you are investigating a problem for which there are fault symptoms, Event logs can provide data that might be helpful.


I have already found myself referring to NirSoft Windows Updates History Viewer because its Quick filter facility is a lot easier than messing around within Event viewer. So I'll keep hold of it & will experiment with it.


Best of luck,
Denis