[SOLVED] CORRUPT FILES SEEN BY SFC /SCANNOW ONLY, PLS HELP

N

Nenadius

Member
Joined
Apr 1, 2016
Posts
14
TthxHi,
I have upgraded to W10 x64 PRO recently and due to having a few blue screen errors and sfc /scannow corrupted files - i have been using dism entries, image health program with wim files from techbench, and sfcfix program. I have tried all repair options given by Windows.
Now, after all that, number of errors is reduced to only few of them. I did not have blue screen recently, but would like to clean up everything and make a clean image backup.
Errors are shown only in sfc /scannow CBS log (not in dism or sfcfix logs - they do not find anything now).
Here is my CBS log attached, and I'll be happy if somebody have some time to help me.View attachment CBS.zip Thx in advance. Nenadius
---------------------------------------------------------------
2016-03-31 22:56:07, Info CSI 0000683f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.10586.0_none_a5d89b3e0a5a2eb3\MSDTC.LOG do not match actual file [l:9]"MSDTC.LOG" :
Found: {l:32 F87YQKwsZSu6uWZh/8QCwFKvAITBjAve5LnPIGVmcng=} Expected: {l:32 Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=}
2016-03-31 22:56:07, Info CSI 00006840 [SR] Cannot repair member file [l:9]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-31 22:56:07, Info CSI 00006841@2016/3/31:20:56:07.190 Primitive installers committed for repair
2016-03-31 22:56:07, Info CSI 00006842 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.10586.0_none_a5d89b3e0a5a2eb3\MSDTC.LOG do not match actual file [l:9]"MSDTC.LOG" :
Found: {l:32 F87YQKwsZSu6uWZh/8QCwFKvAITBjAve5LnPIGVmcng=} Expected: {l:32 Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=}
2016-03-31 22:56:07, Info CSI 00006843 [SR] Cannot repair member file [l:9]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-31 22:56:07, Info CSI 00006844 [SR] This component was referenced by [l:161]"Microsoft-Windows-Client-Features-Package-AutoMerged-com~31bf3856ad364e35~amd64~~10.0.10586.0.Microsoft-Windows-Client-Features-Package-AutoMerged-com-Deployment"
2016-03-31 22:56:07, Info CSI 00006845 [SR] This component was referenced by [l:106]"Microsoft-Windows-ComDTC-com-Package~31bf3856ad364e35~amd64~~10.0.10586.0.f1ef22942af5b956516a3cd533741660"
2016-03-31 22:56:07, Info CSI 00006846 [DIRSD OWNER WARNING] Directory [l:29 ml:30]"\??\C:\Windows\System32\Msdtc" is not owned but specifies SDDL in component Microsoft-Windows-COM-DTC-Runtime, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
---------------------------------------------------------
 
jcgriff2 said:
Hi. . .

Please follow these instructions - https://www.sysnative.com/forums/windows-update/4736-windows-update-forum-posting-instructions.html

Regards. . .

jcgriff2
Click to expand...

Hi, here is copy of SCFIX text, and new CBS zip is attached.
Thks for yr time and help.
---------------------------

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-04-01 19:07:58.369
Microsoft Windows 10 Build 10586 - amd64
Not using a script file.


AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-04-01 19:11:21.608
----------------------EOF-----------------------
 

Attachments

Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named LiquidTension. He's one of our senior trainees here who's in his final phrase 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.
 
Hi BrianDrub,
I am getting again BSOD, driver less or equal...
Seems that we should do something as soon as possible...iff possible.
Nenadius
 
Hello Nenadius,

I'm very sorry the delay.
The BSOD issue you are experiencing may be unrelated to anything we address here - so once we've confirmed any and all corruptions have been fixed, it may be best to seek assistance from the BSOD experts over in the BSOD, Crashes, Kernel Debugging section.

For now, please carry out the instructions below, and provide the logs generated.

bMTzsQ3.png
SFCFix Script (.zip)

