Windows 10: Cbs.log says it failed to create an open package

Ok I ran a Dism and sfc, after that i did a clean install but I still have the same problem. This sounds like a bug but it only affects Windows intelligence updates.Normal Windows updates still work.Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2023-12-25 14:57:03, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2023-12-25 14:57:03, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] 2023-12-25 14:57:03, Info CBS Session: 31078252_2278906

:)

 

Need help reading CBS log Entrys


After installing Win 10, I decided to run sfc /scannow, funny thing is why do you end up with the message about it finding corrupt files after installing a fresh copy of Win 10? Anyway, I started to look at the CBS file that was created and found the following entries:

Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2016-04-15 12:43:21, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2016-04-15 12:43:21, Info CBS Session: 30512949_3960126543 initialized by client WindowsUpdateAgent, external staging directory: (null)
2016-04-15 12:43:21, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2016-04-15 12:43:21, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]

I have no clue what this means, all I know is there is an invalid package somewhere and what package it is, no clue. This is posted a couple of times in the CBS file.

Secondly. Is there a way to find the corrupt entry(s), other than the one I inserted here because this is rather obvious, in the log file without having to spend a day going through this thing and going boinkers reading it?.

Any help would be greatly appreciated.

 

"Package Does Not Have OobeApplicability" in CBS Log, What Does it Mean?

I checked my CBS logs and saw something that has never happened before; it's normal behaviour for CBS to log a series of "detect package" messages, that's nothing new

however, it would appear that since 10:57am on the 13th of December, a new message appears under every "detecting package" log, which is "Package Does Not Have OobeApplicability"

I know oobe means Out Of Box Experience or something similar to that, but I'm unsure what this log message means or why it has started appearing

I did start installing the latest Cumulative Update on the 13th, at 10:57am; however, there were 'Detecting Packages' CBS logs at 10:57 before these OobeApplicability messages started appearing, and they didn't have anything unusual about them. it just sort of started happening 10 seconds later

the Cumulative Update started installing at 10:57am and finished at 11:01am; however, I didn't restart and apply the update until 1pm. I just noticed that the 'OobeApplicability' logs in CBS started appearing at a coinciding time so maybe that has something to do with it, I'm not sure

I just don't know what this CBS message is, or if anyone else has it. my Windows 11 system installed this Cumulative Update as well, but it doesn't have any 'OobeApplicability' CBS logs, just the normal 'Detect Package' messages

 

Understanding the CBS log & repairing corrupt files

I've been getting some event errors lately, in particular 2 errors.

Date: 10/21/2019 8:54:17 AM
Type: ErrorEvent: 1020Source: Microsoft-Windows-Perflib

The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 34008 and the required size was 45368.

Date: 10/21/2019 2:07:45 PM
Type: WarningEvent: 1008Source: Microsoft-Windows-Perflib

The Open procedure for service ".NETFramework" in DLL "C:\WINDOWS\system32\mscoree.dll" failed with error code The system cannot find the file specified.. Performance data for this service will not be available.

So I went to https://support.microsoft.com/en-us/...rrupted-system and ran

sfc /scannow

I got the message:
Windows Resource Protection found corrupt files but was unable to fix some of them.For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log.

I tried to follow the rest of the steps listed on the support page, but got lost in the details.

1. When I used an elevated Powershell & ran the suggested command, I got:

PS C:\> findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

out-file : Could not find a part of the path 'C:\%userprofile%\Desktop\sfcdetails.txt'.At line:1 char:1+ findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\s ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: ) [Out-File], DirectoryNotFoundException + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

2. I manually went to C:\Windows\Logs\CBS & opened CBS.log.There was so much detail that I couldn't follow what was corrupt. I've attached the log.

I would appreciate anyone telling me what files are corrupt & how to replace them. Thank you in advance!