Windows Server 2016 version 1607 fails to install Cumulative updates.

Anonymous
2024-02-27T21:32:23+00:00

This issue seems to have plagued this server for quite some time (OS Build 14393.3443). Other update types, including the servicing stack, are successful, but all cumulative updates fail. Currently, KB534767 is in an update loop. It downloads and prepares for restart, only to fail overnight each night. The same occurred with KB5034119. The error is 80070057.

I have tried various repairs with DISM including using a WIM file from a working image as a source. Any advice would be greatly appreciated. I have also tried just about every option in the wureset.exe tool.

Thanks,

-Dan

Windows Server Devices and deployment Install Windows updates, features, or roles

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Anonymous
    2024-02-28T06:51:48+00:00

    Hi Dan Hines1,

    the error code 80070057 usually indicates that there is a problem with the Windows Update components or the update files themselves. Here are some steps you can try to resolve the issue:

    1. Run the Windows Update troubleshooter. This tool can automatically detect and fix common issues with Windows Update. To run the troubleshooter, go to Settings > Update & Security > Troubleshoot > Windows Update.
    2. Reset the Windows Update components. You can do this by running the following commands in an elevated Command Prompt:
      net stop wuauserv 
      
      net stop cryptSvc 
      
      net stop bits 
      
      net stop msiserver 
      
      ren C:\Windows\SoftwareDistribution SoftwareDistribution.old 
      
      ren C:\Windows\System32\catroot2 catroot2.old 
      
      net start wuauserv 
      
      net start cryptSvc 
      
      net start bits 
      
      net start msiserver 
      
    3. Manually download and install the cumulative update. You can download the update from Microsoft Update Catalog and install it manually.
    4. Check the system files for corruption. You can use the System File Checker (SFC) tool to scan for and repair corrupted system files. To run SFC, open an elevated Command Prompt and type "sfc /scannow".

    Hope it helps.

    Kind regards,

    Lei

    0 comments No comments
  2. Anonymous
    2025-02-26T15:01:07+00:00

    Hi Dan and Lei

    I am having exactly the same issue on a list of my clients Windows Server 2016 version 1607 devices.

    I have completed the above fixes from Lei on all devices and have run the sfc /scannow and all the repair options using the DISM command on all devices.

    Some of the devices did in fact have corrupted files in the system image which the DISM command repaired, but so far, none of this has resolved the problem and these devices continue to fail to patch the Cumulative Update.

    This has been happening to these devices for nearly a year now.

    I have been in contact with our patching supplier who have informed me that there is something on these servers that is rejecting the installation of the Cumulative Update patch.

    Upon some brief investigation on Google it is said that one of these could be causing the patch to be rejected.

    1. Drive space limitations - could be this, as most of these devices have very small OS hard drives
    2. Corrupt system files - cannot be this, cause I have run and repaired what I had to
    3. Network connectivity - wont be this as these devices are live 24/7
    4. Incompatible applications - unlikely to be this as these devices used to patch fine, and now do not. No applications have changed on the devices.
    5. Pending reboots - not this as device gets rebooted once a month when patching is attempted
    6. Windows update service issues - ?
    7. Outdated drivers - could very well be this

    If you have any other ideas of what could cause this, please let me know?

    Thanks

    0 comments No comments