- I restarted server and ran Windows Updates
- 2023-05 Cumulative Update for Windows Server 2019 (KB5026362) appeared to install!
- It then started to install quite an old "Preview" update, 2022-02 Cumulative Update Preview for .NET Framework 3.5, 4.7.2 and 4.8 for Windows Server 2019(KB5011267). This stayed @ 20% for 30min. The CBS log showed no new entries.
- Restarted server. Could tell is was installing the 2023-05 Cumulative Update update on shutdown and start.
- 2023-05 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5026362)
Shows installed!
- Downloaded February 14, 2023-KB5022782 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows 10, version 1809 and Windows Server 2019 manually. This downloaded as windows10.0-kb5022511-x64. I figured the latest cumulative .NET update should catch me up. I should not need a preview from Feb 2022..
- The KB5022782/KB5022511 would just stay @ 20%. The last line in the CBS log again says
"ASSERT: Assertion failed in onecore\base\cbs\core\cbsexecutionitem.cpp(112)"
"Unable to match state from StateToAction table"
- Left this update run for around 15 min. After awhile the CBS.log did update the last modified time and appeared to still be doing things
- Let update continue to run. For another 10 min there was no disk activity nor was there any entries to the CBS.log
- Left update installing overnight. Will check on it in the AM
- Attached are the current CBS logs with updates running stuck @ 20%. Something with .NET seems to be causing these issues?
CBS Logs - CBS (8).zip
