Server 2016 updates install failure

It's also possible that you will see new cumulative updates released today and it might be worth trying those instead.
 
I downloaded the update and started installing it about 4 hours ago, it appears to be doing the same thing, this window is still sitting there:
1644364739894.png
 
I searched for updates this morning and it found the 2022-02 Cumulative Update KB5010359, I told it to apply it and it went to "Downloading updates 9%" in about 10 minutes and nothing more for several hours. I deleted Software Distribution and tried again with the same results. I ran sfc and dism checks and they reported no problems. I downloaded the KB5010359 msu and used expand to extract the .cab and then tried install it using dism add-package but after 10 minutes it reported two errors: Error: 0x800706be and Error: 1726.
I was able to correlate this, as well as previous update attempts, with Application Errors in the event log:
Code: 
Faulting application name: TiWorker.exe, version: 10.0.14393.4222, time stamp: 0x5fffc8b5
Faulting module name: KERNELBASE.dll, version: 10.0.14393.3659, time stamp: 0x5e9140ed
Exception code: 0x80000003
Fault offset: 0x00000000000c6e72
Faulting process id: 0x14dc
Faulting application start time: 0x01d81c413fe706e5
Faulting application path: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4650_none_7eeb34dc2202872c\TiWorker.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
 
We have another thread in which the OP is experiencing the same DISM errors during a .cab installation via DISM. It is proving very difficult to fix.
@PeterJ is currently working on that thread and he may be interested in comparing your findings too. Please provide the CBS.logs from this last attempt.
 
CBS-DISM.7z (3.91MB) - SendSpace.com

C:\Temp>dism /online /add-package /packagepath:c:\temp\02\Windows10.0-KB5010359-x64.cab

Deployment Image Servicing and Management tool
Version: 10.0.14393.3750

Image Version: 10.0.14393.3241

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.4946.1.5
[=========== 20.0% ] An error occurred - Package_for_RollupFix Error: 0x800706be

Error: 1726

The remote procedure call failed.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 
My suspicion is that the Trusted Installer was updated to current with the recent Servicing Stack Update, but since the rest of the system hasn't had a successful update in 18 months there is some system .dll the Trusted Installer is trying to use that is too old and doesn't have a feature it is trying to use. If that is the case we can either try manually updating some of the system DLL's, or since I am working with a VM clone and haven't run the SSU on the live server yet I can revert the VM to the pre-SSU state and we can try manually applying intermediate SSU and cumulative updates to gradually bring it up to date. Unless you have some other ideas for tracking down and fixing the Trusted Installer crashes.
 
Last edited:
We are exploring new territory here so your ideas are good. The other thread I referred you to has also identified a possible .dll to investigate.

Let's see what @PeterJ comes up with.
 
I ran a search for the two files mentioned in your error report on my Server 2016.

I have a match for the TiWorker.exe file but my version of the kernelbase.dll is more recent at version 10.0.14393.4886 which appears to have come from KB5009546. Perhaps you could try and install this update.

[Note: If you want to run a similar search on your systems use the following script file and drag and drop it over SFCFix.exe to run the search and output the results.]
 

Attachments

Here's the results. With Trusted Installer crashing I'm afraid I can't install any updates, unless you mean revert the VM to it's earlier status first.
 

Attachments

Can you go back in your VM to a point where you were installing successfully as reported in post #12? Then try and install KB5009546 before you move on to try the one that failed.
 
I reverted the VM and brought it to the point just after removing the 2 Components keys and multiple reboots, sfc /scannow and dism /restorehealth both complete and report no integrity violations. I snapshotted the VM here. I also have no NIC connected to avoid automatic updates from interfering. I then made two different attempts from this starting point. In the 1st I installed the 2020-09 SSU.msu which installed without error and then tried to install the 2020-11-cumulative update.msu which appeared to hang, after a couple hours I checked the Application Event Log and found the TiWorker crash. I then reverted and tried just doing a dism /add-package with the 2022-02-Cumulative-Update.cab, after a while it failed with the 2 errors and the TiWorker crash was logged. I'm attaching screenshots of the event log TiWorker errors from both attempts.
 

Attachments

  • 2022-02-16 22_30_55-Try1.png
    2022-02-16 22_30_55-Try1.png
    19.4 KB · Views: 4
  • 2022-02-17 00_15_55-Try2.png
    2022-02-17 00_15_55-Try2.png
    20 KB · Views: 4
Last edited:
I would be interested in seeing the CBS logs after you had rebooted multiple times and then rerun the SFC and DISM commands. Please return to that snapshot and post the logs.
 
Please try and manually install KB5005698 (SSU 2021-09) at this point.
Afterwards post the CBS.logs
 
Can you let me know which updates are offered if you check via Windows Update. At this stage do not install anything - I'm just interested to know what is offered.
 
It found these 5 updates and immediately began downloading/installing them.
1645212856491.png
 
And it appears to have hung at 27% and the Application Event Log shows a TiWorker crash:

1645213162814.png
 
I suggest you go back and install them manually by downloading them from the Microsoft Catalogue one at a time. If any fail, stop, capture the CBS log and post it here before doing any more.

Install the Microsoft Office ones first. For now I would suggest not installing the 2022-02 CU
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top