Trying to install cumulative windows updates on a W2022 server and it keeps failing with error: 0x800f0983

Question

Trying to install cumulative windows updates on a W2022 server and it keeps failing with error: 0x800f0983. Have tried clearing out software updates fodlers, stopping and restarting BITs services, running the windows update troubleshooter but still can't install any updates. Have also increased the update partition but this does still not allow successful installation. This has failed for CU 2024-01 & 2024-02.

Answer 1

Hello David Young5,

there can be a problem with the .NET Framework installation on your server. To resolve this issue, you can try the following steps:

1. Open the Server Manager and go to the "Add Roles and Features" wizard.
2. Select the "Features" option and expand the ".NET Framework 4.8 Features" node.
3. Check if the "ASP.NET 4.8" feature is installed. If not, select it and click "Install".
4. Restart the server and try installing the updates again.

If the above steps do not resolve the issue, you can try the following:

1. Open the Command Prompt as an administrator.
2. Type the following command and press Enter: DISM /Online /Cleanup-Image /RestoreHealth
3. Wait for the command to complete and then restart the server.
4. Try installing the updates again.

Hope it helps.

Best regards,

Lei

Answer 2

Thanks Lei.

I've tried both methods and I am still getting the same error.

I've run the Windows Update troubleshooter, and it reports finding an error (and fixed) but doesn't actual fix the issue. The error status:

---

Windows Update Publisher details:

Issues found.

Check for Windows Update issues.

Check for Windows Update issues.

Detects issues related to Windows Update.

Detected.

Resolve Windows Update issues Completed.

Potential issues that were checked

Some security settings are missing or have been changed.

Some security settings are missing or have been changed Issue not present.

Check for missing or corrupt files.

Check for missing or corrupt files Issue not present.

Service registration is missing or corrupt.

Service registration is missing or corrupt Issue not present.

Issues found Detection details.

6 Check for Windows Update issues Detected.

Detects issues related to Windows Update.

Resolve Windows Update issues Completed.

Resolves common Windows Update issues.

InformationalWaaSMedicService

Issues remediated by: DynamicProtectionPlugin

Potential issues that were checked Detection details.

Some security settings are missing or have been changed Issue not present.

Check for missing or corrupt files Issue not present.

Service registration is missing or corrupt Issue not present.

Detection details Expand.

InformationalIsPostback_RC_PendingUpdates

IsPostback: False

InformationalWaaSMedicService

Issue found by:DynamicProtectionPlugin

InformationalIsPostback_RC_PendingUpdates

IsPostback: True

InformationalService Status

Problem with BITS service: The requested service has already been started. System.Management.Automation.RemoteException More help is available by typing NET HELPMSG 2182. System.Management.Automation.RemoteException

InformationalService Status

Problem with BITS service: The requested service has already been started. System.Management.Automation.RemoteException More help is available by typing NET HELPMSG 2182. System.Management.Automation.RemoteException

Collection information

Computer Name: PG-VEEAM

Windows Version: 10.0

Architecture: x64

Time: Wednesday, February 21, 2024 10:34:41 AM

Publisher details Expand

Background Intelligent Transfer Service

Find and fix problems that may prevent background downloads from working

Package Version: 3.5

Publisher: Microsoft Windows

Windows Network Diagnostics

Detects problems with network connectivity.

Package Version: 4.0

Publisher: Microsoft Windows

Windows Update

Resolve problems that prevent you from updating Windows.

Package Version: 9.3

Publisher: Microsoft Windows

Windows Update

Resolve problems that prevent you from updating Windows.

Package Version: 9.2

Publisher: Microsoft Corporation

---

I've even setup an allow all rule in our firewall specific for this server to avoid any potential issues but it is not this causing the problem.

I noticed that when updating it gets to 100% and then fails.

Please advise next step(s) to try as I don't want to have to "rebuild" this server as it is running our Veeam tools and a local repository.

This has been present since cumulative update 2023-12 but prior to that all was updating OK. Any cumulative update since 2023-11 has failed.

Thanks.

DY

Answer 3

Hi DY,

you can understand the cause of the issue and how to fix it by looking at the CBS logs when you are experiencing issues with your Windows Server device and deployment. Here are the steps to view the issue in CBS logs:

1. Open the Event Viewer application.
2. In the left panel, expand "Windows Logs" and select "Applications".
3. In the right panel, locate and click on the "CBS" entry.
4. In the details below, look for error or warning information related to the issue you're experiencing.
5. You can use filters to narrow down the logs so that it's easier to find relevant information.

Answer 4

Hi Lei,

Looking at the event viewer Windows Logs > Applications and there are only Application Errors appearing against wuauclt:

Faulting application name: wuauclt.exe, version: 10.0.20348.1547, time stamp: 0xc5cefde9

Faulting module name: ntdll.dll, version: 10.0.20348.1487, time stamp: 0x04ff1d20

Exception code: 0xc0000005

Fault offset: 0x0000000000019daa

Faulting process id: 0x470c

Faulting application start time: 0x01da0145340f9ebe

Faulting application path: C:\Windows\system32\wuauclt.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 839f7cb1-7839-4c32-9b86-39698d31791a

Faulting package full name:

Faulting package-relative application ID:

Application, module, code and offset are the same for all entries.

Should I be replacing the mentioned DLL file?

Thanks.

DY

Answer 5

Hi DY,

right. However, I would recommend creating a backup of the original file before replacing it.

Additionally, it's important to ensure that you obtain the correct version of the file for your specific version of Windows Server.

Lei