[SOLVED] Aura - As Requested: SFC & DISM indicate problems

[britechguy]

Here are links to the logs:

CBS.log

DISM.log

Thanks in advance for any assistance you can offer me in resolving this issue.

Brian

 

[Aura]

Yo :)

Here, follow the instructions below please.

SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.

• Download SFCFix and move the executable on your Desktop;
• Download the attached SFCFix.zip and move the archive to your Desktop;
  Note: Make sure that the file is named SFCFix.zip, do not rename it.
• Save any work you have open, and close every programs;
• Drag the SFCFix.zip archive 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;

SFCFix.zip

 

[britechguy]

Aura,

Thanks again and here you go:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-06-03 09:48:10.907
Microsoft Windows 10 Build 10586 - amd64
Using .zip script file at C:\Users\brite_000\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.10586.0_none_67b6c95f81009211\gptext.dll
Successfully took permissions for file or folder C:\WINDOWS\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.10586.0_none_fe99296a56e12a80\gpedit.dll
Successfully took permissions for file or folder C:\WINDOWS\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_10.0.10586.0_none_d872f84b4da4f3d4\fde.dll
Successfully took permissions for file or folder C:\WINDOWS\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.10586.0_none_101c8f1242b816da\fdeploy.dll


Successfully copied file C:\Users\brite_000\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.10586.0_none_67b6c95f81009211\gptext.dll to C:\WINDOWS\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.10586.0_none_67b6c95f81009211\gptext.dll.
Successfully copied file C:\Users\brite_000\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.10586.0_none_fe99296a56e12a80\gpedit.dll to C:\WINDOWS\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.10586.0_none_fe99296a56e12a80\gpedit.dll.
Successfully copied file C:\Users\brite_000\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_10.0.10586.0_none_d872f84b4da4f3d4\fde.dll to C:\WINDOWS\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_10.0.10586.0_none_d872f84b4da4f3d4\fde.dll.
Successfully copied file C:\Users\brite_000\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.10586.0_none_101c8f1242b816da\fdeploy.dll to C:\WINDOWS\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.10586.0_none_101c8f1242b816da\fdeploy.dll.


Successfully restored ownership for C:\WINDOWS\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.10586.0_none_67b6c95f81009211\gptext.dll
Successfully restored permissions on C:\WINDOWS\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_10.0.10586.0_none_67b6c95f81009211\gptext.dll
Successfully restored ownership for C:\WINDOWS\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.10586.0_none_fe99296a56e12a80\gpedit.dll
Successfully restored permissions on C:\WINDOWS\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_10.0.10586.0_none_fe99296a56e12a80\gpedit.dll
Successfully restored ownership for C:\WINDOWS\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_10.0.10586.0_none_d872f84b4da4f3d4\fde.dll
Successfully restored permissions on C:\WINDOWS\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_10.0.10586.0_none_d872f84b4da4f3d4\fde.dll
Successfully restored ownership for C:\WINDOWS\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.10586.0_none_101c8f1242b816da\fdeploy.dll
Successfully restored permissions on C:\WINDOWS\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_10.0.10586.0_none_101c8f1242b816da\fdeploy.dll
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2016-06-03 09:56:03.111
Script hash: QbblkULKvZjI6TZ+utUx/7t96Ym+N0spOmswp6Hsuks=
----------------------EOF-----------------------

 

[Aura]

Good! Now can you run SFC again and provide me the CBS.log after?

 

[britechguy]

Certainly. I've got it running now and will post the log after it completes.

 

[britechguy]

Aura,

Final message from SFC indicated no integrity violations. Here's the CBS.log.

 

[Aura]

Indeed, SFC returned a clean CBS.log. Anything else? :)

 

[britechguy]

Aura,

Other than asking whether I should or need to run DISM, nothing but my profound thanks!

Hold it, I lied just a bit, are you able to give a thumbnail sketch of the difference between what SFC and the DISM trio do or are intended to do? Like so many things Microsoft there often appear to be twenty mechanisms to do essentially or exactly the same thing.

 

[Aura]

I think I explained the differences at one point in a thread on BleepingComputer, and I might have explained it to you It was in the Windows 10 section, though I don't remember which thread. I'll see if I can find it.

 

[britechguy]

If you can find it, that's fine, if not, that's fine too. There's been a lot of water flowing under, around, and sometimes a bit over my bridge the last couple of months, so certain "non-vital" information gets lost in that flood.

 

[Aura]

In my opinion, /ScanHealth and /CheckHealth aren't really needed on online Windows image (the current system). They are mostly destined to packaged Windows images that are ready for deployment. The /RestoreHealth switch is the only one that interests us.

Repair a Windows Image
https://support.microsoft.com/en-ca/kb/929833

 

[britechguy]

I've often thought that anything but the /RestoreHealth option seemed to be irrelevant to an online system. Since I've done the "all three" routine a couple of times just because some have insisted it's necessary I've observed that the /RestoreHealth option appears to recapitulate the very action of the /ScanHealth option as its first order of business.

Thanks again, very much, for your help. I really do appreciate it and the amount of time and effort that goes into it.

 

[Aura]

No problem Brian, you're welcome :)