CBS file " Access denied " after running sfc/scannow

  • Thread starter Thread starter Archquark
  • Start date Start date
A

Archquark

I ran sfc/scannow in administrator mode and it said it had found some
corrupt files that it was unable to fix. I opened the C:\Windows\Logs\CBS
directory and it contained 5 files:
CBS,CBS.persist,CheckSUR,CheckSUR.persist and Filterlist. I attempted to
open CBS but a message says " Access is denied ". The same applied to
CBS.persist. I am able to open CheckSUR, CheckSUR.persist and Filterlist.
Upon opening properties on these three files the date created, modified and
accessed is May-28-09.

The dates for CBS are as follows: Created: November-27-08; Modified:
June-15-09; Accessed: May-31-09.

The dates for CBS.persist are: Created: November-27-08; Modified May-31-09;
Accessed:November-27-08.

The CBS file is apparently 15.7 MB and the CBS.persist file is 50.2 MB.

Any idea why I cannot access the relevant CBS file?
 
Anne said:
You can right click it and copy it to your desktop

Open it there

Search for the word 'repair'.
Click to expand...


Delete the CBS.log before you do a SFC /SCANNOW. You'll have a much smaller
log to deal with.

You can also try...

findstr /c:"verify" "c:\windows\log\cbs\cbs.log"

and

findstr /c:"FileHashMismatch" "c:\windows\log\cbs\cbs.log"

Note: text following /c: is case sensitive
 
Thanks for both of your responses. After looking through the file it appears
that the sidebar " settings ini " file has a different system version than
other files. and there is reference to " PROCESSOR_ ARCHITECTURE_AMD64 ". My
processor is a Core 2 Quad Q8200 @2.33Ghz. Why this has occured I have no
idea. The only thing I have done since procuring the system a month ago that
would affect system files is to allow Windows updates, installed Microsoft
Office 2007 for home and students, and installed up to date device drivers
when they became available. I have pasted what I beleive is the applicable
entries. Can you suggest any repair course?

