Windows

Quick Tip: Scan Windows 7 system files to repair errors

Despite our best efforts, every once in a while, Microsoft Windows 7 system files will become corrupted. A simple scan can fix these system errors.

Knock on wood, this has not happened to me in a very, very long time, but every once in a while the Microsoft Windows system files will become corrupted and report errors. The solution to this annoying, but fixable, problem is to repair the files. A reboot of the PC will often do the trick, but there is a way to repair files while Windows 7 is running and, presumably, you are working productively.

This blog post is also available in PDF format in TechRepublic download.

Stay on top of the latest Microsoft Windows tips and tricks with TechRepublic's Windows Desktop newsletter, delivered every Monday and Thursday. Automatically sign up today!
First you will need to start a permission-elevated command-line prompt. Type command into the Desktop Search box and then right-click on the Command Prompt menu entry and select the Run as Administrator item (Figure A).

Figure A

Run the command prompt as administrator.

After accepting the elevated permissions, at the prompt type this command:

sfc /scannow

Now the system will verify the system files and repair any corrupted files (Figure B).

Figure B

Scan for errors.
My test system had no errors (Figure C); however if it did, this scan would have repaired any corrupted files, but without forcing a system reboot.

Figure C

No errors were found.

About

Mark Kaelin is a CBS Interactive Senior Editor for TechRepublic. He is the host for the Microsoft Windows and Office blog, the Google in the Enterprise blog, the Five Apps blog and the Big Data Analytics blog.

54 comments
magical11
magical11

That was very helpful..Thanks but how do I get to the CBS.Log file to see what files are corrupt and unable to fix

Grayko
Grayko

Another thought:  Having written the positive comment just below, and after 30+ years dealing in PC's, I believe MS consistently issues flawed OS's, which leave many of us in a wake of time consuming troubleshooting.  I am getting too, too old for this, and am seriously thinking about the lighter side of Apple.

Grayko
Grayko

There is much to be said for the simple "sfc /scannow" from within the Win7 command window - Note:  Simply follow Mark's instructions to run "command" from Start as an administrator by right clicking it and choosing "Run as Administrator" from the pull-down menu.  This solved my issue with a missing / corrupt sti.dll scanner driver.  Thanks to Mark Kaelin for the tip.  The following is a partial log file from my system (afterward, scan issues were solved):

2014-02-09 18:48:06, Info                  CSI    00000308 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:14{7}]"sti.dll" from store
2014-02-09 18:48:06, Info                  CSI    00000309 Repair results created:
POQ 128 starts:
     0: Create File: File = [l:254{127}]"\SystemRoot\WinSxS\amd64_microsoft-windows-w..sition-coreservices_31bf3856ad364e35_6.1.7601.17514_none_90ba4080c9f2e648\sti.dll", Attributes = 00000080
    1: Move File: Source = [l:158{79}]"\SystemRoot\WinSxS\Temp\PendingRenames\b47bf4c2f925cf01833800002019a00d.sti.dll", Destination = [l:254{127}]"\SystemRoot\WinSxS\amd64_microsoft-windows-w..sition-coreservices_31bf3856ad364e35_6.1.7601.17514_none_90ba4080c9f2e648\sti.dll"
    2: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\753ef9c2f925cf01843800002019a00d._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
    3: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\753ef9c2f925cf01853800002019a00d.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
    4: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\966200c3f925cf01863800002019a00d.$$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
    5: Hard Link File: Source = [l:254{127}]"\SystemRoot\WinSxS\amd64_microsoft-windows-w..sition-coreservices_31bf3856ad364e35_6.1.7601.17514_none_90ba4080c9f2e648\sti.dll", Destination = [l:62{31}]"\??\C:\Windows\System32\sti.dll"

POQ 128 ends.
2014-02-09 18:48:06, Info                  CSI    0000030a [SR] Repair complete
2014-02-09 18:48:06, Info                  CSI    0000030b [SR] Committing transaction
2014-02-09 18:48:06, Info                  CSI    0000030c Creating NT transaction (seq 2), objectname [6]"(null)"
2014-02-09 18:48:06, Info                  CSI    0000030d Created NT transaction (seq 2) result 0x00000000, handle @0x101c
2014-02-09 18:48:06, Info                  CSI    0000030e@2014/2/10:00:48:06.897 CSI perf trace:
CSIPERF:TXCOMMIT;183058
2014-02-09 18:48:06, Info                  CSI    0000030f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

