SFCFIX : Some corruptions could not be fixed automatically

A

Admaaaaa

Well-known member
Joined
Sep 15, 2022
Posts
109
Hi all,

Having all kinds of fun and games with my Win 8.1 installation. I accidentally restarted it (a few weeks ago) while it was in the process of shutting down and since then it's been a nightmare. For days i couldn't even get it to boot into Windows, SFC/DISM wouldn't complete, and there's no system image or restore to go back to. I've only today been able to get hold of a boot disk with the same version (exactly) that i used to install it initially.

I've finally been able to get it to boot into Windows and into my account but Explorer.exe is corrupted and constantly resets itself (every 2/3 seconds), i was able to get into event viewer and it said that Explorer was indeed the problem but that Windows.ui.search.dll was a problem as part of it.

I tried a variety of offline and online commands to try and fix the filestore but nothing as yet has worked. I came across the SFC Fix program and ran it over night but (as in the title) it found issues. The sfcfix.txt file is listed below.





SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-09-14 23:50:05.970
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.




AutoAnalysis::
WARNING: Performed DISM repair due to manifest damage on component "amd64_windows-defender-management.resources_31bf3856ad364e35_6.3.9600.18603_en-gb_bcb974286aefd014". See CBS logfile for more details.


CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.3.9600.20227_none_2821e1104bce060b\vmms.exe
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-hyper-v-vstack-vmwp_31bf3856ad364e35_6.3.9600.20227_none_26cc67b64ca9f8c0\vmwp.exe
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.3.9600.19409_none_67b96291b851af83\AudioEng.dll
CORRUPT: C:\WINDOWS\winsxs\wow64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.3.9600.19409_none_720e0ce3ecb2717e\AudioEng.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-explorerframe_31bf3856ad364e35_6.3.9600.19062_none_b34ebea847b9d82c\ExplorerFrame.dll
CORRUPT: C:\WINDOWS\winsxs\wow64_microsoft-windows-explorerframe_31bf3856ad364e35_6.3.9600.19062_none_bda368fa7c1a9a27\ExplorerFrame.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-ui-search_31bf3856ad364e35_6.3.9600.20237_none_e69242b70feb6321\Windows.UI.Search.dll
CORRUPT: C:\WINDOWS\winsxs\wow64_microsoft-windows-ui-search_31bf3856ad364e35_6.3.9600.20237_none_f0e6ed09444c251c\Windows.UI.Search.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-webservices_31bf3856ad364e35_6.3.9600.19028_none_ff7f4eea0275596a\webservices.dll
CORRUPT: C:\WINDOWS\winsxs\x86_microsoft-windows-webservices_31bf3856ad364e35_6.3.9600.19028_none_a360b3664a17e834\webservices.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-zipfldr_31bf3856ad364e35_6.3.9600.19060_none_68d5feed0933453f\zipfldr.dll
CORRUPT: C:\WINDOWS\winsxs\wow64_microsoft-windows-zipfldr_31bf3856ad364e35_6.3.9600.19060_none_732aa93f3d94073a\zipfldr.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_system.data_b77a5c561934e089_4.0.9696.17240_none_22d216452e073617\System.Data.dll
CORRUPT: C:\WINDOWS\winsxs\x86_system.data_b77a5c561934e089_4.0.9696.17240_none_6a7f4d1c42835f1d\System.Data.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_windows-storage-applicationdata-winrt_31bf3856ad364e35_6.3.9600.19670_none_d535d1e8aa76c3f5\Windows.Storage.ApplicationData.dll
CORRUPT: C:\WINDOWS\winsxs\x86_windows-storage-applicationdata-winrt_31bf3856ad364e35_6.3.9600.19670_none_79173664f21952bf\Windows.Storage.ApplicationData.dll
CORRUPT: C:\WINDOWS\winsxs\msil_miguicontrols_31bf3856ad364e35_6.3.9600.19399_none_42e28a4358388fd2\MIGUIControls.dll
CORRUPT: C:\WINDOWS\winsxs\msil_system.core_b77a5c561934e089_4.0.9696.17240_none_69e573d242f74d99\System.Core.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-fax-common_31bf3856ad364e35_6.3.9600.20474_none_fd577bab3dad11e8\FXSRESM.dll
CORRUPT: C:\WINDOWS\winsxs\wow64_microsoft-windows-fax-common_31bf3856ad364e35_6.3.9600.20474_none_07ac25fd720dd3e3\FXSRESM.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-ieframe_31bf3856ad364e35_11.0.9600.20477_none_518e1382aac44c68\ieframe.dll
CORRUPT: C:\WINDOWS\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_11.0.9600.20477_none_5be2bdd4df250e63\ieframe.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-directx-warp10_31bf3856ad364e35_6.3.9600.19176_none_db2e8c4b2a99ce47\d3d10warp.dll
CORRUPT: C:\WINDOWS\winsxs\x86_microsoft-windows-directx-warp10_31bf3856ad364e35_6.3.9600.19176_none_7f0ff0c7723c5d11\d3d10warp.dll
CORRUPT: C:\WINDOWS\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.20475_none_4e9e27aadc6cc357\intelppm.sys
CORRUPT: C:\WINDOWS\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.20475_none_4e9e27aadc6cc357\amdk8.sys
CORRUPT: C:\WINDOWS\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.20475_none_4e9e27aadc6cc357\amdppm.sys
CORRUPT: C:\WINDOWS\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.20475_none_4e9e27aadc6cc357\fxppm.sys
CORRUPT: C:\WINDOWS\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.3.9600.20475_none_4e9e27aadc6cc357\processr.sys


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 33
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.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-09-15 03:19:38.251
----------------------EOF-----------------------








I see from other posts that the corruptions found aren't necessarily the end of the road. Is there a 'next step' that anyone can suggest?
 
Hello and welcome,

Right-click the Start button and select Command Prompt (administrator).
When command prompt opens, copy and paste the following command into it, then press enter.

Code: 
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
Note: if the file is too big to upload to your next post please upload via a service such as Gofile or WeTransfer and just provide the download link.
 
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
    myjIXnC.png
    SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.
 
I'm unable to do anything outside of command prompt (explorer closes every few seconds, taking all windows with it) can this be combined through a command?
 
I assume you already downloaded the file SFCFix.zip successful and saved the file on your desktop.

Right-click the Start button and select Command Prompt (administrator).
When command prompt opens, copy and paste the following commands into it, press enter after each.

Code: 
CD C:\Users\<username>\Desktop
Code: 
SFCFix C:\Users\<username>\Desktop\SFCFix.zip

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Attach that file to your next reply.
 
Well that seems to have solved a few issues. The flashing and crashing of explorer.exe has been fixed but there are other issues. I'm running another scan now
 

Attachments

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
    myjIXnC.png
    SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.
 

Attachments

Thanks for your continued help Peter. I've run that fix and restarted the desktop. It's very much functioning back to normal, i'll run dism/sfc again just to see if it picks anything else up.
 
SFC is coming back clear now, so that's ticked off. But 2 issues persist, DISM is failing to download the files it needs (i've attached the DISM) and the other thing is, in event viewer i'm getting an application crash for sdiagnhost.exe (every time i boot up windows).

I appreciate this is a SFC fix forum but any suggestions would be much appreciated.
 

Attachments

I appreciate this is a SFC fix forum but any suggestions would be much appreciated
Click to expand...
We can continue here.

ChkDsk Scan
  • Right-click the Start button and click Commandprompt (Run as administrator).
  • A window appears. Typ CHKDSK and press the enter key.
  • Wait until CHKDSK is finished.
  • Download ListChkdskResult.exe by SleepyDude and save it on your desktop.
  • Rightclick
    58a60a47ed1bd-ListChkdskResult.PNG
    ListChkdskResult.exe and click Run as administrator. On completion the tool will save a textfile called ListChkdskResult.txt on your desktop.
  • Attach this text file to your next reply.
 
It's come back all clear. Is there anything additional to this i can try? For the DISM issue i've seen this link to try and fix it, but not attempted it. Is it something you would recommend trying?
 

Attachments

It's come back all clear.
Click to expand...
No, it's not all clear. These lines need further action:
Code: 
Cleaning up instance tags for file 0x1d1e2e.
1768 KB in bad sectors.
Please do following.

Right-click Start then click Command-prompt (administrator).
When command prompt opens, copy and paste the following command into it, press enter afterwards.

Code: 
chkdsk c: /f
At the question "Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)", press Y.
Restart the system.

Do not press any key during the restart. This will allow CHKDSK to start.
Wait for this to complete. Please note that this may take several hours. Let it run even if it looks like the process has stopped!
On completion, the system will restart automatically.
 
So i tried that a few times over the past few weeks, it would get to 13% then (after a good 8+ hours) would crash. I've run it again a few hours ago, it shot past 13% up-to close to 50%, i left it and came back 20 minutes ago and it's crashed again, won't load into Windows (Window's was unable to start) so i've done a system restore (to a point on Friday evening) that's currently running.

One of the Event Viewer logs i saw earlier this week (when i was able to get into Windows) was a "Bad Cluster" error for disk. I imagine that's a pretty clear sign that the harddisk itself needs replacing?
 
Are you sure you used only the /f option ?

Lets have a look at the harddisk.

Download
51ab99ff51ec9-CrystalDiskInfo.png
CrystalDiskInfo.zip and save it on your desktop.
Extract the .zip file into a new folder.
In this new folder, run the tool DiskInfo.
When the tool is finished, it will show some information about the hard disc.
Note: Resize the window so that all information is visible.
Take a screenshot. Read this on how to take a screenshot.
Upload the image file to a file-sharing site and post the download link.
 
Even though it said that the restore couldn't be completed, it did allow me back into Windows. Which seems to be back where it was before i it crashed after the chkdsk.

Below is the Crystal Disk info.




crystalDisk_results.jpg
 
This disk is more than 7.5 years up and running. Make sure to backup all your important data.
Please perform a fresh chkdsk scan as you did in message #14 and provide the log.
 
Yes, it is old. When i starting using the machine (it was my work machine when i was in an old job), the desktop itself has been used since 2011.


Do you mean a normal chkdsk or attempt chkdsk c: /f again?
 
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