[SOLVED] Sfc /scannow could not start the repair service

Good morning Brilliant Brian, techs ,and members I am ready to work with you guys today to solve these annoying computer problems. Same set up no let up. I am ready:wave:
 
Good morning sysnative forum looking too hear from you today I have been waiting for instructions for four days now.
 
after factory reset I still have a few files that need to be corrected and maybe a update problem that keeps trying to update the checksur log says no error here is the sfc log
 

Attachments

Carl, the issue you have being reported in the logs is a known issue and a false positive. You've had this previously. See this.

Code:
2016-10-26 08:32:12, Info                  CSI    000002d7 [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
 
Okay the side bar is an inherent false positive with vista I thought maybe something else was going on with that. my updates were installing now it is on a continuing loop checking for updates and it is increasing the cpu usage again we been through that one before. once you give me the the update to install like you have once gave before to solve this issue then i will be straight and I will create me a specific restore point and back up my registry and i will be good. and by the way i ran the checksur with no errors
 
The same update updated but it has been two hours now and it keep checking for updates, it's like old man river, just keeps rolling along. I don't remember the checking for updates took this long after the update updated in the other post.
 
The old fix is not correcting the new problem 4 of the 5 updates updated and the other one was not for my system. The high cpu usage and checking for updates loop continue. we are one update way from solving this. I have faith in your skills.
 
Hello Brian it looks like that one is not the one everything is still the same so far.
 
I didn't but now I will install the other one since you brought it to my attention.
 
we are not there yet the same loop and high cpu usage is still there at this time
 
checking for updates hasn't stop checking in more than 18 hours and it is still checking. waiting for the next step to solve this windows update dilemma.
 
endless over 24 i stop counting ever since thread #154 and that was about 3pm more that a day and a half ago
 
Back
Top