[SOLVED] Problems with vista at startup and explorer crashing

cuda340

Member
Joined
Nov 19, 2015
Posts
11
sfc /scannow detected corrupt system files couldn't fix automatically. Beeping at startup and problems with password entry. CBS.Log windir\Logs\CBS\CBS.log

I couldn't tell if my attachment attached. I did run the tool first.
:banghead:
 
Last edited:
Am I stupid? Why can't I see my attachment anywhere? Also superfetch and host process, explorer etc... stopped working. It comes right back on after attempting to sleep it.
I will try to attach 1 more -time.
 
Let's take a look. Sorry for the delay. Please do the following. I'm having you re-run SFC so we have a fresh log.

SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Please Note:: if the file is too big to upload to your next post (or if you have issues attaching it) please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Brian, thanks for your help. The sfc scannow could not complete and the special fix tool at your site could not complete either. I also can't update service pack 1 either. I think it is a corrupt system file. I even reset the computer back to it's original settings and it helped but no taco. I made the cbs file but couldn't upload it to your site. I just tried again but I don't see it anywhere. I have ms security essentials and have run a scan with no detection's. explorer was (not responding) again too. Someone said it could be my motherboard. I think it's something that can be fixed. It started beeping at startup again as well. I attached the file. I don't know if you will get it.



Let's take a look. Sorry for the delay. Please do the following. I'm having you re-run SFC so we have a fresh log.

SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Please Note:: if the file is too big to upload to your next post (or if you have issues attaching it) please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Please upload your file to SendSpace and then just provide the link here. How many beeps do you hear at startup? Also is it a long then short or multiple short beeps? Those all mean something different so let me know. Thanks.
 
https://www.sendspace.com/filegroup/gLSnQtKmGCz13XUsG2FyAF5P2Qwaa1fW

I think I did it right. I couldn't see if it was all 3 files though. This file was made before the cmd and fixit tool failed to work the last 2 times I ran them however....
The current beeping pattern is right before the hp logo and it probably beeps about 8-10 times and then stops for 2 seconds and beeps again 3 or 4 times ... then stops. Then a screen appears that asks what os I want to use and gives me only 1 option (of course). Then it starts right up and every once in a while, has a hiccup and fails to run smoothly. It's slow too. Mahalo Brian.
 
The errors in your log are as follows.

