[SOLVED] MSDTC.log problem/corruption

W

Weetje

Contributor
Joined
Jan 24, 2016
Posts
14
Hello,

I'm new here as I'm experiencing a problem with msdtc.log and a search brought me here. Went through some of the other forums: like it!

Anyway, after installing a bunch of windows updates two days ago I got a blank screen (or black screen, with a cursor, but no desktop). After trying many different things, I couldn't get it fixed. I already played around with some updates that wouldn't install the day before (the big one: KB2919355), so was getting tired of it and at some point I decided to go back to a restore point. This brought back the desktop and I could make the changes I planned by doing things a bit differently. However, sfc /scannow would report a corruption, which it didn't before I went to the restore point and successfully updated windows. I'm a little reluctant to run all the updates given that I may get a black screen again; I figured out afterwards the program startisback was the LIKELY culprit, as I hadn't updated that to the latest version, but I'm not sure and I'm sort of done for now with all the updating spending the whole weekend trying to fix things.

Normally I'm able to fix things myself, even though it takes time, but this one is beyond me. I checked many of the other threads on MSDTC.log to see whether I saw a similar problem. And I ran the MSDTC.log fix mentioned in the sticky above about KB3000850. No change.

So, I hope you guys can help me. I ran the sfcfix.exe as is. I also ran it with the "filescan MSDTC.log" sfcfixscript file.
 

Attachments

Hello again,

In the meantime I tried one thing more, which is changing (back) the value in the COMPONENTS hive from 1 to 21 for the compressed/non-compressed indicator, as in this thread. The issues in that thread were very similar.

So I changed in HKLM\COMPONENTS %windir%\System32\config\COMPONENTS


