Problem MSDTC.LOG -> File cannot be decompressed

A

alivilla

New member
Joined
Dec 7, 2019
Posts
4
Hi, I hope you can help me with this. I can only follow instruction but if things don't go according to plan I am definitely not too savvy at this.
Using Windows 8.1, ok?

I ran sfc /scannow and got:

2015-07-23 12:45:09, Info CSI 0000097a [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.3.9600.17415, 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
2015-07-23 12:45:09, Info CSI 0000097c [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.3.9600.17415, 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
2015-07-23 12:45:09, Info CSI 0000097d [SR] This component was referenced by [l:164{82}]"Package_929_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-2734_neutral_GDR"

I found your site and ran sfcfix.exe got the following:
1575745174157.png
I also get:


2019-12-06 23:16:02, Info CSI 0000051d [SR] Cannot repair member file [l:64{32}]"Windows.SystemToast.OpenWith.lnk" of Microsoft-Windows-OpenWith, Version = 6.3.9600.17415, 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
2019-12-06 23:16:04, Info CSI 00000520 [SR] Cannot repair member file [l:64{32}]"Windows.SystemToast.OpenWith.lnk" of Microsoft-Windows-OpenWith, Version = 6.3.9600.17415, 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
2019-12-06 23:16:04, Info CSI 00000521 [SR] This component was referenced by [l:166{83}]"Package_1357_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-3886_neutral_GDR"

and


2019-12-06 23:19:39, Info CSI 000006a8 [SR] Cannot repair member file [l:44{22}]"Windows PowerShell.lnk" of Microsoft.Windows.PowerShell.Common, Version = 6.3.9600.17401, 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
2019-12-06 23:19:39, Info CSI 000006aa [SR] Cannot repair member file [l:56{28}]"Windows PowerShell (x86).lnk" of Microsoft.Windows.PowerShell.Common, Version = 6.3.9600.17401, 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
2019-12-06 23:19:43, Info CSI 000006b9 [SR] Cannot repair member file [l:44{22}]"Windows PowerShell.lnk" of Microsoft.Windows.PowerShell.Common, Version = 6.3.9600.17401, 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
2019-12-06 23:19:43, Info CSI 000006ba [SR] This component was referenced by [l:164{82}]"Package_748_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-1978_neutral_GDR"
2019-12-06 23:19:43, Info CSI 000006bc [SR] Cannot repair member file [l:56{28}]"Windows PowerShell (x86).lnk" of Microsoft.Windows.PowerShell.Common, Version = 6.3.9600.17401, 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
2019-12-06 23:19:43, Info CSI 000006bd [SR] This component was referenced by [l:164{82}]"Package_748_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-1978_neutral_GDR"

and again


2019-12-06 23:28:55, Info CSI 00000ad3 [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.3.9600.17415, 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
2019-12-06 23:28:55, Info CSI 00000ad5 [SR] Cannot repair member file [l:64{32}]"Windows.SystemToast.OpenWith.lnk" of Microsoft-Windows-OpenWith, Version = 6.3.9600.17415, 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
2019-12-06 23:28:56, Info CSI 00000ad7 [SR] Cannot repair member file [l:44{22}]"Windows PowerShell.lnk" of Microsoft.Windows.PowerShell.Common, Version = 6.3.9600.17401, 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
2019-12-06 23:28:56, Info CSI 00000ad9 [SR] Cannot repair member file [l:56{28}]"Windows PowerShell (x86).lnk" of Microsoft.Windows.PowerShell.Common, Version = 6.3.9600.17401, 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

and

Cannot repair member file [l:56{28}]"Windows PowerShell (x86).lnk" of Microsoft.Windows.PowerShell.Common, Version = 6.3.9600.17401, 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

2019-12-06 23:29:14, Info CSI 00000b33 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

That is all! What should I do next? Thank you so much for your consideration!
 
Yes, it is.

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

Hi, thank you so much for your prompt response! I am attaching the CBS file as instructed
 

Attachments

Ok, Here is the file created, it looks good. Please let me know if the problem is finally resolved... Sure looks like it.
 

Attachments

Nope.

Please do the following:

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

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