PENDING SCCM software update install error 0x8007139F

[kaibaker]

While trying to install the monthly September patch Tuesday updates, e.g. 2025-09 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5065426) (26100.6584) and 2025-09 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 24H2 for x64 (KB5064401) would often fail on many machines with error code 0x8007139F. Every single time this would happen, the update will always install on a retry. That's if the issue happened at all, but it happened on around 60% of the endpoints this month in the test deployment group. It appeared to happen to both updates. Based on the error description, it states that the group. or resource is not in the correct state to perform the requested operation. I couldn't find any documentation of this issue for other people using SCCM. I already tried resetting windows update components, running sfc /scannow, and the DISM restore image command which all completed successfully, but nothing has fixed the issue so far. Any help would be greatly appreciated.

 

[Runkley]

While trying to install the monthly September patch Tuesday updates, e.g. 2025-09 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5065426) (26100.6584) and 2025-09 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 24H2 for x64 (KB5064401) would often fail on many machines with error code 0x8007139F. Every single time this would happen, the update will always install on a retry. That's if the issue happened at all, but it happened on around 60% of the endpoints this month in the test deployment group. It appeared to happen to both updates. Based on the error description, it states that the group. or resource is not in the correct state to perform the requested operation. I couldn't find any documentation of this issue for other people using SCCM. I already tried resetting windows update components, running sfc /scannow, and the DISM restore image command which all completed successfully, but nothing has fixed the issue so far. Any help would be greatly appreciated.

Good evening,
After attempting to install the required KBs, please check the following log: C:\Windows\Logs\CBS\cbs.log. There you will be able to determine possible errors when performing updates, provided that you have checked the correct status of the equipment through:

1. Available disk space.

2. Correct status of Windows Update components.

3. Correct system status.

I look forward to your response.

Best regards, mate,

 

[kaibaker]

Good evening,
After attempting to install the required KBs, please check the following log: C:\Windows\Logs\CBS\cbs.log. There you will be able to determine possible errors when performing updates, provided that you have checked the correct status of the equipment through:

1. Available disk space.

2. Correct status of Windows Update components.

3. Correct system status.

I look forward to your response.

Best regards, mate,

Good evening,
After attempting to install the required KBs, please check the following log: C:\Windows\Logs\CBS\cbs.log. There you will be able to determine possible errors when performing updates, provided that you have checked the correct status of the equipment through:

1. Available disk space.

2. Correct status of Windows Update components.

3. Correct system status.

I look forward to your response.

Best regards, mate,

2025-09-14 14:59:13, Info CBS Module starts contributing to an existing logging session
2025-09-14 14:59:13, Info SXS TurboStack version 10.0.26100.5074 (WinBuild.160101.0800) loaded from C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.5074_none_a5532eb7772ad4c4
2025-09-14 14:59:13, Info CSI 00000002@2025/9/14:19:59:13.997 WcpInitialize: wcp.dll version 10.0.26100.5074 (WinBuild.160101.0800)
2025-09-14 14:59:13, Info CSI 00000003 Perf: LRU Cache Initialize @0x244406c9e60; Maximum Size: 87 MiB; Initial Elements: 890
2025-09-14 14:59:13, Info CSI 00000004 Perf: LRU Cache disabled @0x244406c9e60 due to low available memory
2025-09-14 14:59:13, Info SXS Initialized store, arch=amd64, style=Desktop, compact=true, windir=(null), sandbox=
2025-09-14 14:59:13, Info CBS Virtual Edition: Microsoft-Windows-EnterpriseEdition will be mapped to: Microsoft-Windows-ProfessionalEdition
2025-09-14 14:59:13, Info CBS Session: 31204786_191169333 initialized by client WindowsUpdateAgent
2025-09-14 14:59:13, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~amd64~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2025-09-14 14:59:13, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2025-09-14 14:59:13, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2025-09-14 14:59:13, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2025-09-14 14:59:13, Info CBS Module starts contributing to an existing logging session

They mostly seem to say failed to internally open package with error 0x800f0805. When the install is attempted and it does fail, it fails within 5 to 10 seconds, but works on a retry. The error returned by the failed attempt is 0x8007139F but the log has been showing 0x800f0805.