This took quite some time to complete. Attached is a link for the Fixlog.
Appreciate your help!
Fixlog.txt
Appreciate your help!
Fixlog.txt
[SOLVED] All Windows Updates Failing on Server 2019
- Thread starter bkosty
- Start date
- 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
- 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
Hi,
Yes, there is another issue with an older .NET update.
1. Start the
Command Prompt as administrator.
2.Right-click on the file
FRST.exe and choose Run as administrator.
Yes, there is another issue with an older .NET update.
1. Start the
- Open the startmenu and type the command cmd.
- After you find the Command Prompt, right click on it and select Run as Administrator.
- Copy and paste the following into the Command Prompt and press enter.
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS- Copy and paste the following (code) into the Search box and click the Search Registry button.
Code:
KB5004335- When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
- Post the logfile SearchReg.txt as attachment in your next reply.
Start the
Farbar Recovery Scan Tool again.
Warning: This script was written specifically for this system. Do not run this script on another system.
Warning: This script was written specifically for this system. Do not run this script on another system.
- Download the attachment fixlist.txt and save it to your desktop.
- Right-click on FRST.exe and select "Run as administrator".
- Press the Fix button.
- If for some reason the tool needs a restart, please make sure you let the system restart normally.
- When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
- Post the logfile Fixlog.txt as attachment in your next reply.
Hi,
Please reboot the server and attempt to install the .NET update and let me know the result. If it fails attach a new copy of the CBS logs.
Please reboot the server and attempt to install the .NET update and let me know the result. If it fails attach a new copy of the CBS logs.
- Restarted server
- Ran update KB5022782/KB5022511 manually
- Update started. Stops @ 20% again. The last entry in the CBS log is the same as before
2023-06-03 09:34:48, Info CBS Unexpected: Source State: Uninstall Pending, Target State: Absent
2023-06-03 09:34:48, Info CBS ASSERT: Assertion failed in onecore\base\cbs\core\cbsexecutionitem.cpp(112)
Unable to match state from StateToAction table
- Left update for 10 min and there are no new entries in the CBS logs.
- Pulled CBS logs while stuck @ 20%
CBS Logs - CBS.zip
- Ran update KB5022782/KB5022511 manually
- Update started. Stops @ 20% again. The last entry in the CBS log is the same as before
2023-06-03 09:34:48, Info CBS Unexpected: Source State: Uninstall Pending, Target State: Absent
2023-06-03 09:34:48, Info CBS ASSERT: Assertion failed in onecore\base\cbs\core\cbsexecutionitem.cpp(112)
Unable to match state from StateToAction table
- Left update for 10 min and there are no new entries in the CBS logs.
- Pulled CBS logs while stuck @ 20%
CBS Logs - CBS.zip
Last edited:
My fault! At around 14 min the CBS logs had more written to it. It seems to be what happened before when trying, post 22 above. I would guess it just stays here now. I will update if anything changes.
Below are the current CBS logs
CBS Logs - CBS (2).zip
Below are the current CBS logs
CBS Logs - CBS (2).zip
The last issue has to due with an .NET Framework update, please run the following steps first and please don't try to install other updates.
Download the
Microsoft .NET Framework Repair tool and save it to your Desktop.
Download the
- Right-click on NetFxRepairTool.exe and select Run as Administrator.
- Agree with the license terms "I have read and accept the license terms" and click Next.
- After checking, the tool will indicate which problems need to be fixed.
- Click on Next to continue, when this process is finished click Next.
- The tool will now collect the log files... > when completed the following file is created: FixDotNet****.cab.
- Click on Finish to close the tool.
- Right-click on the file FixDotNet****.cab and choose Send to > Compressed (zipped) folder.
- Attach the ZIP file in your next reply.
Hey Maxstar,
I do not see .CAB file generated.
The tool showed these paths on the last page. I copied the "dd_NetFxRepairTool_decompression_log.txt" and "cbs\cbs.log" to the folders as the others and zipped them up. Attached is ".NET Logs.zip"
I do not see .CAB file generated.
The tool showed these paths on the last page. I copied the "dd_NetFxRepairTool_decompression_log.txt" and "cbs\cbs.log" to the folders as the others and zipped them up. Attached is ".NET Logs.zip"
Code:
C:\Windows\windowsupdate.log
C:\Windows\logs\cbs\cbs.log
C:\Users\itptest\AppData\Local\Temp\1\FixDotNet.log
C:\Users\itptest\AppData\Local\Temp\1\NetFxSetupEvents.txt
C:\Users\itptest\AppData\Local\Temp\1\Microsoft .NET Framework Repair Tool Legacy_20230603_101716088.html
C:\Users\itptest\AppData\Local\Temp\1\Microsoft .NET Framework Repair Tool_20230603_101713682.html
C:\Users\itptest\AppData\Local\Temp\dd_NetFxRepairTool_decompression_log.txt
C:\Users\itptest\AppData\Local\Temp\1\FixDotNet_HKCR_Installer.regdump
C:\Users\itptest\AppData\Local\Temp\1\FixDotNet_HKLM_Installer.regdumpStep 1. Follow these instructions to remove an update.
Step 2. Follow these instructions to perform a regsearch with FRST.
Right-click on the file
FRST.exe and choose Run as administrator.
- Open the Start menu of Windows and type the command CMD
- When you see Command Prompt on the list, right-click on it and select Run as administrator.
- When command prompt opens, copy and paste the following command into it, then press enter.
Code:
wusa /uninstall /KB:5007295- Let me know if it says it was successful or if there are any errors.
- When you get the message: The update KB5007295 is not installed on this computer, then perform step 2.
Step 2. Follow these instructions to perform a regsearch with FRST.
- Open the startmenu and type the command cmd.
- After you find the Command Prompt, right click on it and select Run as Administrator.
- Copy and paste the following into the Command Prompt and press enter.
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS- Copy and paste the following (code) into the Search box and click the Search Registry button.
Code:
KB5007295- When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
- Post the logfile SearchReg.txt as attachment in your next reply.
Start the
Farbar Recovery Scan Tool again.
Warning: This script was written specifically for this system. Do not run this script on another system.
Warning: This script was written specifically for this system. Do not run this script on another system.
- Download the attachment fixlist.txt and save it to your desktop.
- Right-click on FRST.exe and select "Run as administrator".
- Press the Fix button.
- If for some reason the tool needs a restart, please make sure you let the system restart normally.
- When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
- Post the logfile Fixlog.txt as attachment in your next reply.
Please try to install the latest . NET update provided by Windows Update and let me know the result. If it fails again attach a new copy of the CBS logs.
My Dude!
Thank you sooo much! Your help is appreciated very much! Been fighting with this for soo long.
The update installed along with everything else that was pending.
It looks like some .NET update in the past broken something really good for me!
I dont have alot but I will donate what i can.
Thanks again!
Thank you sooo much! Your help is appreciated very much! Been fighting with this for soo long.
The update installed along with everything else that was pending.
It looks like some .NET update in the past broken something really good for me!
I dont have alot but I will donate what i can.
Thanks again!
Hi,
You're welcome. Glad to hear everything is up and running again.
And thanks for your donation to Sysnative.
You're welcome. Glad to hear everything is up and running again.
And thanks for your donation to Sysnative.
Has Sysnative Forums helped you? Please consider donating to help us support the site!