[SOLVED] Windows update KB3000850 fails with error: 0x800700a1

P

pbellchambers

New member
Joined
Dec 2, 2014
Posts
3
Steps to reproduce:

1. Install KB3000850 successfully
2. Perform system restore to before installing update
3. Attempt to install update again, receive error: 0x800700a1

SFCFix Log:
Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-12-02 14:25:46.602
Not using a script file.




AutoAnalysis::
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG
CORRUPT: C:\WINDOWS\winsxs\wow64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_14660d42685ac3f1\MSDTC.LOG


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     -3
   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 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-12-02 14:35:07.164
----------------------EOF-----------------------



WindowsUpdate.log attached, CBS logs to follow...
 

Attachments

Hello and welcome to the forum.

This error message has actually come up a few times over the past few weeks.

Code: 
2014-12-02 14:21:08, Error                 CSI    00000882 (F) Failed on regenerating file [l:18{9}]"MSDTC.LOG"[gle=0x80004005]
2014-12-02 14:21:08, Info                  CSI    00000883 [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, [B][COLOR="#FF0000"]file cannot be decompressed[/COLOR][/B]
2014-12-02 14:21:08, Info                  CSI    00000884 [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"

Before we get started on a fix can you please run 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. Go to your desktop and right click on the background -> Select New -> Text Document -> Name this file SFCFixScript.txt.
  3. Open up SFCFixScript.txt and copy all of the following text inside the code box below and paste it into SFCFixScript.txt.
    Code: 
    FileScan::
MSDTC.LOG
  4. Click on File -> Save. Close out of SFCFixScript.txt.
  5. Save any open documents and close all open windows.
  6. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  7. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  8. SFCFix will now process the script.
  9. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  10. 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.
 
Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-12-03 09:57:16.081
Using .txt script file at C:\Users\tregu_000\Desktop\SFCFixScript.txt [1]




FileScan::
[0: 1] C:\Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG
File is untraceable.
 Found: SD6OMNd/nMSy7P0Ob02ZGPT4cYglTnq4Gz0i2cQTLNo=
 Version number not available.
Trace not available.



[1: 1] C:\Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG
File is untraceable.
 Found: Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=
 Version number not available.
Trace not available.



[2: 1] C:\Windows\System32\MsDtc\MSDTC.LOG
File is untraceable.
 Found: 8LZt23we5oM0zYbwU91tGTX3+bBd2i7/WSq3oWcmnkQ=
 Version number not available.
Trace not available.
FileScan:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-12-03 09:57:18.265
Script hash: yqmxX1j/+8ZyX3y6rPOmoWChAp9FEXuZ4bDqiXrV6rc=
----------------------EOF-----------------------
 
I managed to fix this following the information in other threads here. :)

https://www.sysnative.com/forums/wi...nd-system-restore-causing-serious-issues.html
https://www.sysnative.com/forums/windows-update/11969-windows-8-corrupt-files.html

Just some extra notes for your information as I was digging around a bit more...
  • I first tried changing the registry flag without replacing the msdtc.log file and sfc reported that there was a file hash mismatch and wouldn't work.
  • That lead to me looking at my msdtc.log in more detail... the file (C:\Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG) on my machine was only 1KB (the uncompressed one is 4096KB). Does this mean it was indeed compressed, but just corrupt or otherwise un-decompressable in some way and therefore that the registry flag was correct to expect a compressed file?
  • Sfc only worked after both replacing the msdtc.log with your one and then resetting the registry flag


...after fixing this windows update KB3000850 was applied successfully. Thanks a lot! :)
 
These where the threads we used our research on to come up with a fix.

I first tried changing the registry flag without replacing the msdtc.log file and sfc reported that there was a file hash mismatch and wouldn't work.
Click to expand...

That would of been okay, it would of just been a case of replacing the file with a non-corrupt and non-compressed version of the file.

That lead to me looking at my msdtc.log in more detail... the file (C:\Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG) on my machine was only 1KB (the uncompressed one is 4096KB). Does this mean it was indeed compressed, but just corrupt or otherwise un-decompressable in some way and therefore that the registry flag was correct to expect a compressed file?
Click to expand...

By the sounds of that it sounds like the file that was decompressed has since become corrupt. If the file was corrupt that would also stop SFC from being able to decompress the file.

Glad to here that the issue is now resolved :)

Alex
 
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