Main Forum > General Computer Support

SFC log

(1/4) > >>

peter915:
Hi there
I have been using tweak windows repair.
When I run SFC, it tells me there are corrupt system files. :teeth:
CBS. log attached
LAptop is a Windows 8, 32 bit, with latest updates.
2 weeks ago, I did a Windows Refresh - which was a major hassle.
And now I still have issues?
Shane, can you have a look and tell me how to fix this please.
Tweak system file checker log also attached
thanks
Peter

Shane:
From the looks of the log file it is finding files it needs to read as being corrupted

2014-03-20 08:26:24, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2014-03-20 08:26:24, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2014-03-20 08:26:24, Info                  CBS    Session: 30360514_1124961317 initialized by client WindowsUpdateAgent.
2014-03-20 08:26:24, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2014-03-20 08:26:24, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2014-03-20 08:26:24, Info                  CBS    Session: 30360514_1124961318 initialized by client WindowsUpdateAgent.
2014-03-20 08:26:24, Info                  CBS    Session: 30360514_1125430107 initialized by client WindowsUpdateAgent.
2014-03-20 08:26:24, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2014-03-20 08:26:24, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2014-03-20 08:26:24, Info                  CBS    Session: 30360514_1125430108 initialized by client WindowsUpdateAgent.
2014-03-20 08:26:24, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

I think the best thing to do is to do a bad sector check on the drive.

Open a cmd.exe window as administrator. Once open put in

chkdsk C: /f /r

It will try to check the disk but the disk will be in use and it will ask is you want to schedule it for next boot, say yes.

Now reboot, the system should start the chkdsk, if it doesnt try again. If it does start go have some coffee and wait. A chkdsk that checks every sector can take a while depending on the size and speed of the drive and weather it finds any bad sectors or not.

Lets go from there :wink:

Shane

peter915:
Shane
Did as you instructed with check disk command - at boot up
Then did a SFC / scannow
Came back with errors
SFC file log - CBS - has yesterday's date? and same size as yesterday?
Any way - nil change?
Peter

jraju:
Hi Peter,
                   It seems that you have enclosed the total cbs.log, including the problematic files found in the sfc.
Did you try this command to exactly locate the problematic files
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
If you use this command after running sfc, then it only gives the problematic portion of the log.
How did you refresh windows 7. Did you mean repair ?
This article shows some useful tips.
http://www.sevenforums.com/bsod-help-support/55984-how-analyse-cbs-log.html

peter915:
The system is windows 8,
I used the refresh command option in windows 8

Not sure how you mean to use -
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt   ?
From Command promt or Start and Run ?

I did use this command
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log
See attached file
Thanks

Navigation

[0] Message Index

[#] Next page