Windows 10: Errors is CBS logs

Have eventually got 10 activated and it is a bit buggy freezing on certain pages and I ran the sfc and got back there are some errors - see pic - and I am wondering just what these errors are and what to do about them.

Any advice please.

Edit I went looking for them but could not find them.

:)

 

2017-05 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4016871) - Error 0x8007010b

Here's an example of what follows from the above type of error

<paste>

11/05/201713:31WindowsErrorReportingFaultbucket,type0

EventName:CbsPackageServicingFailure2

Response:Notavailable

CabId:0

Problemsignature:

P1:10.0.15063.0

P2ackage_for_RollupFix

P3:15063.296.1.5

P4:amd64

P5:unknown

P6:8007010b

P7:Resolve

P8:Absent

P9:Installed

P10:WindowsUpdateAgent

Attachedfiles:

\\?\C:\WINDOWS\Logs\CBS\CBS.log

\\?\C:\WINDOWS\Logs\CBS\CbsPersist_20170511132725.log

\\?\C:\WINDOWS\Logs\CBS\CbsPersist_20170510191039.log

\\?\C:\WINDOWS\Logs\CBS\CbsPersist_20170510115439.cab

\\?\C:\WINDOWS\Logs\CBS\CbsPersist_20170510111010.cab

\\?\C:\WINDOWS\Logs\CBS\CbsPersist_20170509223748.cab

\\?\C:\WINDOWS\servicing\Sessions\Sessions.xml

\\?\C:\WINDOWS\inf\setupapi.dev.log

Thesefilesmaybeavailablehere:

　

Analysissymbol:

Recheckingforsolution:0

ReportID:92be012e-b54e-4bae-90a6-be196d5f5d70

ReportStatus:262148

Hashedbucket:

</paste>

So, it looks like CBS converts the 0x0103 to a 0x010B. The attached files list was actually first given by a WCPOtherFailure3 event, so I think it could be showing that CBS first sees the error and then does it again with the files it wants to be associated
with the next occurrence. In any case, this is a firm clue about where to look and when: in a CBS log portion which contains that
11/05/201713:31
timestamp and earlier (often much earlier, even into the preceding chunk of the archive).



FYI

Robert

---

 

2017-11 Cumulative Update for Windows 10 Version 1709 for amd64-based Systems (KB4048955) - Error 0x800700c1

I uninstalled Carbonite...it still errors. PowerShell cannot find a CBS log...

PS C:\WINDOWS\system32> (Get-Content C:\Windows\Logs\CBS\cbs.log)[-500..-1] | clip

Get-Content : Cannot find path 'C:\Windows\Logs\CBS\cbs.log' because it does not exist.

At line:1 char:2

+ (Get-Content C:\Windows\Logs\CBS\cbs.log)[-500..-1] | clip

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : ObjectNotFound: (C:\Windows\Logs\CBS\cbs.log:String) [Get-Content], ItemNotFoundExceptio

n

+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetContentCommand

Cannot index into a null array.

At line:1 char:1

+ (Get-Content C:\Windows\Logs\CBS\cbs.log)[-500..-1] | clip

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: ) [], RuntimeException

+ FullyQualifiedErrorId : NullArray

Is it possible the updates are actually installing and the system is just reporting the error erroneously? I think I read of this scenario somewhere while searching for a solution early on.

Thanks for all the help.

 

It might be because Windows is still catching up with Windows Updates.

Copy C:\Windows\Logs\CBS\CBS.log into a compressed folder (right click, send to compressed folder). Should put the zip folder on your Desktop.

Then attach the zip folder and someone can take a look. I'm just about to hit the sack.

 

Ok Bill I will tomorrow away from home again right now and this also happened on the Sandy Bridge I had 10 installed on but I am suspecting it is because that machine was originally a Home edition of 7 even though it says it is 10 Pro*Confused

 

I had the same problem on a clean install on my new build, though the single corrupted file I had was easily solved fortunately *Smile

As mentioned, upload the CBS log in a zip and we'll have a look at it *Smile

 

Having a problem with getting those CBS logs uploaded any ideas please??

 

Could you explain what problem you have?

Have you tried to zip it up and upload the zip?

 

If the file is too big, you can try parsing the log and sending only the results: SFC-Option Five: View Only the "SFC" Scan Results from the CBS.LOG

The full log is always better, but the parsed [SR] entries will give some information to work on.

 

Well I followed the instructions to zip the CBS log and saved it t desktop but it would attach the reply post.

Now I know there is a problem because I have been trying to make a clone of the small drive to a larger one but get a blue screen (not BSOD) telling me there is a problem cloning the install and gives me an error code.

Now again I am away from home but will try again tomorrow. If nothing works then I shall have to do the clean install again my only concern is that I have activated my Kaspersky AV on this drive and they may balk at letting me activate again on the larger drive the rest I am not worried about.

 

I would create a backup and restore the backup on the larger drive, in many cases it is much easier than cloning *Smile

 

Ok Martijn I might just try that too I'll look up for a tutorial on that.

 

Well John, you're just going to have to type everything in the CBS.log *Biggrin

Nah, just kidding
... you could copy the text in the parsed log and paste it in a code box (the # on the posting menu)

You could also try disabling Kaspersky.
There were reported issues with Kaspersky 2015 not being compatible with Win10, but Kaspersky 2016 seems to work well with Win10.

Bill
.

 

Ok Bill and yes I have 2016 KIS as I always upgrade as soon as the next version comes out - one can use the same activation code which is a plus at least. But I will disable it pro tem as well.

 

Disable it just as a test to see if it might be causing some of the issues on your machine.

It should be relatively easy to figure out if that was causing problems.

Disabled - no BSOD or other issues you reported (uploading the CBS zip folder...)
Contact Kaspersky
Run MS Defender until you get an answer

Disabled - still have BSODs or other issues you reported (uploading the CBS zip folder...)
Enable Kaspersky
It wasn't causing the issue(s)

Bill
.