Warning: This fix is intended for use on this particular machine. Do not use this fix on any other machine; doing so may cause damage to your Operating System. If you are not the original poster and require assistance, please start your own topic.

  • Download View attachment SFCFix.zip and save this file to your Desktop.
  • Note: Ensure this file is named SFCFix.zip. Do not rename the file.
  • Close all open windows.
  • SFCFix.exe
    bMTzsQ3.png
    and SFCFix.zip
    49i66Jv.png
    should both be present on your Desktop.
  • Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  • SFCFix will now process the script. Upon completion, a file (SFCFix.txt) will be created on your Desktop.
  • Copy the contents of the file and paste in your next reply.

MgeHyNE.png
SFC /Scannow

  • Press the Windows Key
    pdKOQKY.png
    + r on your keyboard at the same time. Type Notepad and click OK.
  • Copy the bold lines below and paste into the Notepad document:

    sfc /scannow
    timeout /t 120 /nobreak
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\CBS.txt"
    del %0

  • Click Format. Ensure Wordwrap is unchecked.
  • Click File, Save As and name the file sfcscannow.bat.
  • Select All Files as the Save as type. Save the file to your Desktop.
  • Locate sfcscannow.bat
    lmRDSkT.png
    on your Desktop. Right-click the file and click
    AVOiBNU.jpg
    Run as administrator.
  • Upon completion, a file (CBS.txt) will be created on your Desktop. Attach this file in your next reply.
  • Note: If the file is too large to attach, upload to a service such as Dropbox, One Drive or SendSpace and provide a direct download link in your next reply.
 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-04-05 20:02:03.549
Microsoft Windows 10 Build 10586 - amd64
Using .zip script file at C:\Users\Neno\Desktop\SFCFix.zip [0]







PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.10586.0_none_a5d89b3e0a5a2eb3\MSDTC.LOG


Successfully copied file C:\Users\Neno\AppData\Local\niemiro\Archive\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.10586.0_none_a5d89b3e0a5a2eb3\MSDTC.LOG to C:\Windows\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.10586.0_none_a5d89b3e0a5a2eb3\MSDTC.LOG.


Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.10586.0_none_a5d89b3e0a5a2eb3\MSDTC.LOG
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.10586.0_none_a5d89b3e0a5a2eb3\MSDTC.LOG
PowerCopy:: directive completed successfully.







Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-04-05 20:02:04.096
Script hash: TPTeiSG7U6iN4K1J3W0iuIzVFZzRI7DuCGSHXxiMyoU=
----------------------EOF-----------------------
 
Very good. SFC is no longer reporting any corruptions.

Code: 
2016-04-05 20:17:25, Info                  CSI    00006849 [SR] Verify complete
2016-04-05 20:17:25, Info                  CSI    0000684a [SR] Repairing 0 components
2016-04-05 20:17:25, Info                  CSI    0000684b [SR] Beginning Verify and Repair transaction
2016-04-05 20:17:25, Info                  CSI    0000684c [SR] Repair complete

Let's go ahead and double-check with DISM:

MgeHyNE.png
DISM /RestoreHealth

  • Press the Windows Key
    pdKOQKY.png
    + r on your keyboard at the same time. Type Notepad and click OK.
  • Copy the bold lines below and paste into the Notepad document:

    dism /online /cleanup-image /restorehealth
    timeout /t 120 /nobreak
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\CBS.txt"
    del %0

  • Click Format. Ensure Wordwrap is unchecked.
  • Click File, Save As and name the file dism.bat.
  • Select All Files as the Save as type. Save the file to your Desktop.
  • Locate dism.bat
    lmRDSkT.png
    on your Desktop. Right-click the file and click
    AVOiBNU.jpg
    Run as administrator.
  • Upon completion, a file (CBS.txt) will be created on your Desktop. Attach this file in your next reply.
  • Note: If the file is too large to attach, upload to a service such as Dropbox, One Drive or SendSpace and provide a direct download link in your next reply.
 
Hello,

but CBS log shows some owner warnings and duplicate ownership.
Click to expand...
Such entries in CBS.log are not of concern, or indicative of an issue.

I suggest posting in the BSOD, Crashes, Kernel Debugging section to receive assistance with your BSOD issue. It does appear to be caused by system file-related corruptions.

Good luck!
 
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