[SOLVED] Missing Files, Paths; Corrupt File(s); SFCFix Crashes

I'm going to uninstall Avira right now. While I'm doing that:

The DIRSD OWNER WARNING, Duplicate Ownership warnings, entries with question marks, files listed as "not owned"...all of that is OK? Does it make sense to run DISM to analyze health or is that pointless given my clean CBS log?

Sorry for all the questions - maybe I'm just paranoid after all of my recent troubles.

I assume it's OK to uninstall some apps I won't be using and run Disk Cleanup to remove the upgrade log files, previous Windows installation, temporary Windows installation files, delivery optimization and ESD installation files? All of that together totals nearly 30 GB.

Thanks again
 
Uninstalled Avira. Didn't help.

I really need to know why I can't make that change. Any idea at all? What if I tried to take ownership of the registry key? I've seen some posts online about that possibly working.
 
Oh, I meant that Avira should automatically turn Windows Defender off as part of it's installation process.

Yes, feel free to run disk cleanup - it might also be a good idea to run disk defragmenter when it completes.

The ownership / duplicate ownership / no ownership messages are completely normal and can be ignored :)
If you'd like to run DISM you can, I'll review the CBS log.
 
dism.log - Google Drive

CBS.log - Google Drive

CheckHealth and ScanHealth said no corruption found. RestoreHealth quit at 47.6% with error 1726, "the remote procedure call failed"

Btw, in Services, Remote Procedure Call is set to "automatic" and it's currently running. RPC Locator is set to "manual" and isn't running.
 
I ran disk cleanup yesterday. As I rebooted I noticed a message saying something about "please restart to complete driver update." Now my computer will not start. It stalled at the spinning dots. Following some advice I found online unplugged my USB mouse and keyboard but that didn't help. I let the computer run overnight and in the morning found the screen to be white. Shut it down, restarted and then got black screen. Pressing F10 does nothing nor did pressing other keys. I have Windows 10 recovery OS saved to a USB but even that didn't get me to a boot screen. Hoping you can help.
 
Long story short, via System Restore in safe mode, I'm back up and running. I believe it was a driver conflict but have no way of knowing for sure.

My earlier concern about Windows Defender isn't even a priority at this point. My concern is why RestoreHealth fails to complete. Until that question is answered I won't have confidence in the stability of my system despite the repair upgrade.

Thanks again. Hoping to hear from you tomorrow and that you can see me through to resolution in the next few days.
 
Code: 
2017-01-13 17:32:42, Info                  CBS    
=================================
Checking System Update Readiness.


Summary:
Operation: Detect only 
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption:	0
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	0
	CSI Manifest Corruption:	0
	CSI Metadata Corruption:	0
	CSI Payload Corruption:	0
Total Repaired Corruption:	0
	CBS Manifest Repaired:	0
	CSI Manifest Repaired:	0
	CSI Payload Repaired:	0
	CSI Store Metadata refreshed:	True

Total Operation Time: 881 seconds.

2017-01-13 17:32:42, Info                  CBS    CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2017-01-13 17:32:42, Info                  CBS    Count of times corruption detected: 0

Looks like no corruption is detected, I'm not sure why the repair process would fail.

Please try configuring Windows for clean boot and try it again.

Clean Boot

  1. Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.
  2. Type msconfig in the search box, and then tap or click msconfig.
    2832179.png
  3. On the Services tab of the System Configuration dialog box, tap or click to select the Hide all Microsoft services check box, and then tap or click Disable all.
    2832144.png
  4. On the Startup tab of the System Configuration dialog box, tap or click Open Task Manager
    2832180.png
  5. On the Startup tab in Task Manager, for each startup item, select the item and then click Disable.
    2832181.png
  6. On the Startup tab of the System Configuration dialog box, tap or click OK, and then restart the computer.
    2832147.png


    https://support.microsoft.com/en-us/kb/929135
 
Clean boot must have been the ticket because it completed this time. /scanhealth said no component store corruption detected. /restorehealth said the restore option completed successfully.

dism.log - Google Drive

CBS.log - Google Drive

Even though the CBS log says zero corruption I noticed this:

Only CSI metadata corruption found, Process CSI repair.

Does that mean it found something corrupt and fixed it?

Thanks
 
Code: 
2017-01-17 17:36:39, Info                  CBS    
=================================
Checking System Update Readiness.


Summary:
Operation: Detect and Repair 
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:	0
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	0
	CSI Manifest Corruption:	0
	CSI Metadata Corruption:	0
	CSI Payload Corruption:	0
Total Repaired Corruption:	0
	CBS Manifest Repaired:	0
	CSI Manifest Repaired:	0
	CSI Payload Repaired:	0
	CSI Store Metadata refreshed:	True

Total Operation Time: 267 seconds.

