Solved SFCFix

[glachance]

Hello Noel. Thank you so much for providing this much needed service. I almost managed without any help but by the time I found the posts in wich the files are needed were, the zip files from your onedrive account were either gone or had changed to contain completely different stuff.

Thanks again

 

[Layback Bear]

Please don't use Noel repairs for other computers. Each computer problems are different.

Just wait for Noel to give exact instruction for your computers needs with this problem.

 

[GokAy]

Run in cmd:

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\desktop\sfcdetails.txt"

and attach the sfcdetails.txt to your next post.

 

[NoelDP]

Pleasefollow the WindowsUpdate Posting Instructions and postthe requested data



If thefile is too large (8MB compressed), remove the older CBSPersist cab files untilthe final file is below the limit - you can always post them separately afterzipping them. (the forum doesn't allow the upload of bare CAB files, for anumber of reasons)



Pleasealso post the C:\Windows\windowsudpate.log file

 

[glachance]

update

Sorry, I should have gone through the process instead of trying to be a mr smartypants (? i think you say in english?)

I got confused as to where in the process I was supposed to be, so I ran "sfc /scannow" so you would get something interesting in cbs.log. Gathered everything you asked, then ran SCFFix.exe and zipped those results as well. (sorry I know there is a proper order to these things, I just got a little nervous all of a sudden). I'll follow the next instructions to the letter.

 

[NoelDP]

Both SFC and CheckSUR agree that the only problems that need to be addressed are these...

2015-07-07 16:55:52, Info                  CSI    00000304 [SR] Repairing 1 components
2015-07-07 16:55:52, Info                  CSI    00000305 [SR] Beginning Verify and Repair transaction
2015-07-07 16:55:52, Info                  CSI    00000306 [SR] Cannot repair member file [l:22{11}]"msvcr90.dll" of Microsoft.VC90.CRT, Version = 9.0.30729.6161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, file is missing
2015-07-07 16:55:52, Info                  CSI    00000307 [SR] Cannot repair member file [l:22{11}]"msvcp90.dll" of Microsoft.VC90.CRT, Version = 9.0.30729.6161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, file is missing
2015-07-07 16:55:52, Info                  CSI    00000308 [SR] Cannot repair member file [l:22{11}]"msvcm90.dll" of Microsoft.VC90.CRT, Version = 9.0.30729.6161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, file is missing
2015-07-07 16:55:52, Info                  CSI    0000030a [SR] Repair complete

(The other errors that you see in CheckSUR are normal and can be ignored, usually)

I'll post a fix tomorrow - it's past my bedtime now!

 

[glachance]

Thank you!

Tomorrow is fine. Have a good night.

One day I'll find out why I cant just reinstall vcredist2008x32 and x64 and have those damm dlls replace the absent/corrupt ones in winsxs. It's soooo frustrating.

 

[NoelDP]

I've created a folder - gccaa.zip - to my OneDrive at Noel's OneDrive

Please open it and download the contained SFCFix.zip file - save it to the same location as you have the SFCFix.exe file,. but do NOT extract the content

Open the SFCFix location in Windows Explorer - and drag the SFCFix.zip file over onto the SFCFix.exe file - this should force SFCFix to run the file

It will create a new log file - please upload that.

Now run the CheckSUR tool again (it may take a while), and SFC /SCANNOW

Post the new CheckSUR.log file, and the CheckSUR.persist.log file, and CBS.log file

 

[glachance]

Will you look at that! Thank you so much. No checksur files were created during the sfc /scannow. All I got was this lovely message at the end :

Début de l'analyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de l'analyse du système.
La vérification 100% est terminée.
Le programme de protection des ressources Windows n'a trouvé aucune violation d'intégrité.

 

[NoelDP]

OK - now run CheckSUR again - that should also come back clean

 

[glachance]

Clean as a whistle (welll exept the usual 4). Thanks again

(Wow i've been watching so much american tv I actually know expressions now. Even when they make no sense whatsoever. What happened to the whistle? Did someone swallow it? Is that why it gets so clean? I would argue that the whistle is unlikely to come out clean at all.)

 

[NoelDP]

Now do a Check for Updates, and attempt to install only the oldest update found.
If it goes in OK, try the rest.
If it fails, post the C:\Windows\windowsupdaet.log file.