Code:
2015-11-18 09:07:37, Info                  CSI    000005df Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_2afb4740df058c0c\settings.ini do not match actual file [l:24{12}]"settings.ini" :
  Found: {l:32 b:PF+0oMOHeSdDaSy4ZFcNhoRrk9QOY+HBWL4HP5YUMUg=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2015-11-18 09:07:37, Info                  CSI    000005e0 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, 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
2015-11-18 09:07:37, Info                  CSI    000005e1 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_354ff19313664e07\settings.ini do not match actual file [l:24{12}]"settings.ini" :
  Found: {l:32 b:f4a4oE6RZa4FZQ9vPyg3tlS0RBWPkbuQA3+d1SAOqUk=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2015-11-18 09:07:37, Info                  CSI    000005e2 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, 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
2015-11-18 09:07:37, Info                  CSI    000005e3 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_2afb4740df058c0c\settings.ini do not match actual file [l:24{12}]"settings.ini" :
  Found: {l:32 b:PF+0oMOHeSdDaSy4ZFcNhoRrk9QOY+HBWL4HP5YUMUg=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2015-11-18 09:07:37, Info                  CSI    000005e4 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, 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
2015-11-18 09:07:37, Info                  CSI    000005e5 Hashes for file member \??\C:\Program Files\Windows Sidebar\settings.ini do not match actual file [l:24{12}]"settings.ini" :
  Found: {l:32 b:PF+0oMOHeSdDaSy4ZFcNhoRrk9QOY+HBWL4HP5YUMUg=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2015-11-18 09:07:37, Info                  CSI    000005e6 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_2afb4740df058c0c\settings.ini do not match actual file [l:24{12}]"settings.ini" :
  Found: {l:32 b:PF+0oMOHeSdDaSy4ZFcNhoRrk9QOY+HBWL4HP5YUMUg=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2015-11-18 09:07:37, Info                  CSI    000005e7 [SR] Could not reproject corrupted file [ml:520{260},l:72{36}]"\??\C:\Program Files\Windows Sidebar"\[l:24{12}]"settings.ini"; source file in store is also corrupted
2015-11-18 09:07:37, Info                  CSI    000005e8 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_354ff19313664e07\settings.ini do not match actual file [l:24{12}]"settings.ini" :
  Found: {l:32 b:f4a4oE6RZa4FZQ9vPyg3tlS0RBWPkbuQA3+d1SAOqUk=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2015-11-18 09:07:37, Info                  CSI    000005e9 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, 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
2015-11-18 09:07:37, Info                  CSI    000005ea Hashes for file member \??\C:\Program Files (x86)\Windows Sidebar\settings.ini do not match actual file [l:24{12}]"settings.ini" :
  Found: {l:32 b:f4a4oE6RZa4FZQ9vPyg3tlS0RBWPkbuQA3+d1SAOqUk=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2015-11-18 09:07:37, Info                  CSI    000005eb Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_354ff19313664e07\settings.ini do not match actual file [l:24{12}]"settings.ini" :
  Found: {l:32 b:f4a4oE6RZa4FZQ9vPyg3tlS0RBWPkbuQA3+d1SAOqUk=} Expected: {l:32 b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o=}
2015-11-18 09:07:37, Info                  CSI    000005ec [SR] Could not reproject corrupted file [ml:520{260},l:84{42}]"\??\C:\Program Files (x86)\Windows Sidebar"\[l:24{12}]"settings.ini"; source file in store is also corrupted

These can safely be ignored and are falsely reported as corrupt per the following article.
https://support.microsoft.com/en-us/kb/947595

It sounds to me like you are having more of a hardware issue. I suggest that you post an inquiry in either our Windows Vista forum or our hardware forum. I wish we could do more but here in this forum we specialize in Windows Update issues.
 
Brian, thanks for your help. The sfc scannow could not complete and the special fix tool at your site could not complete either. I also can't update service pack 1 either. I think it is a corrupt system file. I even reset the computer back to it's original settings and it helped but no taco. I made the cbs file but couldn't upload it to your site. I just tried again but I don't see it anywhere. I have ms security essentials and have run a scan with no detection's. explorer was (not responding) again too. Someone said it could be my motherboard. I think it's something that can be fixed. It started beeping at startup again as well. I attached the file. I don't know if you will get it.



Let's take a look. Sorry for the delay. Please do the following. I'm having you re-run SFC so we have a fresh log.

SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Please Note:: if the file is too big to upload to your next post (or if you have issues attaching it) please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
I guess that's good news. I still am unable to install service pack 1. Could it be because service pack 2 is all ready in my program list? I could uninstall it and try again? Why won't the cmd complete? Your fix tool also would not complete. This does not seem correct. I also get 'host services stopped running' or 'superfetch'. Windows is looking for a solution.... blah blah blah...
When I made the file copy for you, my computer was acting almost normal because I had run the fix it tools and I think it worked, but when it looked as if everything had gotten installed right finally, I wanted to save it as a restore point and accidentally took it back in time, not forward. Is it possible that I need to send you a recent cbs file?
What is catroot? I was told that there is a process to eliminate the catroot files and that they could be corrupt? Thanks again for all your efforts, steve.
 
The sfc /scannow is completing, it's just telling you that there are corrupt files but as mentioned these can safely be ignored. I would post an inquiry in our hardware forum or Windows vista forum to check out the issue with the beeping you are having at bootup first. Once that's resolved, if you are having trouble installing Windows Updates you may come back here and we can take a look.
 
CMD scanned up to 89% and then the message: 'windows resource protection could not perform the requested operation' pops up ~
c:\windows\system32>
c:\windows\system32>
c:\windows\system32>

I used the MSframework fixit tool and it was also unable to repair the installing issue. It installed all the unimportant updates... just not service pack 1&2. I think the sp2 program all ready installed on this thing has different values and is named differently.
 
OK, no problem. Have the hardware guys check out the issue with the beeping you are having as that may be a serious issue. Then come back here and we'll continue.
 
Thanks again for your time Brian. I had sp1&2 installed. Then, all of a sudden, it wanted me to install them both again. I was having a keyboard sticky key and I think it could still be the beeping culprit. However, it wouldn't surprise me if the motherboard was failing. I checked the memory and it had no issues. It also wouldn't surprise me if there was still some kind of malware hiding in this *****! Have a Merry Turkey Day!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top