[SOLVED] Win7/32 with "corrupt file" that I cannot fix

F

freemansteve

Member
Joined
May 21, 2015
Posts
9
It's an ancient Dell Mini (super slow, even with an SSD in it) but it has its uses occasionally. I'm fond of it. There are no obvious problems like crashes/BSOD etc - it's just slow.

Being a bit OCD I just wanted to check it was "clean" somehow... I removed everything I could and did a scan.

After running "sfc /scannow" I saw there was an error, but the CBS log was too obfuscated for me to make much of it...

I then ran the latest sfcfix.exe and it soon asked for my Win7 DVD, but I don't have any original media - the PC has been kept alive by disk imaging from time to time, and then returning to a previous image if I break the PC. I think the images I retain have corrupt files in them anyway....

So I space-bar to continue without DVD, and the summary shows "CBS & SFC total detected corruption count: 1", and goes on to give me this data from the log file:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-12-10 15:10:03.966
Microsoft Windows 7 Service Pack 1 - x86
Not using a script file.

AutoAnalysis::
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.1.7600.16385_none_19295908c15690f3\MSDTC.LOG

SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2019-12-10 15:20:51.430
----------------------EOF-----------------------

So, my question is - how do I remove/regen the bad file?

Many thanks if you can offer advice!!
 

Attachments

Hello and welcome!

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.



SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. 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"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

Thank you so much!
sfc /scannow is looking good.
Here is the SCFfix.txt:

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-12-11 11:37:23.367
Microsoft Windows 7 Service Pack 1 - x86
Using .zip script file at C:\Users\Misotu\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.1.7600.16385_none_19295908c15690f3

Successfully copied file C:\Users\Misotu\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.1.7600.16385_none_19295908c15690f3\MSDTC.LOG to C:\Windows\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.1.7600.16385_none_19295908c15690f3\MSDTC.LOG.

Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.1.7600.16385_none_19295908c15690f3
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.1.7600.16385_none_19295908c15690f3
PowerCopy:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2019-12-11 11:37:24.584
Script hash: gjhD25X4SOWbSZwNeWljnUR1h5sKocMfDuMJGD4x9GI=
----------------------EOF-----------------------

Any advice, or actions I can take, or am I now in good shape?
cheers
Steve
 

Attachments

Awesome - thank you. My OCD level has dropped a couple of points, and I have disk imaged the drive!
I don't wish to use up your time with trivia or speculation, but are there any known causes for getting a corrupted MSDTC.log file ?
 
Unfortunately, there are not. Corruption can be caused by several factors, like a sudden power loss, interrupting a Windows Update process or disk activity while it is accessing that very file, a failing hard drive or simply a bug in an update (which is not the case here, because we'd be aware).
 
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