Server 2019 Standard Cumulative Update not installing

[DirkH]

Additional information if it could help: Kaspersky was used to patch those servers until a few months. Since sometime last year we use N-Able Patch management. Both programs are still on the server.

 

[DirkH]

CBS.zip as requested:

 

[Maxstar]

if it could help: Kaspersky was used to patch those servers until a few months. Since sometime last year we use N-Able Patch management. Both programs are still on the server.

This is certainly good to know, because I am not familiar with N-Able!

The latest Servicing Stack is (17763.2350) which is a part of the following - expired - update: KB5009557 - Jan 2022.

I would suggest to disable all the third party applications first, and use the regular way to update this server to see what happens.

2024-02-01 16:10:11, Info                  CBS    Failed to get Transaction State for package: Microsoft-Windows-NetFx4-OC-Package~31bf3856ad364e35~amd64~~10.0.17763.1, update: NetFx4 [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
2024-02-01 16:10:11, Error                 CBS    Failed to get store state [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]

 

[DirkH]

Ok, I will uninstall both third-party programs now and check back with you here soon.
The log you show tells me what windows update history shows ... the system is in a restart loop. So no update/program will install which checks that state.

 

[Maxstar]

Great, it is a well-known problem that third party (security) tools may cause odd issues, so keep me posted on this.

 

[DirkH]

We had a second server with the same problems. Time pressure demanded to install a new server. But what I still can see in both cases is the ever growing pending.xml in the WinSXS folder. Deleting it brings it back from scratch.

So, back to the problem here, tried again the latest windows update. No success. Same after uninstalling N-Able, Kaspersky, even Firefox and two other unnecessary tools.
New CBS.zip is attached.

 

[Maxstar]

Hi,

Please run the .NET Framework Repair tool again and post the result.

 

[DirkH]

Installation says successful as before.
CBS.zip attached.

 

[Maxstar]

I mean this tool, this will not install anything but will create a *.cab file with logs.

Download the

Microsoft .NET Framework Repair tool and save it to your Desktop.

• 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.

 

[DirkH]

It tried to repair .NET framework 4.7.2 but there is no FixDotNet****.cab in the same directory where netfxrepairtool.exe is located (desktop). So I cannot attach the file you requested.
But I found fixdotnet.log in Appdata/Local/temp/1 of the user logged in.
The tool suggest retrying installation of .NET framework.

 

[Maxstar]

Hmm, please try to uninstall all the installed .NET Framework features using the Server Manager and let me know the result.
Hopefully it will trigger an error so we can look into this issue further.

 

[DirkH]

I can only uninstall WCF Services. Everything else is impossible because it is a domain controller and this would result in a disaster.
So I try that one uninstallation. Needed a restart.

 

[Maxstar]

Are you able to clone this server, so we can test different things safely without affecting the production server?

 

[DirkH]

I could try to clone it. But uninstalling .NET Framework means uninstalling the AD-infrastructure.
If this helps with a solution on running productive systems I can try to clone it via Veeam Instant Recovery.
I'll try that but that cannot be done before Monday evening. So I check back here in 2 days.
We had this problem on a 2019 server also but there we had .NET framwork 4.8 preinstalled.
Maybe this was the same problem. We now fear that other servers stop updating too.

 

[Maxstar]

Hi,

It seems to be an issue with .NET Framework, so if we could test som things on a clone it would be great.