[SOLVED] too many errors after sfc checking. Also used SFCFixVersion2

S

spydermia

Member
Joined
Nov 3, 2013
Posts
17
Location
Argentina
Hi Team !

Well, I also have the same problem as many others: too many system file errors, having checked with sfc and then with sfcfixversion2 as you asked to others (I was reading some threads)
So, I'm attaching the SFCFix.txt and also a gpedit.png screenshot. This is one of the reasons why I decided to run sfc: The gpedit.msc screen is empty ! and the other reason is that I get a 0xc00007b error when I try to run photoshop lightroom 5.2.

So, I hope you can help me with these.

Best regards.
Ariel
 

Attachments

  • SFCFix.txt
    SFCFix.txt
    47.3 KB · Views: 14
  • gpedit_issue.png
    gpedit_issue.png
    42.2 KB · Views: 8
Hi,

Please can you run the SFC /Scannow command again from an elevated command prompt, and upload your CBS folder to your next post. SFCFix has done a good job at repairing some files, but there are some more to go.

Export CBS folder


  1. Click the Start button :startorb: then click Computer.
  2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
  3. Find and double click on the Logs folder.
  4. Right-click on the CBS folder, and select Copy.
  5. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
  6. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
  7. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.
  8. Attach this new file to your next post.


Regards,
Stephen

Notes to self:

Read More:
 
Hi Stephen,
Well, I've done what you asked.
The strange thing I can see in the sfcfix log that I sent yesterday, is that the "source" used for the restored files was F: On drive F: I have a very old copy of Windows 7, so, I don't know if the restored files are going to be ok.
 
Hi,

Sorry to be a pain! Could you please run SFC for one final time please, because it repaired a load of files, resulting in a messy log file! I haven't been doing this kind of thing (SFC corruptions) for very long, so really need a nice neat log file to work from. There are also a couple of interesting things in the log I want to see if they occur in another run of SFC.

So could you please run SFC /scannow once more please and upload the CBS folder again.

Sorry to be a pain!

Regards,
Stephen
 