ron
ron

"Command" yields the DOS window in older systems. In Windows 7 the DOS window is accessed by typing "cmd". At least that's the case on my PC.

rdhumphries
rdhumphries

Can anyone one tell me what this is or how it got on my computer? I cannot even enter "command prompt" without a popup telling me to buy this overpriced system and will not allow me to use the computer systems for 150 seconds. I cannot enter a command prompt because this popup re-appears when I try to re-enter. I cannot even turn off the computer till after to 150 second time frame. This popup takes total control of the computer. Have no idea where it came from.... Below is the website and I have recieved no replys when I have tried to contact them..... Can anyone help me here? http://www.contextmenu.net/register_windows_explorer_shell_context_menu.html

yyeefix
yyeefix

http://www.fixexedll.com FixExeDll.com is professional website which can tell you how to scan your PC, safely fix errors & clean invalid entries that cause system slow, freezing and crashing, and speed up system performances effectively.

dasabhinav
dasabhinav

after following the above steps, I've received the message saying "Windows Resource Protection cannot start the repair service"

UdaMRockZ
UdaMRockZ

I did the scan.but at 15% it stops and it displays " Windows Resource Protection could not perform the requested operation". My OS is Win 7 Ultimate SP1 32bit. Please provide me with a solution.

ringo
ringo

