Updates failing TiWorker Server 2016

Ryan Brinch 1 Reputation point
2021-03-12T01:03:18.33+00:00

Hi, we have several servers that are failing to patch due to a Faulting Application.

Faulting application path: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4222_none_7f13461e21e4fea5\TiWorker.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Do we know how to fix this error? All Servers 2016 and all the same error application

Thanks
Ryan

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,364 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Teemo Tang 11,331 Reputation points
    2021-03-12T02:06:46.18+00:00

    Hi Ryan,
    Reset Windows update component
    https://learn.microsoft.com/en-us/windows/deployment/update/windows-update-resources
    Then check for update again.
    Also check this similar case for a hint.
    https://learn.microsoft.com/en-us/answers/questions/187412/windows-server-2016-cumulative-updates-failing.html

    -------------------------------------------------------------------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Ryan Brinch 1 Reputation point
    2021-03-12T05:14:11.317+00:00

    hi there

    Thanks, tried those steps however still an issue persists.

    Any other suggestions?

  3. kumar kaushal 176 Reputation points
    2021-04-14T09:44:47.463+00:00

    @Ryan Brinch ...In 2016 please check if on your machine you have kb4601392 . Because with 2016 https://support.microsoft.com/en-us/topic/february-9-2021-kb4601318-os-build-14393-4225-c5e3de6c-e3e6-ffb5-6197-48b9ce16446e Their is a know issue documented where the update gets stuck at 24% . And during this time you will see Tiworker.exe crash . And is recorded in Application event logs . The fix is to get recent SSU installed through DISM and you should be good to go. This was a similar issue that i faced .

    First check the above and if already have the latest SSU https://support.microsoft.com/en-us/topic/kb5001078-servicing-stack-update-for-windows-10-version-1607-february-12-2021-3e19bfd1-7711-48a8-978b-ce3620ec6362 Then disable 3rd party services or remove 3rd party components from the variables and then see if you still see the crash in tiworker.exe .

    You can also collect a procdump for the process itself during the crash

    0 comments