2017-01-17 17:36:39, Info                  CBS    CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2017-01-17 17:36:39, Info                  CBS    Count of times corruption detected: 0

From the results, it doesn't appear to have found anything.

You can re-enable the startup items in groups, then reboot and attempt to run the DISM repair until it fails to find out which item in particular was causing the problem if you would like.
 
Thanks, good idea. I just ran DISM /restorehealth in normal mode. This time, the operation completed successfully 100% with the same results as above (zeros across the board). I guess that means I'm good at this point?
 
Good deal. Well, again, thank you for all your assistance - hopefully I won't need anymore any time soon :) I'll happily be making a small donation to the forum shortly.
 
CBS.log - Google Drive

dism.log - Google Drive

It's me again (;

I hadn't run sfc /scannow since you last helped me 2 weeks ago so just decided to today. Result was "found corrupted files but could not repair them". The log says there's a problem with systemconfiguration.lnk (not sure if there are other issues, that's just the one I noticed), specifically "cannot repair member file" and "could not reproject corrupted file". DISM restorehealth failed about halfway through with "source files could not be found". Logs are enclosed. No idea how or when this happened.

Thanks again
 
Code: 
2017-02-02 14:46:53, Info                  CBS    
=================================
Checking System Update Readiness.

(p)	CSI Payload Corrupt			amd64_microsoft-windows-msconfig-exe_31bf3856ad364e35_10.0.14393.0_none_07eea9feb472b4f8\System Configuration.lnk
Repair failed: Missing replacement payload.

Summary:
Operation: Detect and Repair 
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption:	1
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	0
	CSI Manifest Corruption:	0
	CSI Metadata Corruption:	0
	CSI Payload Corruption:	1
Total Repaired Corruption:	0
	CBS Manifest Repaired:	0
	CSI Manifest Repaired:	0
	CSI Payload Repaired:	0
	CSI Store Metadata refreshed:	True

Total Operation Time: 576 seconds.

2017-02-02 14:46:53, Info                  CBS    CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download Result: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB]

Looks like it is just that one file.

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.

View attachment SFCFix.zip

Step 2 - SFC Scan

  1. Swipe in from the right edge of the screen, and then tap Search.
    (If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search.)
  2. Type cmd in the search box, and then right-click or press and hold on Command Prompt.
  3. Tap or click Run as administrator.
  4. 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
  5. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
Here you go. I think it worked? Is there any way of knowing how my files get corrupted so frequently? Thanks again

PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-msconfig-exe_31bf3856ad364e35_10.0.14393.0_none_07eea9feb472b4f8\System Configuration.lnk
Successfully copied file C:\Users\Joe\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-msconfig-exe_31bf3856ad364e35_10.0.14393.0_none_07eea9feb472b4f8\System Configuration.lnk to C:\Windows\WinSxS\amd64_microsoft-windows-msconfig-exe_31bf3856ad364e35_10.0.14393.0_none_07eea9feb472b4f8\System Configuration.lnk.
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-msconfig-exe_31bf3856ad364e35_10.0.14393.0_none_07eea9feb472b4f8\System Configuration.lnk
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-msconfig-exe_31bf3856ad364e35_10.0.14393.0_none_07eea9feb472b4f8\System Configuration.lnk
PowerCopy:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-02-03 18:10:05.238
Script hash: yM0TONpB8XFQVv0Yj0eWSYVAEPcks85yYgLhDeXIwFE=
----------------------EOF----------------------

cbs.txt - Google Drive
 
Yes, looks like it worked :)

As for the why, I'm not sure. I've seen some disk cleanup tools etc. change or delete built in shortcuts.

Have you tested the memory on this computer before?

If not, you can run the Windows Memory Diagnostic with these instructions:

Click Start, type mdsched.exe in the Search box, and then press Enter.
Choose whether to restart the computer and run the tool immediately or schedule the tool to run at the next restart.
Windows Memory Diagnostics runs automatically after the computer restarts and performs a standard memory test automatically.
When testing is completed, the computer restarts automatically. You’ll see the test results when you log on.
 
Memory diagnostic detected no errors.

But in the Event Viewer under Windows Logs-Servicing, it says "Event ID 1015: 0 of 1 instances of system store corruption have been repaired. Unrepaired corruptions may lead to failures in future system servicing."

What does this mean?
 
Good, I'm glad that the memory tested good.

I'm assuming that event is from 2017-02-02? If so, that would be an expected event because of the corrupt shortcut detected with the DISM run.
 
You're absolutely right. Sorry about that!

What still concerns me is the fact the WU troubleshooter still says "service registration missing or corrupt" and says this pretty much all the time. Same with the WS Apps troubleshooter always saying "Windows Store cache may be damaged". When I actually run those troubleshooters it says the issues are fixed but never really are.

Are there known problems with these troubleshooters giving false errors? Do you think it's worth running DISM again to see if it completes?

Thanks 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