Author Topic: SFC log (Read 46403 times)

peter915 · « **on:** March 19, 2014, 05:20:54 pm »

Hi there
I have been using tweak windows repair.
When I run SFC, it tells me there are corrupt system files.

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 · « **Reply #1 on:** March 20, 2014, 11:21:49 am »

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

Shane

peter915 · « **Reply #2 on:** March 20, 2014, 04:51:33 pm »

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 · « **Reply #3 on:** March 20, 2014, 06:54:49 pm »

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 · « **Reply #4 on:** March 20, 2014, 10:04:58 pm »

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

jraju · « **Reply #5 on:** March 20, 2014, 10:17:12 pm »

By elevated command prompt and
typing sfc /scannow.
This command may be tried for 3 times, to enable to correct system protected files from store. And to get the txt form it, i suggested the command line command.
It seeems that repairs have been done to the damaged or missing file. Did you have any problem now.

peter915 · « **Reply #6 on:** March 20, 2014, 11:02:45 pm »

I just ran sfc / scannow
results - below

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\WINDOWS\system32>

Log file is still yesterday's date?

jraju · « **Reply #7 on:** March 20, 2014, 11:15:19 pm »

Hi, am surprised that for executing the command today, you get log text dated yesterday. strange

peter915 · « **Reply #8 on:** March 21, 2014, 12:32:34 am »

I removed the entire CBS dir and did SCF again
And this time I got a new CBS log file. today's date
File attached

jraju · « **Reply #9 on:** March 21, 2014, 02:11:03 am »

No. Analyse the sfc.details txt, by the command line command i have enclosed.
See if there are missing dll files or system files. It will be shown.
Some files could not be repaired , if it includes some album, music , files leave it .
But if there are system files missing and if it is reported not found in store, then these files have to be copied from the installation dvd.
If the files are of other types, like video, sample music etc do not bother.

peter915 · « **Reply #10 on:** March 21, 2014, 03:26:24 am »

I have examined the CBS log file - and the repair section lists the following -
Note - I did a search on the net and found reference to prncacla.inf, Version = 6.2.9200.1643
This site here mentions fixes - but not quite the same as my problem.
http://www.sysnative.com/forums/windows-update/7702-guide-cnbj2530-dpb-and-prncacla-inf-corruptions-windows-8-8-1-a.html

It would seem this problem is fairly common?

copy below - CBS repair log section.

2014-03-21 16:23:57, Info CSI 000003a0 [SR] Beginning Verify and Repair transaction

2014-03-21 16:23:57, Info CSI 000003a2 [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.1643
0, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonS
xS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate",
TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-03-21 16:23:58, Info CSI 000003a4 [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.1643
0, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonS
xS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate",
TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-03-21 16:23:58, Info CSI 000003a5 [SR] This component was referenced by [l:160{80}]"Package_83_for_KB2769165~31bf3856ad364e35~x86~~6.2.
1.0.2769165-10628_neutral_GDR"

peter915 · « **Reply #11 on:** March 21, 2014, 03:29:13 am »

I then did the first repair mentioned in the link above - see my last post
Screen copy from Command prompt.

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 6.2.9200.16384

Image Version: 6.2.9200.16384

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was
repaired.
The operation completed successfully.

C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth

jraju · « **Reply #12 on:** March 21, 2014, 03:33:27 am »

hi, please say whether your problem got solved? Shane, it seems that the problem is solved. i already suggested to add a SOLVED button to enable the closure by the asker or yourself as admin.

peter915 · « **Reply #13 on:** March 21, 2014, 04:14:41 am »

Hi there
I ran SFC / scannow again, after running the fix described before
(C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth)
And the results
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

I suggest you mark this thread as a fix?
thanks
Peter

Shane · « **Reply #14 on:** March 21, 2014, 08:43:06 am »

In windows 8 MS finally gave a way to cleanup the winsxs folder, which is what the sfc was complaining about.

(This is actually in my Windows Repair Program) The new command in my repair tool tells Windows to restore the winsxs folder, which means it gets rid of old versions of files. Shrinking the size and removing problem files.

Shane

peter915 · « **Reply #15 on:** March 21, 2014, 01:19:30 pm »

Shane
So are you saying then that this problem was due mainly to poor house keeping by MS?
Or was it due to some malicious virus or ? or both?
Peter

Shane · « **Reply #16 on:** March 21, 2014, 01:23:49 pm »

Poor house keeping yes, but the winsxs folder is easy to break.

They introduced the winsxs folder starting in vista, and it always grew with every update or program install and never shrank.
http://blogs.technet.com/b/askcore/archive/2008/09/17/what-is-the-winsxs-directory-in-windows-2008-and-windows-vista-and-why-is-it-so-large.aspx

So systems that did a lot had huge winsxs folders and MS gave no way to clean it up other than a reinstall of Windows. SO finally in 8 they offered a way to clean it up removing old copys of files. Which if a old copy of a file was causing the problem then that would fix it.

When you have a folder with that many files and such it will only take 1 file to make the sfc complain, and it never gives you a reason error message and leaves it up to the user to go through a hugh log file trying to determine exactly what went wrong.

I HATE the winsxs folder, when it breaks it can create a lot of trouble.

Shane

jraju · « **Reply #17 on:** March 21, 2014, 06:05:43 pm »

Which part of the tool in your latest edition has this fix. From the tools, which one to select to have the correct size of winsxs folder

Shane · « **Reply #18 on:** March 21, 2014, 06:24:28 pm »

Repair Windows 8 Component Store :-D

Remember each repair in the program has a info file for it.

Quote

Repair Windows 8 Component Store

The following commands are done.

Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth

The first command cleans up the component store (WinSxS Folder) in windows, reducing it size and removing old entries.

The 2nd command is used to repair corrupt files and corrupt entries in the component store.

Reasons for this repair:
Used to fix Windows component store corruption when a SFC /SCANNOW command is unable to repair corrupted system files because the store (source) is corrupted, then run the SFC command again.
Used to fix Windows component store corruption when the same Windows Updates continue to appear to be available to install even though they already show successfully installed in update history.

More information on these commands can be found here:
http://technet.microsoft.com/en-us/library/hh824869.aspx
and
http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

Shane