Windows Server 2022 cumulative updates fail with 0x80073701 — Missing NetworkController assembly, DISM reports healthy
I'm experiencing a persistent Windows Update issue on a production Windows Server 2022 system and am looking for assistance with a Component-Based Servicing (CBS) repair.
Server information:
- OS: Windows Server 2022, version 21H2
Current build: 20348.4052
Last successfully installed cumulative OS update: KB5063880 (August 2025)
Roles: Active Directory Domain Services, DNS, and File Server
This is our only domain controller.
Problem:
Cumulative OS updates have consistently failed since approximately August 2025 with error 0x80073701 (ERROR_SXS_ASSEMBLY_MISSING).
Recent failed updates include:
KB5126655 — October 2026 cumulative update
KB5134140 — October 2026 cumulative update, attempted using the standalone Microsoft Update Catalog installer
The standalone installation produces the same error, so this does not appear to be solely a Windows Update download-cache issue.
CBS.log identifies the following failure:
HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING)
ICSITransaction_PinDeployment(
a = NetworkController-Server-Deployment,
version = 10.0.20348.3932,
arch = amd64
)
Failed to pin deployment while resolving Update:
NetworkController-Server-Package
0x80073701
The error also references:
Microsoft-Windows-msmq-powershell-Opt-WOW64-Package
10.0.20348.3932
Troubleshooting performed:
DISM /Online /Cleanup-Image /ScanHealth — No component store corruption detected.
DISM /Online /Cleanup-Image /RestoreHealth — Completed successfully.
sfc /scannow — No integrity violations found.
Checked Windows feature states. Network Controller management tools and MSMQ are available but not installed.
Queried the affected package using DISM. NetworkController-Server-Package~31bf3856ad364e35~amd64~~10.0.20348.3932 is registered as Staged.
Checked C:\Windows\WinSxS\Manifests. The NetworkController-Server-Deployment manifest for version 10.0.20348.3932 is missing, although versions 20348.4050 and 20348.5622 exist.
Downloaded and extracted the original Microsoft KB5062572 cumulative update. Located and extracted the exact missing manifest:
amd64_networkcontroller-server-deployment_31bf3856ad364e35_10.0.20348.3932_none_fa2908d4d09c92ec.manifest
Ran DISM with the extracted manifest directory as a repair source:
DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\UpdateRepair\RepairSource /LimitAccess
The command completed successfully, but the missing manifest was not restored.
Retried with standalone KB5134140. Installation failed again with the same missing assembly.
CBS.log also states:
Exec: Will not run corruption repair
because no store corruption found.
Questions:
What is the supported method for repairing a missing CBS deployment assembly when DISM reports the component store as healthy?
Can the missing NetworkController-Server-Deployment version 20348.3932 be restored using the original Microsoft cumulative update package without manually modifying WinSxS?
Could the staged Network Controller package have an inconsistent servicing registration, and how can that be safely diagnosed or repaired?
Is there an alternative supported servicing repair method that avoids an in-place OS repair or rebuilding the domain controller?
Because this server is our only domain controller and file server, I am trying to resolve the issue without disrupting Active Directory, DNS, or shared file services.
I can provide the full CBS.log and additional DISM logs if needed.
Any guidance on a supported targeted CBS repair would be greatly appreciated.I'm experiencing a persistent Windows Update issue on a production Windows Server 2022 system and am looking for assistance with a Component-Based Servicing (CBS) repair.
Server information:
OS: Windows Server 2022, version 21H2
Current build: 20348.4052
Last successfully installed cumulative OS update: KB5063880 (August 2025)
Roles: Active Directory Domain Services, DNS, and File Server
This is our only domain controller.
Problem:
Cumulative OS updates have consistently failed since approximately August 2025 with error 0x80073701 (ERROR_SXS_ASSEMBLY_MISSING).
Recent failed updates include:
KB5126655 — October 2026 cumulative update
KB5134140 — October 2026 cumulative update, attempted using the standalone Microsoft Update Catalog installer
The standalone installation produces the same error, so this does not appear to be solely a Windows Update download-cache issue.
CBS.log identifies the following failure:
HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING)
ICSITransaction_PinDeployment(
a = NetworkController-Server-Deployment,
version = 10.0.20348.3932,
arch = amd64
)
Failed to pin deployment while resolving Update:
NetworkController-Server-Package
0x80073701
The error also references:
Microsoft-Windows-msmq-powershell-Opt-WOW64-Package
10.0.20348.3932
Troubleshooting performed:
DISM /Online /Cleanup-Image /ScanHealth — No component store corruption detected.
DISM /Online /Cleanup-Image /RestoreHealth — Completed successfully.
sfc /scannow — No integrity violations found.
Checked Windows feature states. Network Controller management tools and MSMQ are available but not installed.
Queried the affected package using DISM. NetworkController-Server-Package~31bf3856ad364e35~amd64~~10.0.20348.3932 is registered as Staged.
Checked C:\Windows\WinSxS\Manifests. The NetworkController-Server-Deployment manifest for version 10.0.20348.3932 is missing, although versions 20348.4050 and 20348.5622 exist.
Downloaded and extracted the original Microsoft KB5062572 cumulative update. Located and extracted the exact missing manifest:
amd64_networkcontroller-server-deployment_31bf3856ad364e35_10.0.20348.3932_none_fa2908d4d09c92ec.manifest
Ran DISM with the extracted manifest directory as a repair source:
DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\UpdateRepair\RepairSource /LimitAccess
The command completed successfully, but the missing manifest was not restored.
Retried with standalone KB5134140. Installation failed again with the same missing assembly.
CBS.log also states:
Exec: Will not run corruption repair
because no store corruption found.
Questions:
What is the supported method for repairing a missing CBS deployment assembly when DISM reports the component store as healthy?
Can the missing NetworkController-Server-Deployment version 20348.3932 be restored using the original Microsoft cumulative update package without manually modifying WinSxS?
Could the staged Network Controller package have an inconsistent servicing registration, and how can that be safely diagnosed or repaired?
Is there an alternative supported servicing repair method that avoids an in-place OS repair or rebuilding the domain controller?
Because this server is our only domain controller and file server, I am trying to resolve the issue without disrupting Active Directory, DNS, or shared file services.
I can provide the full CBS.log and additional DISM logs if needed.
Any guidance on a supported targeted CBS repair would be greatly appreciated.