Code: 
c!microsoft-w..-deployment_31bf3856ad364e35_6.3.9600.16384_19f730b5f5963bc8    REG_BINARY    
    f!msdtc.log    REG_DWORD    [COLOR=#ff0000]0x1[/COLOR]
    f!msdtc.exe    REG_DWORD    0x1


to


Code: 
c!microsoft-w..-deployment_31bf3856ad364e35_6.3.9600.16384_19f730b5f5963bc8    REG_BINARY    
    f!msdtc.log    REG_DWORD    [COLOR=#ff0000]0x21[/COLOR]
    f!msdtc.exe    REG_DWORD    0x1

The CBS.log does now not report a wrong hashtag anymore, but still contains an error that it cannot repair (both sfc and sfcfix not). It's in the attachment.

Hope you can help with this error too!

Ray
 

Attachments

Hi zcomputerwiz,

Thanks for the response and help.

I did run the procedure in that sticky thread (as it matches my error), and if I remember correctly also after changing (back) the registry value described above. Just to be sure, I ran the procedure again, and it still gives an error. I ran sfc /scannow and sfcfix (and the latter told me to get help here again).

The CBS.log file is attached again, as well as the sfcfix.log (even though it's the same)

Hope you know some other solution.
Ray
 

Attachments

Code: 
2016-01-25 01:13:25, Info                  CSI    0000084c [SR] Repairing 1 components
2016-01-25 01:13:25, Info                  CSI    0000084d [SR] Beginning Verify and Repair transaction
2016-01-25 01:13:25, Info                  CSI    0000084e Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG do not match actual file [l:18{9}]"MSDTC.LOG" :
  Found: {l:32 b:SD6OMNd/nMSy7P0Ob02ZGPT4cYglTnq4Gz0i2cQTLNo=} Expected: {l:32 b:Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=}
2016-01-25 01:13:25, Info                  CSI    0000084f [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-01-25 01:13:25, Info                  CSI    00000850 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG do not match actual file [l:18{9}]"MSDTC.LOG" :
  Found: {l:32 b:SD6OMNd/nMSy7P0Ob02ZGPT4cYglTnq4Gz0i2cQTLNo=} Expected: {l:32 b:Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=}
2016-01-25 01:13:25, Info                  CSI    00000851 [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2016-01-25 01:13:25, Info                  CSI    00000852 [SR] This component was referenced by [l:326{163}]"Microsoft-Windows-Client-Features-Package-AutoMerged-com~31bf3856ad364e35~amd64~~6.3.9600.16384.Microsoft-Windows-Client-Features-Package-AutoMerged-com-Deployment"

I found the problem, it appears the wrong script was attached on the guide page.

Let's try this:

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

DISM /RestoreHealth Scan

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. Right-click on the Start
    w8start.png
    button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

    Dism /Online /Cleanup-Image /RestoreHealth

  3. When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:

    C:\Windows\Logs\CBS\CBS.log
 
Hi zcomputerwiz,

Thanks for the quick reply. I really appreciate your help.

I ran the new sfcfix.zip and I got the following returned (which looked good to me)

Code: 
SFCFix version 2.4.8.0 by niemiro.Start time: 2016-01-27 23:14:51.443
Microsoft Windows 8.1 Update 1 - amd64
Using .zip script file at C:\Users\User\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG


Successfully copied file C:\Users\User\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG to C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG.


Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.8.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-01-27 23:14:51.677
Script hash: 3RhU03+VaFcKrTq2vzsYslFR0iMFQxAbzdowBED+W9Y=
----------------------EOF-----------------------

Then I ran the DISM command and it said it the component corruption was repaired (I ran DISM before, a couple of times even at different points of iteration, and I received the same message). The CBS.log is attached.

By the way, the code you refer to in your post is an old result from 25/01. I got that error when the registry value was set to 1, and disappeared when I set it back to 21 (as explained in my initial post). Not sure, as I'm not an expert, but just to be sure.

This would be yesterday's error:
Code: 
2016-01-27 00:41:30, Error                 CSI    00000851 (F) Failed on regenerating file [l:18{9}]"MSDTC.LOG"[gle=0x80004005]2016-01-27 00:41:30, Info                  CSI    00000852 [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be decompressed
2016-01-27 00:41:30, Error                 CSI    00000853@2016/1/26:23:41:30.548 (F) base\wcp\library\delta_library.cpp(287): Error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) originated in function Windows::Rtl::DeltaDecompressBuffer expression: g_pfnApplyDeltaB(( (DELTA_FLAG_TYPE)0x00000000 ), ReferenceInput, CompressedInput, &UncompressedOutput)
[gle=0x80004005]

Do you want me to run sfc /scannow? Or would that interfere?

Ray
 

Attachments

The script I uploaded has the decompressed file, so that would be the reason for the error.

Let's replace it with the compressed version.

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

When SFCFix has finished, run DISM again. When DISM has completed, zip and attach CBS.log with your reply.
 
Thanks. I just ran the sfcscript and attached the CBS log-file.

SFC returned:

Code: 
SFCFix version 2.4.9.0 by niemiro.Start time: 2016-01-28 23:40:42.848
Microsoft Windows 8.1 Update 1 - amd64
Using .zip script file at C:\Users\User\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG


WARNING: File C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG was not backed up as that would replace the current backup.
Successfully copied file C:\Users\User\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG to C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG.


Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.9.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-01-28 23:40:43.052
Script hash: yjjGtesxe3yvSPUBHyX/bTacPGsznNjxatePGv2FSDc=
----------------------EOF-----------------------
 

Attachments

Looks like that did it!

Let's check with SFC, just to be sure.

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

If SFC reports that no integrity violations were detected, then everything should be good.
 
Well, that worked indeed!!! Thanks so much for all your help. Awesome.

indeed it reported no integrity violations, and the CBS.log is clean of errors. BTW, do I need to worry about those double ownership issues?

Thanks again!
Ray
 

Attachments

Excellent, glad to hear it's working :thumbsup2:

No, those ownership warnings are normal.

If you are able to check for and install updates, then I think we have it solved!
 
Hello zcomputerwiz,

Thanks for the update on the file permissions.

The msdtc.log problem seems solved. Today I ran windows update, and all updates were installed, except for one: KB 3000850, the biggest one (700+MB).
Not sure whether you want me to create a new thread, since the error is different this time. If so, let me know.

I ran sfc /scannow and it indicated some files were corrupted and it said there were repaired.
I also ran DISM /online /cleanup-image /restorehealth and it hung at 40% for hours, so I cancelled it. I rebooted and tried again, with the same result.

I also ran SFCFix, but it also hangs on the dism command at 40% (this time I let it run for about 5 hours).

After the sfc /scannow, the CBS.log file was small (like a couple of hundred bytes), but after three hanging DISM commands, it has increased to 107Mb. So I split the CBS.log in separate files (numbered chronologically), otherwise the forum won't let me attach it. CBS2.log seems to span only a couple of minutes, and it seems it is in some sort of loop (checking different packages associated with different KBs and something not finding them).

And I see an error about the Windows Store components in CBS1 and CBS3, but I traced the error code and message (CBS_E_CANCEL) down to me cancelling the DISM. Not sure, so maybe not....

CBS2 contains many info messages about it not finding packages

Anyway, I hope you can help with this one too.

Ray

PS. for a potential next post, can I simply delete the CBS.log file before the next sfc/dism run to keep the size manageable?
 

Attachments

In the meantime, I did some tests and tries, and have a "little" update:

I managed to get KB3000850 installed, by also installing two other KBs (which were not auto installed by Windows Update), and ran another sfc.

However, the corruption is still there. Anticipating another big CBS.log I created two log files. First I ran sfc /scannow and it reported corrruptions and it mentioned it couldn't repair those. The log file is CBS_after_sfc.

Then I tried DISM /online /cleanup-image /restorehealth again. This time it went 100%, but also reported errors and resulted in an error itself: 0x800f081f (see attached screenshot). The logfile is cbs_after_dism.

Since DISM ran and completed, I also ran sfcfix, which also completed. The log is attached too. It appears the corrupted MSDTC.log is back.
 

Attachments

=================================
Checking System Update Readiness.

(p) CSI Payload Corrupt amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG
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: 550 seconds.

Yes, it wants the uncompressed MSDTC.log - but this time for version 6.3.9600.17415.

Follow these instructions to replace it:

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

When SFCFix has completed, run DISM again and attach CBS.log with your reply.
 
Thanks zcomputerwiz!! As far as I can tell, it looks solved now. Really great stuff. Very much appreciated.

DISM reported that it repaired something and/but the CBS.log mentions 0 corruptions.

sfcfix.txt reports:

Code: 
SFCFix version 2.4.9.2 by niemiro.Start time: 2016-02-01 23:24:40.767
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\User\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG


Successfully copied file C:\Users\User\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG to C:\WINDOWS\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG.


Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2016-02-01 23:24:41.142
Script hash: O6Aw+oMlb7yEDIXywgtbJ1YPbao+ui/+uAreu07EWY8=
----------------------EOF-----------------------

CBS.log reports

Code: 
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: 349 seconds.

Seems like something I want. :smile9:
 

Attachments

Very good!

Check for any available Windows Updates and install any that are offered.
If any updates fail, zip up and attach CBS.log
 
Well, my laptop was up to date already (given that I managed to install KB3000850 prior to the latest issue with MCDTC), so I let it install all optional updates available. And all were installed. The CBS.log is also clean (unless this sqm upload issue thing is something).

As far as I can see, the problem is solved. The only thing left is getting this white windows logo (get windows 10) off the notification area (as a result of the optional update), but that's the easy stuff. :smile9:

So thanks again! Awesome!! You guys are doing some great stuff.
 
Excellent!

Glad we could be of assistance.

I'll mark the thread solved. If you encounter any problems, please post back and I will continue to assist you.
 
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