[SOLVED] Windows 7 Professional SP1 x64 - SFCFix fails to repair corrupt files

Berbe · May 22, 2020

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-05-22 07:07:19.799
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component prnep00b.inf and file Amd64\EP0NOE18.DLL. File is reported as corrupt by SFC.
CORRUPT: Amd64\EP0NOE18.DLL of component prnep00b.inf.

CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-wmspdmoe_31bf3856ad364e35_6.1.7601.19091_none_57f14dc586c8b09d\WMSPDMOE.DLL
CORRUPT: C:\Windows\winsxs\msil_system.windows.forms_b77a5c561934e089_6.1.7601.18763_none_054d4eab00293a08\System.Windows.Forms.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-directx-direct3d10.1_31bf3856ad364e35_7.1.7601.16492_none_4348f88492fd6ee6\d3d10_1core.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-themeui_31bf3856ad364e35_6.1.7601.24260_none_87554075930d60b0\themeui.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_01c9581e60cbee58\MFC90JPN.DLL
CORRUPT: C:\Windows\winsxs\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90JPN.DLL

SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 7
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 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2020-05-22 07:10:19.369
----------------------EOF-----------------------

I ran FRST64 beforehand, but no fixlist.txt file was generated: I concluded that no infection was found.

Sadly, none of the files listed above are part of the original install DVD I have, and so it seems those files came from Windows Update packages... but it seems SFCFix did not find its way around them.

EP0NOE18.DLL seems in an especially worrying state...

Any idea on how to solve them?

Attached are the logs from the latest runs of CheckSUR & SFC

PeterJ · May 23, 2020

Hello and welcome,

I ran FRST64 beforehand, but no fixlist.txt file was generated: I concluded that no infection was found.

FRST will never generate a file called fixlist.txt. That file is created manually by a helper and provided to you. FRST can be used for virus/malware removal but not as a stand-alone scanner.

Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

Download the file SFCFix.zip and save it on your desktop.
Save any work you have open, and close all programs.
Drag the SFCFix.zip file over the

SFCFix.exe executable and release it.
SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Open the file, then copy and paste its content in your next reply.

Berbe · May 23, 2020

This did the trick! Thank a lot!
As requests the SFCFix.log file is attached.

I ran a subsequent sfc /scannow check after reboot (I did one before reboot by mistake, still triggering the same errors).
No error was found anymore! You'll find the new CBS.log file attached too. It still contains some verbose output about files being moved around. Are these backups being made from clean files? In any case, is there anything left to worry about?

If it's not intrusive to ask, what is your source for any random clean Windows file? Is there a way to extract them from original WSU packages? How do you find specific WSU updates related a specific file version?

PeterJ · May 23, 2020

Please attach the file C:\Windows\Logs\CBS\CbsPersist_20200523212954.cab to your next reply.

Berbe · May 23, 2020

I unfortunately deleted all the .cab files in the folder.

PeterJ · May 23, 2020

Shutdown and restart the machine.
Check Windows Update again and report the result.
If it fails, attach the zipped cbs.log to your next reply.

Berbe · May 23, 2020

The only update I got was the usual daily KB2310138 - Security Essentials (version 1.315.1303.0)

Ran sfc /scannow again, still no integrity problem anymore (as I confirmed before). You'll find the latest CBS.log file attached.

I tried recovering deleted files but the CbsPersist_20200523212954.cab one you requested could not be restored.

PeterJ · May 24, 2020

Great. Your posting in message #3 confused me a bit.

It still contains some verbose output about files being moved around.

You can ignore that.

If it's not intrusive to ask, what is your source for any random clean Windows file?

Google it or extract from another machine. You may need to download the KB it contains.

Can we close this thread or are there remaining issues ?

Berbe · May 24, 2020

PeterJ said:
Great. Your posting in message #3 confused me a bit.

Sorry about that.

PeterJ said:
Google it or extract from another machine. You may need to download the KB it contains.

Well. I tried searching for the files to no avail. Sometimes nothing poepped up, or in the wrong versions... + hard to trust files coming from sources nothing indicate they are trustworthy. That is how problems can even start...
I usually try to be self-sustaining before bothering others when that fails

If you got a specific trustworthy source, I would be glad to know about it :)

PeterJ said:
Can we close this thread or are there remaining issues ?

Yes! Many thanks again!
Is there a way I can offer some help in return?

PeterJ · May 24, 2020

Don't mess with system files if you don't know what you are doing. Better seek help.
The Microsoft Update Catalog can be used to get updates manually.
How to expand and extract files is learned in the Windows Update Academy on this forum: Want To Learn How to Fix Windows Update Issues? Join The Sysnative Windows Update Academy!

Is there a way I can offer some help in return?

You can reply in other sections if you like and/or make a donation here: Donate to Sysnative

Berbe · Aug 13, 2020

Some more problems lead to some more corruption...

Attached is the CBS.log file

PeterJ · Aug 13, 2020

Follow the instructions below please.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

Download the attachment SFCFix.zip and save it on your desktop.
Save any work you have open, and close all programs.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the computer.
Run sfc /scannow in a elevated commandprompt and report the result.
If it fails, attach the zipped cbs.log to your next reply.

Berbe · Aug 13, 2020

Here are the results of both attempts, failing on the 3rd file.

Berbe · Aug 13, 2020

Scratch that: after rebooting the computer & doing another scan: no more corrupted file was to be found.

Thanks again!

PeterJ · Aug 14, 2020

Great. All problems solved ?

Berbe · Sep 12, 2020

Last time, no... but, still having had "disk" problems, I kept having had BSoD.

After having changed harddisks (yielded no results), solved the problem 2 weeks ago by dismantling the PC and fiddling with the SATA cable... Since then: not a single crash!
F4 7A BSoD are no longer a thing.Root cause identifiend & seemingly fixed.

However... I would require your benevolent help one last (I hope) time.

PeterJ · Sep 12, 2020

Here you go.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

Download the attachment SFCFix.zip and save it on your desktop.
Save any work you have open, and close all programs.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the computer.
Run sfc /scannow in a elevated commandprompt and report the result.
If it fails, attach the zipped cbs.log to your next reply.

Berbe · Sep 12, 2020

Worked like a charm!

Thanks... again.

PeterJ · Sep 12, 2020

Great. Can we mark this thread as solved ?

[SOLVED] Windows 7 Professional SP1 x64 - SFCFix fails to repair corrupt files

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Member

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst