SFCFix crash upon initalizing SFC corruption

maxpeen · Jun 27, 2019

Help! Can't post a thread. Creat/upload no problem but no possibility to post. please advice (content here below)

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

--------------

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-06-22 22:25:53.462
Microsoft Windows 10 Build 18362 - amd64
Not using a script file.

SFCFix version 3.0.2.1 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2019-06-22 22:25:59.021
----------------------EOF----------

20190622-CBS.zip

Sysnative Windows Update · Jun 27, 2019

Hello and welcome!

Due to the precise nature of your corruption, you will receive help from a user named writhziden. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.

maxpeen · Jun 27, 2019

Thanks much, strange fact is it was running the first time (thereafter i did perform a re-install of the program). We'll patiently await, PC is functional however some strange behavour (such as MMC for eventviewer does not work, but that is clearly visible in the logs). Tried to initate that manually but never worked. Upgrade to 1903 also did not help I'll keep watching here, thanks much.

writhziden · Jun 27, 2019

Hello, and welcome to Sysnative Forums. Thank you for your patience while we analyzed your files. Below are the recommended steps to begin the process for fixing the corruption found on your system.

Step 1
Run SFCFix with the included SFCFix.zip archive

WARNING! The following fix is specific to the user's system in this thread only and may be harmful to apply to another system. If you came across this thread and have a similar issue, start your own thread by following the Windows Update Forum Posting Instructions

Download using the link to SFCFix.zip (see the next step for the link) and save it on your desktop.
LINK -----> SFCFix.zip (attachment also at the bottom of this post)
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

Click on the Start button/screen and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator. Allow any User Account Control box that appears.
When the command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, and press enter.

sfc /scannow
Once the command finishes, if you see "Windows Resource Protection did not find any integrity violations" then check if your problems are fixed with Event Viewer. If issues still exist with Event Viewer, or if you see another message from sfc /scannow, proceed to Step 3

Step 3
Export/Upload CBS log file
You only need to do this if sfc /scannow still reported corruption or Event Viewer still has MMC issues:

Read More:

What to do if your CBS log file is too large to upload

Read More:

maxpeen · Jun 28, 2019

Muchas Gracias, will either perform this today or this weekend and revert back.

maxpeen · Jun 28, 2019

1. first it failed with this:

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-06-28 20:06:33.173
Microsoft Windows 10 Build 18362 - amd64
Using .txt script file at C:\Users\XXXXXX\Downloads\SFCFix.txt [1]




PowerCopy::
Failed to find any content under directory "\WinSxS" in line ""\WinSxS" C:\WINDOWS\WinSxS [DIR]".
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-06-28 20:06:33.179
Script hash: 2GOD7t/jkrirFXQ4NQ+z7xcg9YoZeChViOPxdJSDTDw=
----------------------EOF-----------------------

