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.

I've been seeing the fact that you have to run the sfc at least three times with a reboot each time, this I didn't know. I'll try it and see what happens. The syntax you posted is a great idea, however what goes into "[SR]". I don't use the command prompt that much.

xpac5896 said:

I've been seeing the fact that you have to run the sfc at least three times with a reboot each time, this I didn't know. I'll try it and see what happens. The syntax you posted is a great idea, however what goes into "[SR]". I don't use the command prompt that much.

Here is another way to obtain your cbs log.......................

Go to File Explorer > click This PC > click open C :drive > open Windows > open Logs > open CBS > cbs log should be at the top of the list. > open it and the log is in Notepad.

That one I already know. I've been trying to figure out how to find the problem areas without having to go through the log line per line, the file is very large even though it's mainly text. The one problem I posted is rather easily found as it is much shorter in length than the rest of the other entries in the log.
I've looked through the file, though not all of it, and am wondering how the error is worded. If I knew that then finding the problems would be much simpler. If you take the first message I posted:

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

It failed to open a package, what package that is, have no clue. My limited understanding is that there is a STORE in Windows that houses the files. If there is a problem with a particular file, Windows goes to that store and uses the file to fix or replace the file that is bad. I'm guessing that is the use of the sfc /scannow command so that it can find the bad files and repair or replace them. this is my best guess as how this works. I know there is another command, which I can't remember that can be used in conjunction with sfc /scannow that can fix the STORE if there should be corrupt files in it. The funny thing is, how do you get corrupt files when you do a clean install? The only answer I can come up with is that they were corrupt in the first place.

Thanx for that. This will help tremendously.

xpac5896 said:

Thanx for that. This will help tremendously.

Situation exactly the same, running sfc after running DSIM and then using this command:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
gave me several entries naming Power Shell as the culprit.
Microsoft Downloads only have packages that I was able to find for Win 7 and Win 8.1, which would not install on Win/10. Can't even fake it out because the install does not allow emulation of an earlier release. Here's download:
Microsoft PowerShell