Windows >
Windows Vista Forums
>
Desktop & Personalization
>
Cannot unlock password-protected Screensaver. Have to unplug PC to re login.
Cannot unlock password-protected Screensaver. Have to unplug PC to re login.
- I've had my 64-bit Home Premium Vista PC since 12/08. One weird problem seems to have gone from a 1x/month occurrence to 1 - 2x/week and it is getting annoying:
I've go away from the PC for an hour or several, I return, screensaver is churning away as it should,
I touch the keyboard or mouse to hit Ctrl Alt del and type in my password but instead of seeing the default screen for my PC and my name and blank field to type in my password,
I get a black screen except for a cursor arrow.
I hit ctrl alt del and everything else I can think of to bring up the login screen but it's still just black screen and white arrow.
the only way I can get to my PC is to unplug and reboot totally. This is getting old.
How do I make it go away? Thank you.4 people need an answerI do too
All Replies
- Hello angela_g,
1. Open Power Options by clicking the Start button, clicking Control Panel, clicking System and Maintenance, and then clicking Power Options.
2. On the Select a power plan page, in the task pane, click Require a password on wakeup.
3. On the Define power buttons and turn on password protection page, click Don't require a password.
4. Click Save changes.
Hope this helps you. Let us know either way. Make it a great day!
"In the End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.)- Unmarked As Answer byBarb WinterMSFT, ModeratorThursday, September 10, 2009 12:18 AM
- Unproposed As Answer byRyanT - Support EngineerMSFTTuesday, September 29, 2009 6:33 PM
- Proposed As Answer byRoger Wo Thursday, September 10, 2009 7:05 AM
- Marked As Answer byangela_g Friday, August 28, 2009 10:46 PM
- well, 16 hours after your fix suggestion, problem has not yet reoccured. But may only happen 1 or 2/x month. I'll let you know if it does. Fingers crossed . . .
- Unproposed As Answer byRyanT - Support EngineerMSFTTuesday, September 29, 2009 6:33 PM
- Proposed As Answer byRoger Wo Thursday, September 10, 2009 7:05 AM
- Hello angela_g,
I think you'll be fine now. Glad to hear your issue was resolved. Make it a great day!
"In the End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.)- Proposed As Answer bygreenajj114 Monday, September 21, 2009 7:12 PM
- Unproposed As Answer byRyanT - Support EngineerMSFTTuesday, September 29, 2009 6:32 PM
- Uh, guess again. My machine locked as described above 2x in the past 12 hours. Which is way more frequently than I ever had before this "fix." I still haven't lost any data because I tend to save docs before I go away from the PC, but this 2nd time, for whatever reason, it took a heckuva a long time to get all the apps and browser windows up and running again.
I went back to Ctrl Panel. For all 3 possible power plan settings, it is still at Don't require a password . But for some reason, this is not working.
This is the sort of reason why people migrate from PC to Mac, I think.
Another idea to solve this stupid annoying issue once and for all? - Hello angela_g,
No problem! Lets try this option below:
To resolve this issue, use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps:- Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
- Type the following command, and then press ENTER: sfc /scannow (yes there is a space after sfc) The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.
To determine which files could not be repaired by the System File Checker tool, follow these steps:
- Open an elevated command prompt.
- Type the following command, and then press ENTER:
findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txtNote The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool.
- Type the following command, and then press ENTER:
edit sfcdetails.txtThe Sfcdetails.txt file uses the following format:Date/Time SFC detail
The following sample log file contains an entry for a file that could not be repaired:2007-01-12 12:10:42, Info CSI 00000008 [SR] Cannot repair member file [l:34{17}]"Accessibility.dll" of Accessibility, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
If the System File Checker tool cannot repair a file, follow these steps:- At an elevated command prompt, type the following command, and then press ENTER:
takeown /f Path_And_File_NameFor example, type takeown /f E:\windows\system32\jscript.dll.
- Type the following command, and then press ENTER to grant administrators full access to the file:
icacls Path_And_File_Name /GRANT ADMINISTRATORS:FFor example, type icacls E:\windows\system32\jscript.dll /grant administrators:F.
- Type the following command to replace the file with a known good copy of the file:
Copy Path_And_File_Name_Of_Source_File Path_And_File_Name_Of_DestinationFor example, type copy E:\temp\jscript.dll E:\windows\system32\jscript.dll.
- You may need to have your Vista OS dvd on hand to repair your system should the scan fail to fix some of the files.
Hope this helps you. Let us know either way. Make it a great day!
"In the End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.) - Thank you but here's what happened.
I did your first 1) and 2) fine.
I did second 2), entered the command, nothing happened. Got cmd prompt again. But maybe that's what's supposed to happen?
I tried to do 3) after that but got an error msg:
"'edit' is not recognized as an internal or external command, operable program or batch file. "
I also tried to access the CBS.log file on my own using Notepad. Couldn't open it, got a Notepad error msg saying "access is denied." When I did the system scan it said it found corrupt files but was unable to fix some of them.
So as far as I can tell, this exercise did nothing to solve the problem.
BTW, I realize we all have our own personal style, but if you were me, and you were working with a technician and you did the fix they suggested (a week or 2 ago) and they indicate they think the problem is solved, but then the problem reoccurs, in a particularly annoying way, and you attempt to communicate your annoyance and frustration to the person you're dealing with and the answer you get back is "No problem" with no indication of sympathy that the first fix they were confident about didn't work, how would you feel?
Hello angela_g,
Sorry that my advice and fix lasted only 2 weeks on your PC. If i offended you in any way, I sorry! I meant "no problem" as to lets go to another possible solution without delay. If I was you and your were me I would want you to get my PC fixed ASAP. ;-) Can you tell me what it said when the scan was finished (example: No Integrities found etc.) Did you reboot your system after the scan? Hope this helps you. Make it a great day!
"In the End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.)- Since the problem sometimes only occurred 1x/month, not sure that your previous 'fix' made any difference at all. Hence, my statement that as far as I can tell, this has done nothing to solve the problem.
When the scan was finished it said it found some corrupt files and was unable to fix some of them, then said where the log file with details were, the cbs.log file I could not open.
I don't think I rebooted my system after the scan but I can't recall for sure. Was I supposed to?
Hello angela_g,
Do you have your Vista OS dvd? You will need it to repair your corrupt files with it. You posted this info which has helped us. CBS.Logs are not to be worried about at this time. Remember these are system files, when they are corrupt the windows/program will not operate correctly. Make it a great day!
"In the End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.)- Edited byTHE C. Wednesday, September 09, 2009 7:19 AM
- Yes, I believe I have my Vista OS DVD.
I have tried to answer all your questions. You have not answered all of mine, such as when I asked
"I don't think I rebooted my system after the scan but I can't recall for sure. Was I supposed to?" Could you please answer that question?
I was also surprised that when I reported an error when I typed the cmd you instructed me to,
"Type the following command, and then press ENTER:edit sfcdetails.txt"I got in return and reported to you the msg:
"'edit' is not recognized as an internal or external command, operable program or batch file,"
Yet you did not provide any explanation or clarification as to why this didn't work.
I am surprised now when you say.
"You also never posted this info which would have helped us"
Please clarify what info you are referring to. I have no idea. - Hello angela_g,
I am very determined to get you back up and running! ;-) Okay, yes after the scan you should have posted it found corrupted files and couldn't repair all of them! So I know it was able to fix some of the files though, so a reboot, which you have done since then so what answer would I need to provide you now regarding reboot? You believe you have the Vista OS dvd? When you have it handy, see instruction below:
If you have a Windows Vista installation disc, you need to restart (boot) your computer using the installation disc. If you do not restart your computer from the disc, the option to repair your computer will not appear.If you have a Windows installation disc:
1. Insert the installation disc.
2. Restart your computer.
Click the Start button, click the arrow next to the Lock button, and then click Restart.
3. If prompted, press any key to start Windows from the installation disc.
NoteIf your computer is not configured to start from a CD or DVD, check the information that came with your computer. You may need to change your computer's BIOS settings. 4. Choose your language settings, and then click Next.
5. Click Repair your computer.
6. Select the operating system you want to repair, and then click Next.
7. On the System Recovery Options menu, click Startup Repair. Startup Repair might prompt you to make choices as it tries to fix the problem and, if necessary, it might restart your computer as it makes repairs.
If Startup Repair is a preinstalled recovery option on your computer:
1. Remove all floppy disks, CDs, and DVDs from your computer, and then restart your computer.
Click the Start button, click the arrow next to the Lock button, and then click Restart.
2. Do one of the following:
• If your computer has a single operating system installed, press and hold the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you will need to try again by waiting until the Windows logon prompt appears, and then shutting down and restarting your computer.
• If your computer has more than one operating system, use the arrow keys to highlight the operating system you want to repair, and then press and hold F8.
3. On the Advanced Boot Options screen, use the arrow keys to highlight Repair your computer, and then press ENTER. (If Repair your computer is not listed as an option, then your computer does not include Startup Repair as a preinstalled recovery option.)
4. Select a keyboard layout, and then click Next.
5. Select a user name and enter the password, and then click OK.
6. On the System Recovery Options menu, click Startup Repair. Startup Repair might prompt you to make choices as it tries to fix the problem and, if necessary, it might restart your computer as it makes repairs.
Hope this helps you. Let us know either way. Make it a great day!
"In the End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.)- Edited byTHE C. Wednesday, September 09, 2009 7:18 AM
- 1. I said Mon. at 4:32PM PT in answer to your question:
"When the scan was finished it said it found some corrupt files and was unable to fix some of them, then said where the log file with details were, the cbs.log file I could not open."
Is this the info that you were referring to when you subsequently said:
" You also never posted this info which would have helped us. "??
I really can't tell if this is the info you want or not. I wish you'd tell me specfically what info you want from me. Now you say "So I assumed nothing was found!" but IF the corrupted files are what you refer to, something WAS found, and so I don't know if all your subsequent instructions to me today apply to me or not. Can you please clarify what you mean?? I THINK something was found but again, I can't tell if you missed my msg. Mon or if you are referring to something else.
2. Also, was I supposed to say something other than
"Type the following command, and then press ENTER:edit sfcdetails.txt" ??Since what I got in return and reported to you was:
"'edit' is not recognized as an internal or external command, operable program or batch file,"
Yet you did not provide any explanation or clarification as to why this didn't work, whether I should have used some similar syntax. Can you please tell me what I should have entered here to get the result you had in mind?
3. Finally, is there a way other than Notepad for me to open up that CBS.log file without getting an "access denied" message??
When you clarify the information I ask for in #1, I will know if I should follow the instructions in your msg today.
Hello angela_g,
There is no debate! It was my mistake on the corrupt files and you posting it, don't worry about the CBS.log files for you need to try and repair those files. As for the access denied, if you ever have trouble just right click cmd prompt and run as administrator. Please follow the instructions I provided in my previous reply. Let me know either way if the repair helps you. I will be waiting, take care. Make it a great day!
"In the End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.)- I'd like to clarify that The C is a volunteer in the forums. He's helped many, many Microsoft Answers users by volunteering his own time and expertise here in our community forums.
Becuase you marked his initial reply which seemed to solve your problem was marked as an answer, Microsoft support agents would not have monitored this thread or pursued it.
Since your problem came back, I have unmarked it (sorry, C!) so that other community experts and Microsoft support agents can take a look at it.
I would suggest that you try the repair option he outlines, as that is typically the best way to deal with corrupted files. Once you do that, please let us know if you need continued support.
I'll make sure that we watch this thread to see if the repair solves your issue.
thanks for using the forums,
Barb Winter
Microsoft Answers Program Manager
Visit our Microsoft Answers Feedback Forum and let us know what you think.If you get your question answered, please come back and mark the reply as an answer so others can find it.
If you get helped by an answer to someone else's question, please mark the post as Helpful.
- Edited byBarb WinterMSFT, ModeratorThursday, September 10, 2009 12:30 AMclarity
- Hello Barbara,
We will wait for angela_g's reply. Thanks, for the update! Make it a great day!
"In the End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.) - Hello Barbara,
Thank you for your message. I said the question was answered after C said on 8/31, "I think you'll be fine now." My mistake. I will be more careful in the future about marking questions as answered.
I will be happy to do as C requests when he answers my questions. Here is one that seems to have been disregarded from Wed. I was hoping that numbering out the questions would help but I guess not.
"2. Also, was I supposed to say something other than
"Type the following command, and then press ENTER:edit sfcdetails.txt" ??Since what I got in return and reported to you was:
"'edit' is not recognized as an internal or external command, operable program or batch file,"
Yet you did not provide any explanation or clarification as to why this didn't work, whether I should have used some similar syntax. Can you please tell me what I should have entered here to get the result you had in mind?"
C, if you feel this question is irrelevant or you don't understand it or whatever, could you at least acknowledge it by letting me know that?
Thank you. - BTW, C, I opened the CBS.logs file (thanks for the hint about how to open with Admin rights -- surprised I didn't know that sooner.) The file is quite long, even if I just look at the time period when I ran the scan as you suggested. Is there anything in particular that I should look for within the file, or were you just interested in the result I earlier reported:
"When the scan was finished it said it found some corrupt files and was unable to fix some of them, then said where the log file with details were, the cbs.log file I could not open."
BTW, I do not have a Vista DVD, just Vista CDs.
I still look forward to you clarifying what you meant on Mon. when you told me to enter the command
edit sfcdetails.txt
and I got "bad syntax" msg in return.
I'm guessing this is the "System File Checker" you refer to later in that email.
If this is a step to solving this problem, I prefer, unless told to do otherwise, to finish this step before proceeding to any further steps. Hence, I look forward to your explicit clarification to what I should do to make this command work or, if you had commands confused and I should go onto something else.
Thank you.
- Hello angela_g,
One that is labled OS recovery, is the Vista dvd. The other one is likely a drivers or software disc. You will need to follow previous reply with this disc. Make it a great day!
"In the End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.) - Hello, Angela
I will be happy to do as C requests when he answers my questions. Here is one that seems to have been disregarded from Wed. I was hoping that numbering out the questions would help but I guess not.
"2. Also, was I supposed to say something other than
"Type the following command, and then press ENTER:edit sfcdetails.txt" ??Since what I got in return and reported to you was:
"'edit' is not recognized as an internal or external command, operable program or batch file,"
Yet you did not provide any explanation or clarification as to why this didn't work, whether I should have used some similar syntax. Can you please tell me what I should have entered here to get the result you had in mind?"The command was incorrect; it should have been "notepad.exe sfcdetails.txt". It will show the parsed version of the CBS.log file and as you noticed, it is quite long so it’s definitely helpful in seeing what file(s) couldn’t be repaired.
The easiest way of opening it so that we can find out what couldn’t be repaired would be to go to Start, All Programs, Accessories, right click Command Prompt and choose Run as Administrator. You may be prompted to continue. In the Command Prompt simply type notepad.exe sfcdetails.txt and press ENTER.
If Notepad opened the file, skip below, but if a blank Notepad window opens, you will need to run the file scan again – aside from the one command, they are the same as what The C posted:
In the Command Prompt that you opened, type (or copy and paste) the following commands one at a time and press enter:
SFC /SCANNOW
findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log > sfcdetails.txt
notepad.exe sfcdetails.txtIn the sfcdetails file in notepad, you will notice that each line begins with a date and time (Year-Month-Day Hour:Minute:Second), it may go back a long time and there may be a lot of them, but to make it easier, we will start from the bottom (the most recent).
So scroll down to the very bottom and take note of the date, copy all the lines from the date that you took note of and paste them to us.
We look forward to hearing back from you.
David
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think. - Hi David & C,
1. Startup Repair Results
From both my PC and from the OS "Reinstallation DVD" that came with my Dell, I did what C suggested on Sept. 8. No errors were found when I ran "Startup Repair."
2. Other Utilities Results
I also ran 2x some test utilities in a separate CD that came from Dell with the PC. It found both times "Error msg 4400:0011A Msg SCSI 0-0000 Disk 0 Compact flash
Target not ready." (Dell may only know how to interpret this, but didn't sound related to my problem.
3. CBS.LOG and takeown /f Results
A couple of days ago, I went in cbs.log (after C told me to open with Admin) and did a search for "Cannot repair . . ." That gave me the same file names tcpmon.ini and settings.ini.
Unfortunately, the information AROUND the filenames looked much like the sample info that C gave Sept. 7, with (to me) no easy to read pathname. I tried to copy and paste the file names and cmd:
takeown /f \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\tcpmon.ini
(with pathname preceded by a C: and with no C:) Either way, for both files I always got
" Error: The system cannot find the path specified."
Below I have copied (1) tcpmon.ini repair results and (2) systems.ini repair results from CBS.LOG
(1) tcpmon.ini
2009-09-06 18:27:04, Info CSI 0000013b [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-
TCPMonINI, Version = 6.0.6001.18000, 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-09-06 18:27:06, Info CSI 0000013c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-
tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2009-09-06 18:27:06, Info CSI 0000013d [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-
TCPMonINI, Version = 6.0.6001.18000, 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-09-06 18:27:06, Info CSI 0000013e [SR] This component was referenced by [l:164
{82}]"Package_30_for_KB936330~31bf3856ad364e35~amd64~~6.0.1.18000.936330-185_neutral_GDR"
2009-09-06 18:27:06, Info CSI 0000013f Hashes for file member \??\C:\Windows\System32\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2009-09-06 18:27:06, Info CSI 00000140 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-
tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2009-09-06 18:27:06, Info CSI 00000141 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini";
source file in store is also corrupted
2009-09-06 18:27:06, Info CSI 00000142 Repair results created:
POQ 51 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\b172e74e5a2fca016b160000ec157803._0000000000000000.cdf-ms", Destination =
[l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\d1c0e74e5a2fca016c160000ec157803.$$.cdf-ms", Destination = [l:74
{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
2: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\1121f24e5a2fca016d160000ec157803.$$_system32_21f9a9c4a2f8b514.cdf-ms",
Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
3: Move File: Source = [l:272{136}]"\SystemRoot\WinSxS\Temp\PendingRenames\8185fa4e5a2fca016e160000ec157803.$$_system32_printing_admin_scripts_en-
us_f242a041737eb912.cdf-ms", Destination = [l:184{92}]"\SystemRoot\WinSxS\FileMaps\$$_system32_printing_admin_scripts_en-us_f242a041737eb912.cdf-ms"
4: Move File: Source = [l:204{102}]"\SystemRoot\WinSxS\Temp\PendingRenames\71a32d4f5a2fca016f160000ec157803.$$_inf_3f581daba4c8c835.cdf-ms",
Destination = [l:116{58}]"\SystemRoot\WinSxS\FileMaps\$$_inf_3f581daba4c8c835.cdf-ms"
5: Move File: Source = [l:220{110}]"\SystemRoot\WinSxS\Temp\PendingRenames\813b304f5a2fca0170160000ec157803.$$_inf_pnrpsvc_3932681b8fb41c9d.cdf-ms",
Destination = [l:132{66}]"\SystemRoot\WinSxS\FileMaps\$$_inf_pnrpsvc_3932681b8fb41c9d.cdf-ms"
6: Move File: Source = [l:230{115}]"\SystemRoot\WinSxS\Temp\PendingRenames\f1bd334f5a2fca0171160000ec157803.$$_inf_pnrpsvc_0409_437342b1fe2eac8a.cdf
-ms", Destination = [l:142{71}]"\SystemRoot\WinSxS\FileMaps\$$_inf_pnrpsvc_0409_437342b1fe2eac8a.cdf-ms"
7: Move File: Source = [l:298
{149}]"\SystemRoot\WinSxS\Temp\PendingRenames\f1a8754f5a2fca0172160000ec157803.$$_system32_spool_tools_microsoft_xps_document_writer_6c7957555c36ce
bb.cdf-ms", Destination = [l:210{105}]"\SystemRoot\WinSxS\FileMaps\$$_system32_spool_tools_microsoft_xps_document_writer_6c7957555
2009-09-06 18:27:06, Info CSI c36cebb.cdf-ms"
8: Move File: Source = [l:226{113}]"\SystemRoot\WinSxS\Temp\PendingRenames\f183904f5a2fca0173160000ec157803.$$_system32_tasks_5f1dd67a5a1ae70e.cdf
-ms", Destination = [l:138{69}]"\SystemRoot\WinSxS\FileMaps\$$_system32_tasks_5f1dd67a5a1ae70e.cdf-ms"
9: Move File: Source = [l:246
{123}]"\SystemRoot\WinSxS\Temp\PendingRenames\11d2904f5a2fca0174160000ec157803.$$_system32_tasks_microsoft_b7abd682baafefc2.cdf-ms", Destination =
[l:158{79}]"\SystemRoot\WinSxS\FileMaps\$$_system32_tasks_microsoft_b7abd682baafefc2.cdf-ms"
10: Move File: Source = [l:220{110}]"\SystemRoot\WinSxS\Temp\PendingRenames\5150964f5a2fca0175160000ec157803.$$_pla_reports_a2604845b2b380ca.cdf-
ms", Destination = [l:132{66}]"\SystemRoot\WinSxS\FileMaps\$$_pla_reports_a2604845b2b380ca.cdf-ms"
11: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\e1209a4f5a2fca0176160000ec157803.$$_pla_system_571618c4f89c6368.cdf-ms",
Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\$$_pla_system_571618c4f89c6368.cdf-ms"
12: Move File: Source = [l:216{108}]"\SystemRoot\WinSxS\Temp\PendingRenames\51a39d4f5a2fca0177160000ec157803.$$_pla_rules_0bde462ce96f215e.cdf-ms",
Destination = [l:128{64}]"\SystemRoot\WinSxS\FileMaps\$$_pla_rules_0bde462ce96f215e.cdf-ms"
13: Create Directory: Directory = [l:30{15}]"\??\C:\PerfLogs", Attributes = 00000080
14: Create Directory: Directory = [l:42{21}]"\??\C:\PerfLogs\Admin", Attributes = 00000080
15: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\115aa44f5a2fca0178160000ec157803.program_files_ffd0cbfc813cc4f1.cdf-ms",
Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
16: Move File: Source = [l:262
{131}]"\SystemRoot\WinSxS\Temp\PendingRenames\a12aa84f5a2fca0179160000ec157803.program_files_windows_collaboration_6ec8ad810c61b947.cdf-ms",
Destination = [l:174{87}]"\SystemRoot\WinSxS\FileMaps\program_files_windows_collaboration_6ec8ad810c61b947.cdf-ms"
17: Move File: Source = [l:274{137
2009-09-06 18:27:06, Info CSI
}]"\SystemRoot\WinSxS\Temp\PendingRenames\b1c2aa4f5a2fca017a160000ec157803.program_files_windows_collaboration_en-us_cee18e392f8e71b7.cdf-ms",
Destination = [l:186{93}]"\SystemRoot\WinSxS\FileMaps\program_files_windows_collaboration_en-us_cee18e392f8e71b7.cdf-ms"
and
(2) Settings. ini
2009-09-06 18:27:55, Info CSI 00000160 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:0PDSWziLzWVBYwaR3HhXAym9NjNH+J+Minhz2QfaecY=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-09-06 18:27:55, Info CSI 00000161 [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-09-06 18:28:01, Info CSI 00000162 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:0PDSWziLzWVBYwaR3HhXAym9NjNH+J+Minhz2QfaecY=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2009-09-06 18:28:01, Info CSI 00000163 [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-09-06 18:28:01, Info CSI 00000164 [SR] This component was referenced by [l:162
{81}]"Package_17_for_KB948465~31bf3856ad364e35~amd64~~6.0.1.18005.948465-60_neutral_GDR"
2009-09-06 18:28:03, Info CSI 00000165 Repair results created:
POQ 58 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\6193fb6e5a2fca016d190000ec157803._0000000000000000.cdf-ms", Destination =
[l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\81e1fb6e5a2fca016e190000ec157803.$$.cdf-ms", Destination = [l:74
{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
2: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\c141066f5a2fca016f190000ec157803.$$_system32_21f9a9c4a2f8b514.cdf-ms",
Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
3: Move File: Source = [l:246
{123}]"\SystemRoot\WinSxS\Temp\PendingRenames\415c0c6f5a2fca0170190000ec157803.$$_system32_speech_speechux_bf4b53e8d47da913.cdf-ms", Destination =
[l:158{79}]"\SystemRoot\WinSxS\FileMaps\$$_system32_speech_speechux_bf4b53e8d47da913.cdf-ms"
4: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\a1b70f6f5a2fca0171190000ec157803.program_files_ffd0cbfc813cc4f1.cdf-ms",
Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
5: Move File: Source = [l:250
{125}]"\SystemRoot\WinSxS\Temp\PendingRenames\11c9106f5a2fca0172190000ec157803.program_files_windows_sidebar_8d6dbc4becba56da.cdf-ms", Destination =
[l:162{81}]"\SystemRoot\WinSxS\FileMaps\program_files_windows_sidebar_8d6dbc4becba56da.cdf-ms"
6: Move File: Source = [l:262{131}]"\SystemRoot\WinSxS\Temp\PendingRenames\d19d126f5a2fca0173190000ec157803.program_files_windows_sidebar_en-
us_467d8a71f43f36ce.cdf-ms", Destination = [l:174{87}]"\SystemRoot\WinSxS\FileMaps\program_files_windows_sidebar_en-us_467d8a71f43f36ce.cdf-ms"
7: Move File: Source = [l:208{104}]"\SystemRoot\WinSxS\Temp\PendingRenames\31bd1f6f5a2fca0174190000ec157803.$$_ehome_40103e2da1d121de.cdf-ms",
Destination = [l:120{60}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_40103e2da1d121de.cdf-ms"
8: Move File: Source
2009-09-06 18:28:03, Info CSI = [l:230
{115}]"\SystemRoot\WinSxS\Temp\PendingRenames\81f1226f5a2fca0175190000ec157803.$$_ehome_createdisc_ed3f8f2e7a4426af.cdf-ms", Destination = [l:142
{71}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_ed3f8f2e7a4426af.cdf-ms"
9: Move File: Source = [l:252
{126}]"\SystemRoot\WinSxS\Temp\PendingRenames\3110276f5a2fca0176190000ec157803.$$_ehome_createdisc_styles_pal_55d264f56641a00e.cdf-ms", Destination =
[l:164{82}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_styles_pal_55d264f56641a00e.cdf-ms"
10: Move File: Source = [l:270
{135}]"\SystemRoot\WinSxS\Temp\PendingRenames\f1e4286f5a2fca0177190000ec157803.$$_ehome_createdisc_styles_pal_symphony_b9729623521ab9e5.cdf-ms",
Destination = [l:182{91}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_styles_pal_symphony_b9729623521ab9e5.cdf-ms"
11: Move File: Source = [l:288
{144}]"\SystemRoot\WinSxS\Temp\PendingRenames\31f22b6f5a2fca0178190000ec157803.$$_ehome_createdisc_styles_pal_symphony_symphony_f1d008156719fefe.cd
f-ms", Destination = [l:200{100}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_styles_pal_symphony_symphony_f1d008156719fefe.cdf-ms"
12: Move File: Source = [l:224
{112}]"\SystemRoot\WinSxS\Temp\PendingRenames\612b366f5a2fca0179190000ec157803.$$_speech_common_76cd6f1aaba6e83b.cdf-ms", Destination = [l:136
{68}]"\SystemRoot\WinSxS\FileMaps\$$_speech_common_76cd6f1aaba6e83b.cdf-ms"
13: Move File: Source = [l:266
{133}]"\SystemRoot\WinSxS\Temp\PendingRenames\b1ed45705a2fca017a190000ec157803.program_files_windows_sidebar_gadgets_265d2ddf4d58a723.cdf-ms",
Destination = [l:178{89}]"\SystemRoot\WinSxS\FileMaps\program_files_windows_sidebar_gadgets_265d2ddf4d58a723.cdf-ms"
14: Move File: Source = [l:300
{150}]"\SystemRoot\WinSxS\Temp\PendingRenames\51d9c8705a2fca017b190000ec157803.users_default_appdata_roaming_microsoft_windows_sendto_cc2b2363b730
3311.cdf-ms", Destination = [l:212{106}]"\SystemRoot\WinSxS\FileMaps\users_default_appdata_roaming_microsoft_windows_sendto_cc2b2363b7303311.cdf-ms"
15: Move File: Source = [l:236{118}
2009-09-06 18:28:03, Info CSI
]"\SystemRoot\WinSxS\Temp\PendingRenames\f11cea705a2fca017c190000ec157803.$$_system32_smi_schema_b445cd341d59fadc.cdf-ms", Destination = [l:148
{74}]"\SystemRoot\WinSxS\FileMaps\$$_system32_smi_schema_b445cd341d59fadc.cdf-ms"
16: Move File: Source = [l:262
{131}]"\SystemRoot\WinSxS\Temp\PendingRenames\21a9fb705a2fca017d190000ec157803.$$_system32_licensing_channels_ocur_0c3b4dedc2b45c25.cdf-ms",
Destination = [l:174{87}]"\SystemRoot\WinSxS\FileMaps\$$_system32_licensing_channels_ocur_0c3b4dedc2b45c25.cdf-ms"
17: Move File: Source = [l:242
{121}]"\SystemRoot\WinSxS\Temp\PendingRenames\619803715a2fca017e190000ec157803.$$_ehome_createdisc_style_0d4521df11573950.cdf-ms", Destination =
[l:154{77}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_style_0d4521df11573950.cdf-ms"
18: Move File: Source = [l:254
{127}]"\SystemRoot\WinSxS\Temp\PendingRenames\61226a715a2fca017f190000ec157803.$$_ehome_createdisc_styles_ntsc_c4d1e502f2c449b1.cdf-ms", Destination =
[l:166{83}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_styles_ntsc_c4d1e502f2c449b1.cdf-ms"
19: Move File: Source = [l:272
{136}]"\SystemRoot\WinSxS\Temp\PendingRenames\c10c6b715a2fca0180190000ec157803.$$_ehome_createdisc_styles_ntsc_symphony_daaa4003771a0c78.cdf-ms",
Destination = [l:184{92}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_styles_ntsc_symphony_daaa4003771a0c78.cdf-ms"
20: Move File: Source = [l:290
{145}]"\SystemRoot\WinSxS\Temp\PendingRenames\e1cb6d715a2fca0181190000ec157803.$$_ehome_createdisc_styles_ntsc_symphony_symphony_97a43ae95f09b23
9.cdf-ms", Destination = [l:202{101}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_styles_ntsc_symphony_symphony_97a43ae95f09b239.cdf-ms"
21: Move File: Source = [l:252
{126}]"\SystemRoot\WinSxS\Temp\PendingRenames\214a73715a2fca0182190000ec157803.$$_ehome_createdisc_components_ccfb52aef0cf0151.cdf-ms", Destination =
[l:164{82}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_components_ccfb52aef0cf0151.cdf-ms"
22: Move File: Source = [l:266{133}]"\SystemRoot\WinSxS\Temp\PendingRen
2009-09-06 18:28:03, Info CSI ames\f14575715a2fca0183190000ec157803.$$_ehome_createdisc_components_tables_c2b8c3e0749098d8.cdf-ms",
Destination = [l:178{89}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_components_tables_c2b8c3e0749098d8.cdf-ms"
23: Move File: Source = [l:260
{130}]"\SystemRoot\WinSxS\Temp\PendingRenames\31a67f715a2fca0184190000ec157803.$$_ehome_createdisc_sonicresources_7e22c968e006c522.cdf-ms",
Destination = [l:172{86}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_createdisc_sonicresources_7e22c968e006c522.cdf-ms"
4. SFCDETAILS.TXT
2009-09-06 18:27:04, Info CSI 0000013b [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-06 18:27:06, Info CSI 0000013d [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-06 18:27:55, Info CSI 00000161 [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-09-06 18:28:01, Info CSI 00000163 [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-09-06 18:34:19, Info CSI 000002d4 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-06 18:34:19, Info CSI 000002d6 [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-09-06 18:34:19, Info CSI 000002d8 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-06 18:34:19, Info CSI 000002de [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-09-07 09:17:15, Info CSI 0000013b [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-07 09:17:18, Info CSI 0000013d [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-07 09:18:33, Info CSI 00000161 [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-09-07 09:18:40, Info CSI 00000163 [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-09-07 09:27:51, Info CSI 000002d4 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-07 09:27:51, Info CSI 000002d6 [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-09-07 09:27:51, Info CSI 000002d8 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-07 09:27:51, Info CSI 000002de [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-09-11 15:21:21, Info CSI 0000013f [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-11 15:21:27, Info CSI 00000141 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-11 15:22:28, Info CSI 00000161 [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-09-11 15:22:32, Info CSI 00000163 [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-09-11 15:32:04, Info CSI 000002d8 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-11 15:32:04, Info CSI 000002da [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-09-11 15:32:04, Info CSI 000002dc [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, 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-09-11 15:32:04, Info CSI 000002e2 [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
Hello, Angela
If you have a memory card reader in your computer, the error message from the Dell utility is probably just because there isn’t anything in it.
The .ini files are printer/sidebar settings and since settings change, sometimes Windows will think it was corrupted - It’s safe to ignore those two files.
Is this a laptop or desktop?
When you say you have Vista CDs, are they install CDs or recovery CDs?Are you using one of the default screen savers or a third party one?
Does this still happen frequently?What devices do you have connected to your computer? Do you have a printer, scanner, camera or external drive or anything else?
To help narrow down the cause, we can try creating another account to see if there is a weird setting or any profile corruption.
If you do not have a second account already, you can create one by going to Start, Control Panel, User Accounts and Family Safety, User Accounts, then click Manage Another Account. You may be prompted to continue. On the next screen, click Create New Account and enter the name and account type (just use the same type as your current account - most likely administrator) then click Create Account.
Since this is a problem resuming and passwords, click the account that you just created and then click Create a password to make the accounts as similar as possible.
Log out of your current account and login to the new account and try to see if you can re-create the problem or not.
We look forward to hearing back from you.
David
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think.- Hi David,
Thanks for the quick reply to my LOOONG msg.
1. Is this a laptop or desktop? Desktop Vista 64-bit home premium, 8 gb RAM sp2
2. When you say you have Vista CDs, are they install CDs or recovery CDs? The one from which I ran Startup Repair is labelled "Operating System Reinstallation DVD Windows Vista Home Premium 64-bit sp1)
3. Are you using one of the default screen savers or a third party one? default, the one that comes with OS
4. Does this still happen frequently? As I said in my first email, it started (when I got PC last Dec.) from a 1x/month occurrence to 1 - 2x/week. As I said in my post of 9/5, it happened 2x in less than 24 hours (definitely a first) after it had supposedly been fixed. It hasn't occurred since then but until a few days ago, I had my screen saver set to a very high time period before it kicked in, so I was not using screensaver at all, basically.5. What devices do you have connected to your computer? Do you have a printer, scanner, camera or external drive or anything else? Just a printer which is usually off. Network connection is a wire connection to a wireless router.
6. To help narrow down the cause, we can try creating another account to see if there is a weird setting or any profile corruption.
I did this, with an almost identical user name, admin access, and same password. However, this new account is of course missing many of the programs and settings in my old one. So this will only work as a test if I remember to log into new acct. when I'm leaving my PC for any length of time. Still that's better than leaving the PC with screensaver/password protect essentially off, which is what I've been doing since 9/5 when the problem was not only solved but seemed to be worse and was affeccting my productivity. - Sorry, I just read this over (while sitting in a tiresome, repetitive conf call.) and I realized I didn't proof well before hitting 'send".
Last line should be "was not only NOT solved but. . ."
and in #4 above, should read "(definitely a first to happen twice so fast)"
G'night Hello, Angela
To clarify, did the problem happen on the other account?
To expand, the new account is just to test for now. If the problem doesn’t happen at all using it, we can migrate all of your settings and documents over to the new account but for now we are just focusing on narrowing the possibilities down.
I should have mentioned in my last post that to quickly test if the problem persists, you can set the screen saver to activate after a minute and then just wait till it comes on to check if you are able to resume or not.
If the problem still happens under the other account, we can try doing a clean boot to check if an application or background service is interfering.
A Clean Boot will disable all non-Microsoft background services and applications temporarily. It is possible that you may not have full access to all of your programs while testing, but it can be easily restored at any time.
To do a Clean Boot, go to Start, type “msconfig” in the search box and press enter. You may be prompted to continue.
In the System Configuration Screen, go to the Services Tab, check the Hide all Microsoft Services box in the bottom left corner and then click the Disable All button.
Next, go to the Startup tab and then click the Disable All button.
Press OK, restart your computer and test if you are able to reproduce the problem or not.To restore your computer to a normal boot, simply run the “msconfig” program again and select the Normal Startup option on the General tab.
We look forward to hearing back from you with the results.
David
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think.- Hi David,
Thanks for the quick reply and the explanation about the alternative account and the Clean Boot.
At this point, I've gotten behind in my work & other projects dealing with this and really don't want to spend more time on it than I need to. So I appreciate the suggestion about setting the screensaver to 1 minute to test it quickly, but I'd rather spend less of MY time testing now, even if it means more CALENDAR time testing before we get a result.
so I will definitely get back to you with results, but as it is, I'm just challenged remembering to switch to the new alternate account when I'm leaving my PC for any length of time. I'll let you know if the problem occurs with alternate account, and if so, we can do clean boot. If not, but if it persists in my original account, then the migration. Right?
So unless you say otherwise, no news is good news from me. But no news may also mean I'm not testing real aggressively. OK?
Thanks,
Angela - What are your system specs?
- You could check wether it is locked or not.
- I did not reply to 10/15 msg as I'd given some sys specs at beginning of msg and didn't know if you'd missed that or wanted add'l specific specs or what.
For your msg today,
You could check wether it is locked or not
I do not know what you mean by 'it'. My guess is it might be covered in 8/27 msg, but w/o knowing the meaning of "it", I'm just guessing. I'm afraid I find your messages overly cryptic, as in I'm supposed to understand what you mean w/o you explicitly saying what you are asking or suggesting.
