As noted above, this seems to be suddenly working of its own accord now. Guess it was worth it to learn to debug at the ETL file level....
I'll close this as solved if it still works in a little while.
I noted KB5039212 simply because things were fine prior to installing this one update. I'd installed the preview of this update (KB5037853) at the end of May with no issues.
Hey there! A fellow Extra-class Ham! :waves:
I actually wonder if it's something on the server side for MS, as it's not...
I did a deep dive into the WU error with PerfView..... two things caught my eye in particular:
*FAILED* [80245006] SLS sync failed during service registration...
and
*FAILED* [80245006] Failed to execute service registration call...
though it appears that SLS sync is the main problem here.
Windows Update shows error 0x80245006 when checking for updates after installing latest KB5039212 updates successfully and rebooting.
Used FixWin 11.1 to run the (retired) Windows Update Troubleshooter which was not useful:
IsPostback_RC_PendingUpdates
IsPostback: False
WaaSMedicService
Issue...