Weird errors in CBS log!

When I run Windows Update, I get some strange errors in the CBS log. The updates are all installing/working. This latest one is from updating the Defender definitions. I've indicated the strange ones with *** and made some notes. This was a clean install of Windows 11 22621 back in June.

I've also seen the same errors on another PC running 22621.


2022-08-29 10:14:17, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~amd64~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] *** (THIS PACKAGE DATES BACK TO WINDOWS 10 PREVIEW FROM 2014)
2022-08-29 10:14:17, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] ***




2022-08-29 10:14:17, Info CBS Session: 30980999_3073266468 initialized by client WindowsUpdateAgent, external staging directory: (null)



2022-08-29 10:14:17, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~x86~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] *** (WHY IS IT TRYING TO OPEN AN X86 PACKAGE on X64 Windows?!)
2022-08-29 10:14:17, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] ***



2022-08-29 10:14:20, Info CBS WU creates the package, AppID:MoUpdateOrchestrator, UpdateID:{33D6CF13-224E-459B-AD4F-AF8C5E3CC469}, revision: 202



2022-08-29 10:14:20, Info CBS Read out cached applicability from TiLight for package: Mapping_Package_for_KB3089226_af-ZA_amd64~31bf3856ad364e35~amd64~~10.0.10240.0, ApplicableState: 0, CurrentState:0 *** (AF-ZA? I'm running EN-GB)




2022-08-29 10:14:20, Info CBS WU creates the package, AppID:MoUpdateOrchestrator, UpdateID:{D2F7B212-A697-4BA7-BF5E-0FBE67A1E93F}, revision: 200
2022-08-29 10:14:20, Info CBS Read out cached applicability from TiLight for package: Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9075.8, ApplicableState: 112, CurrentState:112
2022-08-29 10:14:20, Info CBS WU creates the package, AppID:MoUpdateOrchestrator, UpdateID:{33238534-6440-4232-9A18-E7A602E51BE6}, revision: 201
2022-08-29 10:14:20, Info CBS Read out cached applicability from TiLight for package: Package_for_KB3064238~31bf3856ad364e35~amd64~~10.0.1.2, ApplicableState: 0, CurrentState:0




2022-08-29 10:14:17, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~amd64~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] ***




2022-08-29 10:14:17, Info CBS Session: 30980999_3073266468 initialized by client WindowsUpdateAgent, external staging directory: (null)
2022-08-29 10:14:17, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~x86~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] ***




2022-08-29 10:14:20, Info CBS WU creates the package, AppID:MoUpdateOrchestrator, UpdateID:{33D6CF13-224E-459B-AD4F-AF8C5E3CC469}, revision: 202
2022-08-29 10:14:20, Info CBS Read out cached applicability from TiLight for package: Mapping_Package_for_KB3089226_af-ZA_amd64~31bf3856ad364e35~amd64~~10.0.10240.0, ApplicableState: 0, CurrentState:0
2022-08-29 10:14:20, Info CBS WU creates the package, AppID:MoUpdateOrchestrator, UpdateID:{D2F7B212-A697-4BA7-BF5E-0FBE67A1E93F}, revision: 200
2022-08-29 10:14:20, Info CBS Read out cached applicability from TiLight for package: Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9075.8, ApplicableState: 112, CurrentState:112
2022-08-29 10:14:20, Info CBS WU creates the package, AppID:MoUpdateOrchestrator, UpdateID:{33238534-6440-4232-9A18-E7A602E51BE6}, revision: 201
2022-08-29 10:14:20, Info CBS Read out cached applicability from TiLight for package: Package_for_KB3064238~31bf3856ad364e35~amd64~~10.0.1.2, ApplicableState: 0, CurrentState:0

BrianInEngland said:

failed for Package_for_KB3025096..........0x800f0805

Click to expand...

Now that is really a weird one. Since you see this in 2 machines running the Insider Preview version of 11, I suspect it may be a bug, but, searching the web, I did not see any reports from anyone else about it. You might also search the feedback hub to see if anyone else has reported it there.

That update was a 2014 Windows 10 update with no mention in MS update catalog about Windows 11.
0x800f0805 error usually stops other updates from downloading but you say WU is working fine for defender definitions. However, there is a possibility defender updates would install when other updates would not. Have any other system updates recently installed without issue? Look at your update history under quality updates.

The normal flow of events to troubleshoot such errors would be to try the following:

1. run troubleshooter-settings-system-troubleshoot-other troubleshooters-windows update-RUN.

2. Reset Windows update using Brink's tutorial Reset Windows Update in Windows 11 Tutorial

