Installation of cumulative update fails on Windows Server 2016

Question

Hello all,

Hopefully there is someone out there who can help diagnose and fix the problems I am having with one Windows Server 2016 that cannot install cumulative updates.

This has started with cumulative update for October, but I thought it will maybe succeed installing the November update. When trying the last month update I have also tried downloading the package and running the installer, but it just times out after some time of running.

Currently the errors in windowsupdate.log are:

2020.12.02 22:39:02.5766151 2404 8048 Handler CBS called Progress with state=2, ticks=690, total=1000

2020.12.02 22:39:14.2279740 2404 8048 Handler CBS called Error with 0x800f081f, <NULL>

2020.12.02 22:39:14.2280510 2404 8048 Handler CBS called Progress with state=7, ticks=1000, total=1000

2020.12.02 22:39:14.2283566 2404 8048 Handler CBS called Terminate

2020.12.02 22:39:14.2296989 2404 516 Handler Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x8024200d

I Have tried reinitializing windows update client. Also, I have performed sfc, but I have not found any problems with the server itself. Btw. This server is one of two Exchange DAG servers which have the same setup. On one of them updates install without problems.

Thanks in advance for your help and advice.

Br,

Mladen

Answer 1

I have attached the full windowsupdate.log file. Hopefully this will help.

44540-windowsupdatelog.txt

Answer 2

Hi,

Could we check if the Windows Server 2016 could not installed CU or any other update?

We could manually check the status of the updates on your WSUS server. Assuming its not an approval issue (i.e make sure they're all approved and targeted at the appropriate computer group). Please try to run a manual synchronication and then checking the update status again should resolve the issue.

Besides, try run Overdrives maintenance script and see if that resolves the issue:
https://community.spiceworks.com/topic/2140056-maybe-wam-wsus-is-not-longer-free
Note: the above links are not from MS, and just for your reference.

---

If the response 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.

Answer 3

Hello,

I have once more cleaned up WU on the server, rebooted it. Also, I have installed new clean WSUS server, performed synchronisation, approved the updates and tried once more. Now, the CBS error log seems to contain more information.
I am attaching both, the WU_log and BCS_log.

If there is someone who can identify the problem, it would be greatly appreciated.

Thanks,
Mladen

Answer 4

Hi,

It seems that there is something wrong with Windows Update Delivery Optimization and privacy, we could disable it in Settings. Here is the screenshot we could refer to:

Besides, we could disable it by configuring the group policy, please set it by following screenshot:

And refer to this link:
https://learn.microsoft.com/en-us/windows/deployment/update/waas-delivery-optimization

---

If the response 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.

Answer 5

Hi Amandayou,

There is no such setting on my Win2016, nor in the AD group policy, nor local group policy on the server.
Anyway, this does not make much sense because other servers (about 15-20) install updates without problems. One of those is mail2, a DAG secondary server installed and set-up the same way as mail1.

It must me some other problem.
Meanwhile, I have performed sfc and dism with normal results.