Hi,
ok Stephen, don't worry about it, it's not a problem.
The thing is that the file is getting bigger every time ! :(

I don't really know if it's repairing or not....is doubtful...

Anyway, here is the file. I only uploaded the cbs.log, the others didn't change.

If you think I should run the sfc again, just tell me, no problem.

Thanks for now.


Ariel
 

Attachments

Hi again,

Thanks for doing that! Yeah, the log is getting bigger and bigger, because it is appending the latest log to the bottom of the old one. As a result, it grows and grows until Windows decided to archive it.

However, it is quite a long log, and may require a little while for me to source all the replacement files.

I may post fixes in stages as I source groups of files.

Regards,
Stephen
 
Hi,

I am so sorry about the wait.

I am currently awaiting a response from my instructor on your log, hence the wait.

If you would like to go down the route of a reinstall, we have a tutorial on how to do a repair install, which will reinstall the OS whilst leaving your files untouched. https://www.sysnative.com/forums/wi...-install-windows-windows-7-windows-vista.html

If you would like to see if I can put a repair together, I'll let you know what my instructor says.

Regards,
Stephen
 
Ok Stephen, I'm sorry, I'll wait some more time, because I would prefer not to re-install the OS.
Thanks for your patience.
 
Hi,

Heard back from my instructor yesterday.

For some reason, SFC is producing a different log style than it normally does, and neither of us are sure why. This means I need another file.

Export COMPONENTS Hive

Please download RegBak (by AceLogix Software) from the following link and save it to your Desktop. http://acelogix.com/downloads/regbak.zip


  • Right-click on regbak.zip then select Extract all... and extract the files to your Desktop
    For 32-bit (x86) editions of Windows, double-click on regbak.exe
    For 64-bit (x64) editions of Windows, double-click on regbak64.exe​

    If you are unsure whether you have x86 or x64 Windows, see here
  • Without changing any options, click Next. RegBak will now backup all of your registry hives.
  • Navigate to C:\Windows\RegBak\{Date}\ and copy the COMPONENTS file (it has no extension) to your Desktop
  • Upload this file for me to analyse please, using any of the following options:
    Microsoft Skydrive
    Dropbox
    SendSpace (or any other file-sharing site of your preference)​

Kind regards,
Stephen
 
Hi,

Unfortunately no COMPONENTS file is present on your SkyDrive. Please delete the other files in that folder - SOFTWARE, DEFAULT etc, they are not needed. I will try to get the COMPONENTS file later (sometimes RegBak fails as it did in this situation). However, before, I would like you to run SFCFix v2 again.


  1. Download SFCFix.exe and save this to your Desktop.
  2. Save any open documents and close all open windows.
  3. Double click on SFCFix.exe to open it.
  4. Follow all on screen instructions and upon completion, a file should be created on your Desktop: SFCFix.txt.
  5. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please.


Regards,
Stephen
 
Hi, sorry....but, which are the components files ?? There are several files and I think they are part of the program RegBak, and I've understood you needed the ones with no extension, that's why I sent to you those files.
So, I don't realize what you need. I also have a User folder into RegBak folder.
Oh ! if you meant that there would have to exist a file with the name COMPONENTS, I tell you, no! it doesn't exist such a file.

(sorry about my poor english)

I'll be running sfcfix again in a while....
 
Hi,

Don't worry. :) I did mean a file with the name COMPONENTS, but since that file doesn't exist in the RegBak folder, then it wasn't backed up by RegBak. This happens sometimes, so I do have alternative instructions for getting it.

However, for now, don't worry about it. Just run SFCFix again and post the log in your next post. That's all I need for now.

Regards,
Stephen
 
Hi, this is the sfcfix.txt content:


SFCFix version 2.0.2.1 by niemiro.
Start time: 2013-11-13 23:03:29.045
Not using a script file.


AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.0.2.1 by niemiro has completed.
Currently storing 33 datablocks.
Finish time: 2013-11-13 23:04:03.376
----------------------EOF-----------------------
 
Hi Tom, here is the content of the file you asked me:


Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 22.0
2013-11-20 20:50
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Payload File Missing 0x00000000 qwavedrv.sys amd64_microsoft-windows-qwave_31bf3856ad364e35_6.1.7600.16385_none_b49f0b68626c0d4f 
(f) CSI Payload File Missing 0x00000000 gameux.dll.mui amd64_microsoft-windows-gameexplorer.resources_31bf3856ad364e35_6.1.7600.16385_es-es_6a65a32788e2b710 
(f) CSI Payload File Missing 0x00000000 GCDEF.dll.mui amd64_microsoft-windows-d..rectinput.resources_31bf3856ad364e35_6.1.7600.16385_es-es_0904bc5fca096360 
(f) CSI Payload File Missing 0x00000000 oledb32r.dll.mui amd64_microsoft-windows-m..oledb-rll.resources_31bf3856ad364e35_6.1.7600.16385_es-es_d3391b84138f461f 
(f) CSI Payload File Missing 0x00000000 gpedit.dll.mui amd64_microsoft-windows-g..in-gpedit.resources_31bf3856ad364e35_6.1.7600.16385_es-es_60eecb3224301366 
(f) CSI Payload File Missing 0x00000000 hdwwiz.exe.mui amd64_microsoft-windows-legacyhwui.resources_31bf3856ad364e35_6.1.7600.16385_es-es_acd574bd5394c981 
(f) CSI Payload File Missing 0x00000000 hdwwiz.cpl.mui amd64_microsoft-windows-legacyhwui.resources_31bf3856ad364e35_6.1.7600.16385_es-es_acd574bd5394c981 
(f) CSI Payload File Missing 0x00000000 g711codc.ax.mui amd64_microsoft-windows-tapi3.resources_31bf3856ad364e35_6.1.7600.16385_es-es_199d26f6b94b852a 
(f) CSI Payload File Missing 0x00000000 gpprnext.dll.mui amd64_microsoft-windows-p..ooler-ppc.resources_31bf3856ad364e35_6.1.7600.16385_es-es_568a3676e9cb435f 
(f) CSI Payload File Missing 0x00000000 rasacd.sys amd64_microsoft-windows-rasautodial_31bf3856ad364e35_6.1.7600.16385_none_6bcef05d7f04260a 
(f) CSI Payload File Missing 0x00000000 certenc.dll x86_microsoft-windows-certutil_31bf3856ad364e35_6.1.7600.16385_none_b55b5e1094b0283d 
(f) CSI Payload File Missing 0x00000000 FXSUTILITY.dll.mui amd64_microsoft-windows-f..lications.resources_31bf3856ad364e35_6.1.7600.16385_es-es_701a185e95e0dd14 
(f) CSI Payload File Missing 0x00000000 rrinstaller.exe.mui amd64_microsoft-windows-m..oundation.resources_31bf3856ad364e35_6.1.7600.16385_es-es_ea6967d5d5c25c68 
(f) CSI Payload File Missing 0x00000000 mfpmp.exe.mui amd64_microsoft-windows-m..oundation.resources_31bf3856ad364e35_6.1.7600.16385_es-es_ea6967d5d5c25c68 
(f) CSI Payload File Missing 0x00000000 mferror.dll.mui amd64_microsoft-windows-m..oundation.resources_31bf3856ad364e35_6.1.7600.16385_es-es_ea6967d5d5c25c68 
(f) CSI Payload File Missing 0x00000000 mf.dll.mui amd64_microsoft-windows-m..oundation.resources_31bf3856ad364e35_6.1.7600.16385_es-es_ea6967d5d5c25c68
Summary:
Seconds executed: 875
 Found 16 errors
  CSI Payload File Missing Total count: 16

Thanks
 
Last edited by a moderator:
Hi spydermia,

Let's fix a few of these whilst I source copies of the rest:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u/16537616/Fixes/SFCFix/Scripts/spydermia/SFCFix.zip

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.
 
You must log in or register to reply here.

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

Back
Top