3. From administrative command prompt run sfc /scannow (which you've already done) but do it again after resetting update components

4. run dism /online /cleanup-image /restorehealth from an administrative command prompt. Then restart and follow-up with another sfc /scannow to see if dism fixed anything.

5. Do a repair install. Repair Install Windows 11 with an In-place Upgrade Tutorial

glasskuter said:

Now that is really a weird one. Since you see this in 2 machines running the Insider Preview version of 11, I suspect it may be a bug, but, searching the web, I did not see any reports from anyone else about it. You might also search the feedback hub to see if anyone else has reported it there.

That update was a 2014 Windows 10 update with no mention in MS update catalog about Windows 11.
0x800f0805 error usually stops other updates from downloading but you say WU is working fine for defender definitions. However, there is a possibility defender updates would install when other updates would not. Have any other system updates recently installed without issue? Look at your update history under quality updates.

The normal flow of events to troubleshoot such errors would be to try the following:

1. run troubleshooter-settings-system-troubleshoot-other troubleshooters-windows update-RUN.

2. Reset Windows update using Brink's tutorial Reset Windows Update in Windows 11 Tutorial

3. Run sfc (which you've already done) but do it again after resetting update components

4. run dism /online /cleanup-image /restorehealth from an administrative command prompt. Then restart and follow-up with another sfc /scannow to see if dism fixed anything.

5. Do a repair install. Repair Install Windows 11 with an In-place Upgrade Tutorial

Click to expand...

Other updates have installed. I got the.232, 317, 382 and 457 cumulative updates.

glasskuter said:

Now that is really a weird one. Since you see this in 2 machines running the Insider Preview version of 11, I suspect it may be a bug, but, searching the web, I did not see any reports from anyone else about it. You might also search the feedback hub to see if anyone else has reported it there.

That update was a 2014 Windows 10 update with no mention in MS update catalog about Windows 11.
0x800f0805 error usually stops other updates from downloading but you say WU is working fine for defender definitions. However, there is a possibility defender updates would install when other updates would not. Have any other system updates recently installed without issue? Look at your update history under quality updates.

The normal flow of events to troubleshoot such errors would be to try the following:

1. run troubleshooter-settings-system-troubleshoot-other troubleshooters-windows update-RUN.

2. Reset Windows update using Brink's tutorial Reset Windows Update in Windows 11 Tutorial

3. Run sfc (which you've already done) but do it again after resetting update components

4. run dism /online /cleanup-image /restorehealth from an administrative command prompt. Then restart and follow-up with another sfc /scannow to see if dism fixed anything.

5. Do a repair install. Repair Install Windows 11 with an In-place Upgrade Tutorial

Click to expand...

All updates are working, I've done four cumulative updates (current build 22621.457) and the Net framework update installed last week too.

My pc was a clean install, the other one was upgraded through Windows Update back in May. Both are EN-GB locales.

SFC and DISM checks don't show any errors.

BrianInEngland said:

All updates are working,

Click to expand...

Then I suspect it is a bug in the insider version. On one of the machines I would still run steps 1-4 above to make sure.

If it still occurs after doing the troubleshooting, to get the attention of others on the same version as you, open a new thread in the Windows Insider section of this forum. In it's title say something like "RP version 22621-Does anyone else have this weird SFC error?"
In the thread say:
"I have 2 machines running 22621 that have the following SFC error about an old Windows 10 update (KB3025096) but WU is working fine. One system was a clean install of 11 and the other was an upgrade. I have run all windows update troubleshooting steps. I suspect this is a bug, but would someone else running this insider version run sfc /scannow to see if you have the same error. It would be muchly appreciated. .
<POST ERROR HERE>

22621.457 here on insider preview, no sign of anything wrong in the CBS log on running sfc /scannow.

And nothing relating to Windows 10 and that PC was an upgrade from 10. Originally on Beta but dropped it back to preview when we had that option.

Brian, I would think that if everything is working OK, it's probably not doing any harm, tried cleaning up the component store? might get rid of whatever these odd failures are.

clam1952 said:

22621.457 here on insider preview, no sign of anything wrong in the CBS log on running sfc /scannow.

And nothing relating to Windows 10 and that PC was an upgrade from 10. Originally on Beta but dropped it back to preview when we had that option.

Brian, I would think that if everything is working OK, it's probably not doing any harm, tried cleaning up the component store? might get rid of whatever these odd failures are.

Click to expand...

Yes it appears to be a strange bug, especially as 2 PCs are showing it and everything seems to be working

Just Googled KB3025096 and found this from last year and appears to relate to Win10 Redirecting

clam1952 said:

Just Googled KB3025096 and found this from last year and appears to relate to Win10 Redirecting

Click to expand...

That's interesting, looks like this bug is a hold-over from Windows 10 for some strange reason. As long as my PC works and updates I'm not worried too much. That post also has the 'AF-ZA' thing that I'm seeing with mine.

BrianInEngland said:

2022-08-29 10:14:17, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~amd64~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] *** (THIS PACKAGE DATES BACK TO WINDOWS 10 PREVIEW FROM 2014)
2022-08-29 10:14:17, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] ***
2022-08-29 10:14:17, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] ***

Click to expand...

You can ignore them, they're insignificant and are a very common "false" error.

x BlueRobot said:

You can ignore them, they're insignificant and are a very common "false" error.

Click to expand...

Yes I kind of thought that was the case. Especially the x86 references!

BrianInEngland said:

CBS_E_INVALID_PACKAGE] *** (THIS PACKAGE DATES BACK TO WINDOWS 10 PREVIEW FROM 2014)

Click to expand...

Never had this issue with 11, but 10 sure does for me. Even a fresh 10 21H2 ISO has this issue, IIRC.

RJARRRPCGP said:

Never had this issue with 11, but 10 sure does for me. Even a fresh 10 21H2 ISO has this issue, IIRC.

Click to expand...

11 as of now, has this bug!