[I'm having trouble understanding why after all these years when you want to do anything other than run a program we still have to go to DOS!] Most computers be it mainframe, mini or micro work at roughly the DOS level and lower (read machine language). Do not be foiled by the pretty screen mouse etc. for the most part that is sizzle and little if any steak.

jd
jd

I'm having trouble understanding why after all these years when you want to do anything other than run a program we still have to go to DOS! I mean get real - I think everything we do from a command prompt should be available as a tool in accessories by now.

nikthiemann
nikthiemann

I have an "spdcmdcon.sys" error and no scan will work. This malware is blocking all before it comes to a blue screen saying I have to do this and that wich does not work either. So much for scans. I even tried to bypass with a USB nada

Texas.Ex
Texas.Ex

Does anyone know what to do if SFC won't run at all? I get the message "Windows Resource Protection could not start the repair service." I'm running Windows 7 Home Premium, 64-bit. Thanks in advance. Sparky

billfranke
billfranke

How do I get the "Run as Admin" choice? I followed the steps provided, but when I right-clicked, I was no "run as administrator" option to click. When I right-click on other programs, however, that choice appears. I took ownership of the command prompt, but that changed nothing. I tried to run sfc/scannow, but I was told that I needed admin privileges to do that. I am the only user of this desktop PC and my account clearly says that I am an administrator. Why am I locked out and how can I change this? [Edit: I'm running Win7 Home Premium 64-bit English on my own home network.]

jdev1
jdev1

2010 SFC Scan now READ CBS LOG file results only possible when logged on Windows as a system administrator

jdev1
jdev1

sfc /scan now error and all attempt reading txt file gives display message access denied

sailnow
sailnow

Sounds wonderful, but is such a utility available with Windows XP Pro ? Bill W - sailnow@bluefrog.com

kclewis0614
kclewis0614

This may be quicker for some users... to quickly run as administrator, say for CMD follow the steps above until the right-click... instead of doing that ctrl-Shift then enter. this will run as administrator... little tip I learned working for HP..."now right click...no RIGHT click ... That would be the button on the RIGHT...never mind pres CTRL-SHIFT then while holding those down, press enter... it worked? great..."

jonc2011
jonc2011

My Win7/64 system found errors: "Windows Resource Protection found corrupt files and successfully repaired then. Details are included in C:\Windows\Logs\CBS\CBS.log" But access to this file is denied, even when I gain full permissions. Ideas anyone? ANSWER - (in a post below - thanks), is to run Notepad as administrator, then open the log file. However, unless you're a techie, it won't tell you very much. My log file is 8MB. So far no detectable change in computer performance (+ or -).

Mark W. Kaelin
Mark W. Kaelin

At the risk of jinxing myself, I have not had any system errors in a very, very long time. Have you? How did you repair the corrupted files?

darkstate
darkstate

Have you tried running it in safe mode? Reboot and press F8

callupchuck
callupchuck

I also get the message "Windows Resource Protection could not start the repair service." I'm running Vista home premium 32-bit. The system will not boot except to a Vista repair disc. I have removed several infections from the drive by scanning it remotely, but am still unable to get it to boot on it's own.

d_g_l_s
d_g_l_s

to get to the command prompt is to go to Start menu, All Programs, Accessories, and then right-click on the Command Prompt and you should see the Run as Administrator.

paul.viacrucis
paul.viacrucis

So I opened the CBS.log file with Notepad++ running as admin. When you do, be prepared for lots of code to look at. My log file was over 32,000 lines long! You can bet I'm not going to go down there and try to figure out what was fixed. Suffice it to say I will just accept the message that my corruption(s) were fixed according to the results message I received from the command line.

drzaius
drzaius

Run Notepad as an administrator & then open the log file from Notepad

darkstate
darkstate

Yes this is available for XP but its a bit more complicated, you will need the xp disc so it can compare the contents of the I386 folder on the disc with the XP system files. The way I did it was like this. Use your xp cdrom - and copy I386 directory to C:\Documents and Settings\Your user name\My Documents\XP (Or anywhere on your PC) - modify HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ SourcePath=C:\Documents and Settings\Your user name\My Documents\XP (This points sfc /scannow.exe to the i386 file you just copied) Run sfc /scannow.exe. (Run windows update right after sfc has completed running to make sure you get the latest hotfixes.) Also make sure the disc is the same service pack otherwise it won't work and will kill your pc. Also do this at your own risk. This worked for me many times when i was new to XP many years ago and worked fine for a friend. Goodluck

sailnow
sailnow

This utility in Win 7, sounds great. Is such a utility available in Windows XP home & Pro ??

atateroy
atateroy

Hey, You have lost me totally! Where is the "right click" step? And when should I press "CTRL-SHIFT"?

Texas.Ex
Texas.Ex

When I run sfc /scannow I get the following message: "Windows Resource Protection could not start the repair service." What happened? I am running Windows 7 Home Premium, 64-bit with lots of RAM and disc space. Thanks in advance for the help. Sparky

ghbgiest
ghbgiest

I have a 64bit Windows 7 Professional running on a Intel Core 2 Duo 64 bit machine. I loaded some bad USB drivers from card reader. So I used SFC /scannow and only fixed a few at a time; so I ran it multiple(25 or so)times. Made the system worse; didn't fix the USB. Finally I had to "upgrade" reinstall Windows 7; that fixed everything.

aubs50
aubs50

the files aere still corrupted as sfc/scannow does not list the files that are corrupt.i do not know how to find the corrupted files so am having to plod along as it is tho it is slow. thanks for reply aubs

aubs50
aubs50

ran sfc/scannow and it says has corrupted files that it cannot repair.Yet the systaem (vista 64 home premium)runs ok a bit slow but ok.

Texas.Ex
Texas.Ex

Nope - didn't work for me - same response! Sparky

billfranke
billfranke

Thank you for the suggestion, but there's still no "Run as Administrator" option.

BeyondITall
BeyondITall

Does anyone else think it is strange that you would need administrative permissions to read a system log file? Why is such an elevated permission needed in the first place? These are, afterall, log files. Is there some malware that is jacking with the log files and giving false readings to the end user as a result? Should that be the case, then you have more concerns than just a log file.

kclewis0614
kclewis0614

"First you will need to start a permission elevated command line prompt. Type command into the Desktop Search box and then right-click on the Command Prompt menu entry and select the Run as administrator item. (Figure A)" instead of right clicking, hold down ctrl-shift and press enter... hope that helps...

darkstate
darkstate

Have you tried the command string findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt This will show you the corrupt files that it found Make sure you go to the directory %windir%\logs\cbs\cbs.log >sfcdetails.txt when its done to see the results. As the last post says, go to http://support.microsoft.com/kb/929833 for more info.

Stacy Sherrill
Stacy Sherrill

I sometimes wear a low-end tech-support hat. In assisting clients with running certain software, there are times when the software will not run under a particular user account (even if an administrator). The tried/true solution for this is to create another account and run the software from there. Obviously not an optimum solution. Will this repair corrupt account permissions? If not, what will?

darkstate
darkstate

I'm presuming you are doing this as admin? If you are using cmd make sure you right click and run as administrator. Here's some info about the error you are getting and what it is in respect to the os. http://msdn.microsoft.com/en-us/library/aa382503%28VS.85%29.aspx I'm on win 7 ultimate and it works fine for me using either a cmd or a bat file run as admin.

d_g_l_s
d_g_l_s

though not sure why that was not already visible and available. I do sometimes look into the right-click properties in order to enable Administrator for a particular program that needs it and so I thought of this possibility for your situation. Glad it works! Thank God.

billfranke
billfranke

Thank you very much! That did it. "Run as Administrator" now appears when I right-click.

d_g_l_s
d_g_l_s

to right-click on the Command Prompt program, choose Properties and Shortcut tab, then choose Advanced and select Run as Administrator?

d_g_l_s
d_g_l_s

are you running? Never mind, I just noticed the end of your article. :)

BeyondITall
BeyondITall

that aspect of using the system file checker and how to get a report. What I do not understand is why you would need to view this file with administrative rights. What is Microsoft's purpose of doing this? This is, afterall, only a report.

darkstate
darkstate

To run and then see the results of scannow. To verify and fix an error in windows 7, open a elevated command prompt and type sfc /SCANNOW To see what couldn't be fixed if it show's an error . Next look to see what wasn't fixed by typing findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt then %windir%\system32\Sfcdetails.txt For a more detailed description and even taking ownership of a denied access file. goto -> http://support.microsoft.com/kb/929833

dleippe
dleippe

Once you get to a command prompt with administrative privileges type "sfc /scannow" and be prepared to have your installer disk for XP, Vista, or Windows 7. XP has always prompted me for the disk. So far Windows 7 hasn't required the disk.

dleippe
dleippe

Just go to Start>Programs>Accessories>CMD Right click CMD and select Run as administrator or right click CMD and select pin to start menu or pin to taskbar for faster access next time. Each time right click CMD and select run as Administrator

Raymond Danner
Raymond Danner

From the large number of references to the Sidebar's Settings.ini file, I suspect that is the problem. Try renaming the file and have Sidebar recreate it.

aubs50
aubs50

how do I include the text of sfc file seems that the fault is the windows sidebar? I am not an IT specialist,I am just a normal pc user and do not or rather did not understand any of what I was doing.Am learning though.thanks aubs soft-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 2010-11-16 23:51:34, Info CSI 0000016f [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 2010-11-16 23:54:25, Info CSI 000001e3 [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 2010-11-16 23:54:26, Info CSI 000001e8 [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 2010-11-16 23:58:15, Info CSI 000002f4 [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 2010-11-16 23:58:15, Info CSI 000002f6 [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 2010-11-16 23:58:15, Info CSI 000002f8 [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 2010-11-16 23:58:15, Info CSI 000002fb [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 2010-11-17 00:26:38, Info CSI 0000016d [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 2010-11-17 00:26:43, Info CSI 0000016f [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 2010-11-17 00:28:43, Info CSI 000001e3 [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 2010-11-17 00:28:44, Info CSI 000001e8 [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 2010-11-17 00:31:37, Info CSI 000002f4 [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 2010-11-17 00:31:37, Info CSI 000002f6 [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 2010-11-17 00:31:37, Info CSI 000002f8 [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 2010-11-17 00:31:38, Info CSI 000002fb [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 2010-11-17 00:47:46, Info CSI 0000016d [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 2010-11-17 00:47:51, Info CSI 0000016f [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 2010-11-17 00:50:33, Info CSI 000001e3 [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 2010-11-17 00:50:35, Info CSI 000001e8 [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 2010-11-17 00:54:19, Info CSI 000002f4 [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 2010-11-17 00:54:19, Info CSI 000002f6 [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 2010-11-17 00:54:19, Info CSI 000002f8 [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 2010-11-17 00:54:19, Info CSI 000002fb [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 2010-11-17 20:51:17, Info CSI 0000016d [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 2010-11-17 20:51:22, Info CSI 0000016f [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 2010-11-17 20:53:59, Info CSI 000001e3 [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 2010-11-17 20:54:01, Info CSI 000001e8 [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 2010-11-17 20:57:43, Info CSI 000002f4 [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 2010-11-17 20:57:43, Info CSI 000002f6 [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 2010-11-17 20:57:43, Info CSI 000002f8 [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 2010-11-17 20:57:43, Info CSI 000002fb [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