2. i changed the path to the actual path in the txt file than it ran with the following output

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-06-28 20:07:40.683
Microsoft Windows 10 Build 18362 - amd64
Using .txt script file at C:\Users\Louise\Downloads\SFCFix.txt [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\wow64_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.18362.1_none_1401e6d840a000f1\gptext.dll
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\wow64_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.18362.1_none_aae446e316809960\gpedit.dll
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\wow64_microsoft-windows-fde_31bf3856ad364e35_10.0.18362.1_none_84be15c40d4462b4\fde.dll
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\wow64_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.18362.1_none_bc67ac8b025785ba\fdeploy.dll

Successfully copied file C:\Users\Louise\Downloads\WinSxS\wow64_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.18362.1_none_1401e6d840a000f1\gptext.dll to C:\WINDOWS\WinSxS\wow64_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.18362.1_none_1401e6d840a000f1\gptext.dll.
Successfully copied file C:\Users\Louise\Downloads\WinSxS\wow64_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.18362.1_none_aae446e316809960\gpedit.dll to C:\WINDOWS\WinSxS\wow64_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.18362.1_none_aae446e316809960\gpedit.dll.
Successfully copied file C:\Users\Louise\Downloads\WinSxS\wow64_microsoft-windows-fde_31bf3856ad364e35_10.0.18362.1_none_84be15c40d4462b4\fde.dll to C:\WINDOWS\WinSxS\wow64_microsoft-windows-fde_31bf3856ad364e35_10.0.18362.1_none_84be15c40d4462b4\fde.dll.
Successfully copied file C:\Users\Louise\Downloads\WinSxS\wow64_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.18362.1_none_bc67ac8b025785ba\fdeploy.dll to C:\WINDOWS\WinSxS\wow64_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.18362.1_none_bc67ac8b025785ba\fdeploy.dll.

Successfully restored ownership for C:\WINDOWS\WinSxS\wow64_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.18362.1_none_1401e6d840a000f1\gptext.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\wow64_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.18362.1_none_1401e6d840a000f1\gptext.dll
Successfully restored ownership for C:\WINDOWS\WinSxS\wow64_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.18362.1_none_aae446e316809960\gpedit.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\wow64_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.18362.1_none_aae446e316809960\gpedit.dll
Successfully restored ownership for C:\WINDOWS\WinSxS\wow64_microsoft-windows-fde_31bf3856ad364e35_10.0.18362.1_none_84be15c40d4462b4\fde.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\wow64_microsoft-windows-fde_31bf3856ad364e35_10.0.18362.1_none_84be15c40d4462b4\fde.dll
Successfully restored ownership for C:\WINDOWS\WinSxS\wow64_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.18362.1_none_bc67ac8b025785ba\fdeploy.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\wow64_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.18362.1_none_bc67ac8b025785ba\fdeploy.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2019-06-28 20:07:41.308
Script hash: ExCOWrqz/BMig6c4zt45CvSmHqKxlaeNZZbK567zfH4=
----------------------EOF-----------------------

3. than i ran sfc /scannow under admin privileges following output came, along with the logfile (attached)

Code:

Microsoft Windows [Version 10.0.18362.175]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>

4. Final question: could this have been the reason of faulty and unstable operating system, or no change at all?

maxpeen · Jun 28, 2019

sorry, just after pasting i re-read that i should not have uploaded the log...

Still the question remains (4).

maxpeen · Jun 28, 2019

\

meanwhile snap-in event viewer still crashes

writhziden · Jun 28, 2019

Yes, the corruption occurred in a key component of Windows, so it is possible it was causing the unstable behavior you were seeing.

For the MMC issue, I recommend the following procedure:

Click on the Type here to search text box
Type Check for updates into the text box
Click on the Check for updates (System settings) option
Scroll down to Additional updates available and click on KB4501375
Start the installation process for KB4501375

Alternatively, you can download and install the update directly from the Microsoft Update Catalog: Microsoft Update Catalog | KB4501375

KB4501375 may fix the MMC error if it is the same error others have been facing with Event Viewer. The note about it is shown below with the link to more information about the update:

Addresses an issue that may display the error, “MMC has detected an error in a snap-in and will unload it.” when you try to expand, view, or create Custom Views in Event Viewer. Additionally, the application may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs.

June 27, 2019—KB4501375 (OS Build 18362.207)

maxpeen · Jun 29, 2019

Righto, just installed that one yesterday (after my post above though). I'll monitor the behavior of the PC and revert back if issues occur.

The professional help here is much appreciated. As an IT guy (more networking/Wi-Fi/virtualization and design/operational side) it is quite frustrating if you can't fix something. Re-install is, particularly on this setup, not always an option and (in my opinion) the rout e that should be taken by default.

Search

Search

SFCFix crash upon initalizing SFC corruption

maxpeen

Member

Sysnative Windows Update

Inactive

maxpeen

Member

writhziden

Administrator, .NET/UWP Developer

Attachments

maxpeen

Member

maxpeen

Member

Attachments

maxpeen

Member

maxpeen

Member

writhziden

Administrator, .NET/UWP Developer

maxpeen

Member