[SOLVED] sfc /scannow could not repair member file [l:18{9}]"MSDTC.LOG"

Anthony · Jan 4, 2017

I felt that the computer has been running a little slugish so I ran SFC /scannow.

Some files could not be repaired. I have attached resulting log files. Please help.

My computer is compaq Presario with AMD athalon 64 x2 dual core processor
Windows Vista home premium.

Thank you.

BrianDrab · Jan 4, 2017

Hi and welcome to Sysnative. Please start with the following.

Step#1 - 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.

Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Anthony · Jan 4, 2017

Thank you for the response. Here is the result text file.

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-01-04 20:23:16.905
Microsoft Windows Vista Service Pack 2 - x86
Using .zip script file at C:\Users\Anthony\Desktop\SFCFix.zip [1]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.0.6001.18000_none_195302e56002fb82\MSDTC.LOG

Successfully copied file C:\Users\Anthony\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.0.6001.18000_none_195302e56002fb82\MSDTC.LOG to C:\Windows\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.0.6001.18000_none_195302e56002fb82\MSDTC.LOG.

Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.0.6001.18000_none_195302e56002fb82\MSDTC.LOG
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.0.6001.18000_none_195302e56002fb82\MSDTC.LOG
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2017-01-04 20:23:17.295
Script hash: CyQ9mx8QxqhnLSM8n5dqGVY0A4pDpm+l5Y9Cu+aYvhQ=
----------------------EOF-----------------------

Anthony · Jan 4, 2017

Anything next to perform ?

BrianDrab · Jan 4, 2017

Yup. Go ahead and do a sfc /scannow and all should be good.

Anthony · Jan 4, 2017

I ran sfc /scannow and it returned message: could not find any integerity violations.

Thank you BrianDrab for your help.

After looking at the original CBS.log file are there any recommendaitons I should do ? did you see anything ?

Anthony

BrianDrab · Jan 4, 2017

Nope. All looks good. Take care.

Search

Search

[SOLVED] sfc /scannow could not repair member file [l:18{9}]"MSDTC.LOG"

Anthony

New member

Attachments

BrianDrab

Emeritus

Attachments

Anthony

New member

Anthony

New member

BrianDrab

Emeritus

Anthony

New member

BrianDrab

Emeritus