2009-06-15 10:40:59, Info CSI 000002c5 [SR] Verify
complete
2009-06-15 10:40:59, Info CSI 000002c6 [SR] Repairing 2
components
2009-06-15 10:40:59, Info CSI 000002c7 [SR] Beginning
Verify and Repair transaction
2009-06-15 10:40:59, Info CSI 000002c8 Hashes for file
member
\SystemRoot\WinSxS\amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:wPwYEjx0jUmK1ZooSr1PFJO9wl0/DOfU+QhhH2AuYuE=} Expected:
{l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-06-15 10:40:59, Info CSI 000002c9 [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture
neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35},
Type neutral, TypeName neutral, PublicKey neutral in the store, hash
mismatch
2009-06-15 10:40:59, Info CSI 000002ca Hashes for file
member
\SystemRoot\WinSxS\wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_373b6a9f10881953\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:wPwYEjx0jUmK1ZooSr1PFJO9wl0/DOfU+QhhH2AuYuE=} Expected:
{l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-06-15 10:40:59, Info CSI 000002cb [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10),
Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in
the store, hash mismatch
2009-06-15 10:40:59, Info CSI 000002cc Hashes for file
member
\SystemRoot\WinSxS\amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:wPwYEjx0jUmK1ZooSr1PFJO9wl0/DOfU+QhhH2AuYuE=} Expected:
{l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-06-15 10:40:59, Info CSI 000002cd [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture
neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35},
Type neutral, TypeName neutral, PublicKey neutral in the store, hash
mismatch
2009-06-15 10:40:59, Info CSI 000002ce [SR] This
component was referenced by
[l:162{81}]"Package_17_for_KB948465~31bf3856ad364e35~amd64~~6.0.1.18005.948465-60_neutral_GDR"
2009-06-15 10:40:59, Info CSI 000002cf Hashes for file
member
\SystemRoot\WinSxS\wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_373b6a9f10881953\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:wPwYEjx0jUmK1ZooSr1PFJO9wl0/DOfU+QhhH2AuYuE=} Expected:
{l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-06-15 10:40:59, Info CSI 000002d0 [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10),
Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in
the store, hash mismatch
2009-06-15 10:40:59, Info CSI 000002d1 [SR] This
component was referenced by
[l:162{81}]"Package_17_for_KB948465~31bf3856ad364e35~amd64~~6.0.1.18005.948465-60_neutral_GDR">
 
Archquark said:
Thanks for both of your responses. After looking through the file it
appears that the sidebar " settings ini " file has a different system
version than other files. and there is reference to " PROCESSOR_
ARCHITECTURE_AMD64 ". My processor is a Core 2 Quad Q8200 @2.33Ghz. Why
this has occured I have no idea. The only thing I have done since
procuring the system a month ago that would affect system files is to
allow Windows updates, installed Microsoft Office 2007 for home and
students, and installed up to date device drivers when they became
available. I have pasted what I beleive is the applicable entries. Can you
suggest any repair course?

2009-06-15 10:40:59, Info CSI 000002c5 [SR] Verify
complete
2009-06-15 10:40:59, Info CSI 000002c6 [SR] Repairing
2 components
2009-06-15 10:40:59, Info CSI 000002c7 [SR] Beginning
Verify and Repair transaction
2009-06-15 10:40:59, Info CSI 000002c8 Hashes for file
member
\SystemRoot\WinSxS\amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:wPwYEjx0jUmK1ZooSr1PFJO9wl0/DOfU+QhhH2AuYuE=} Expected:
{l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-06-15 10:40:59, Info CSI 000002c9 [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture
neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in
the store, hash mismatch
2009-06-15 10:40:59, Info CSI 000002ca Hashes for file
member
\SystemRoot\WinSxS\wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_373b6a9f10881953\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:wPwYEjx0jUmK1ZooSr1PFJO9wl0/DOfU+QhhH2AuYuE=} Expected:
{l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-06-15 10:40:59, Info CSI 000002cb [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10),
Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in
the store, hash mismatch
2009-06-15 10:40:59, Info CSI 000002cc Hashes for file
member
\SystemRoot\WinSxS\amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:wPwYEjx0jUmK1ZooSr1PFJO9wl0/DOfU+QhhH2AuYuE=} Expected:
{l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-06-15 10:40:59, Info CSI 000002cd [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture
neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in
the store, hash mismatch
2009-06-15 10:40:59, Info CSI 000002ce [SR] This
component was referenced by
[l:162{81}]"Package_17_for_KB948465~31bf3856ad364e35~amd64~~6.0.1.18005.948465-60_neutral_GDR"
2009-06-15 10:40:59, Info CSI 000002cf Hashes for file
member
\SystemRoot\WinSxS\wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_373b6a9f10881953\settings.ini
do not match actual file [l:24{12}]"settings.ini" :
Found: {l:32 b:wPwYEjx0jUmK1ZooSr1PFJO9wl0/DOfU+QhhH2AuYuE=} Expected:
{l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-06-15 10:40:59, Info CSI 000002d0 [SR] Cannot
repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar,
Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10),
Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8
b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in
the store, hash mismatch
2009-06-15 10:40:59, Info CSI 000002d1 [SR] This
component was referenced by
[l:162{81}]"Package_17_for_KB948465~31bf3856ad364e35~amd64~~6.0.1.18005.948465-60_neutral_GDR">
Delete the CBS.log before you do a SFC /SCANNOW. You'll have a much
smaller log to deal with.

You can also try...

findstr /c:"verify" "c:\windows\log\cbs\cbs.log"

and

findstr /c:"FileHashMismatch" "c:\windows\log\cbs\cbs.log"

Note: text following /c: is case sensitive
Click to expand...
Click to expand...

Start up Regedit and delete these two keys (save them before you delete
them, in the unlikely event you need them later)

amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758
wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_373b6a9f10881953

Run SFC again to check for any more errors. If no errors, then run Windows
Update. And also check to see if Sidebar is working OK.


wow64... I guess that means you're running Vista 64-bit, yes?
 
Yes, I am running Windows Vista Home Preminum 64 bit operating system.
Thanks for quick reply I will proform the operations suggested and get back
to you with the results.
Start up Regedit and delete these two keys (save them before you delete
them, in the unlikely event you need them later)

amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758
wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_373b6a9f10881953

Run SFC again to check for any more errors. If no errors, then run
Windows Update. And also check to see if Sidebar is working OK.


wow64... I guess that means you're running Vista 64-bit, yes?




Delete the CBS.log before you do a SFC /SCANNOW. You'll have a much
smaller
log to deal with.
Click to expand...

I was never able to do this, however, it's easy enough to delete all
data
recorded previous to the date of running sfc /scan now.

In regard to:

[SR] Cannot repair member file [l:24{12}]"settings.ini" of
Microsoft-Windows-Sidebar

Please see:

http://www.vistax64.com/general-discussion/219350-sfc-cannot-repair-sidebar-ini-hash-error.html
Click to expand...
 
I deleted the keys that you specified Tae Song and ran SFC . I then ran
Windows Update and the only file was an update to Windows Defender program.
Sidebar appears to be running fine.
Anne I read the article you provided the link to. I do have the same
messages showing up in the CBS file shown in the article, after deleting
original as suggested by Tae Song.
Thanks again to both of you. Is there someway of showing my problem has
been fixed in this newsgroup. Some newsgroups have an icon you click on to
show that you are satisfied with answers.

Archquark said:
Yes, I am running Windows Vista Home Preminum 64 bit operating system.
Thanks for quick reply I will proform the operations suggested and get
back to you with the results.
Start up Regedit and delete these two keys (save them before you delete
them, in the unlikely event you need them later)

amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_2ce6c04cdc275758
wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6002.18005_none_373b6a9f10881953

Run SFC again to check for any more errors. If no errors, then run
Windows Update. And also check to see if Sidebar is working OK.


wow64... I guess that means you're running Vista 64-bit, yes?




Delete the CBS.log before you do a SFC /SCANNOW. You'll have a much
smaller
log to deal with.
Click to expand...

I was never able to do this, however, it's easy enough to delete all
data
recorded previous to the date of running sfc /scan now.

In regard to:

[SR] Cannot repair member file [l:24{12}]"settings.ini" of
Microsoft-Windows-Sidebar

Please see:

http://www.vistax64.com/general-discussion/219350-sfc-cannot-repair-sidebar-ini-hash-error.html
Click to expand...
Click to expand...
 
Back
Top