[SOLVED] Microsoft Updates Fail (Windows 8.1)

sjohansen

Member
Joined
Jan 17, 2015
Posts
5
MS Updates: KB3002885 & KB3000850 will not install (Error details have shown both 800F0922 & 80073AA2)

After considerable research and exhaustive steps for resolving (sfc /scannow, dism, chkdsk, health, restore health, disabling secure boot, etc...) short of a fresh install, I thought I would download and run the FCFix application from sysnative which started and completed 5 of the 6 steps and the failed to complete with the below message:
-------------------------------------------------
SFCFix version 2.4.1.0 by niemiro.
Start time: 2015-01-17 08:45:41.385
Not using a script file.


SFCFix version 2.4.1.0 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2015-01-17 08:45:47.957
----------------------EOF-----------------------

I found several forums that reference the same information found below in my CBS.log file:

2015-01-05 17:45:34, Info CSI 00000870 [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}, Typeneutral, TypeName neutral, PublicKey neutral in the store, file cannot bedecompressed

2015-01-05 17:45:34, Info CSI 00000873 [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}, Typeneutral, TypeName neutral, PublicKey neutral in the store, file cannot bedecompressed

2015-01-05 17:45:34, Info CSI 00000874 [SR] This component was referencedby [l:326{163}]"Microsoft-Windows-Client-Features-Package-AutoMerged-com~31bf3856ad364e35~amd64~~6.3.9600.16384.Microsoft-Windows-Client-Features-Package-AutoMerged-com-Deployment"


There are a number of downloads in this forum to repair, but instructions stating that they are case note specific. Looking for help.

Thanks.
 
Hello and welcome to the forum :)

Before we get started on a fix can you please run a new scan with SFC /SCANNOW and upload a CBS log?

SFC /SCANNOW
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code:
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive

Alex
 
Thank you for taking the time to help with this situation. I removed the SFCFix app and reinstalled... below is the result:

SFCFix version 2.4.1.0 by niemiro.
Start time: 2015-01-17 18:11:52.357
Not using a script file.


AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-01-17 18:12:40.446
----------------------EOF-----------------------

Attached are text files of the CBS log & Admin steps taken thus far in addition to several other recommendations found in threads.

View attachment sfcdetails.txt
View attachment Command Promp Task History.txt

After completing all of the above, the two MS updates KB3002885 & KB3000850 still cannot be installed.

I also noted a difference in the CBS log between the two runs which are below:

2015-01-05 17:45:34, Info CSI 00000870 [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
2015-01-05 17:45:34, Info CSI 00000873 [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}, Typeneutral, TypeName neutral, PublicKey neutral in the store, file cannot bedecompressed
2015-01-05 17:45:34, Info CSI 00000874[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"

2015-01-17 15:58:58,Info CSI 000000eb [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}, Typeneutral, TypeName neutral, PublicKey neutral in the store, file cannot bedecompressed
2015-01-17 15:59:00, Info CSI 000000f8 [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}, Typeneutral, TypeName neutral, PublicKey neutral in the store, file cannot bedecompressed
2015-01-17 15:59:00, Info CSI 000000f9 [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"
 
Last edited:
Code:
2015-01-05 17:45:34, Info CSI 00000870 [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, [COLOR="#FF0000"]file cannot be[/COLOR] [COLOR="#FF0000"]decompressed[/COLOR]
2015-01-05 17:45:34, Info CSI 00000873 [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}, Typeneutral, TypeName neutral, PublicKey neutral in the store, [COLOR="#FF0000"]file cannot be [/COLOR][COLOR="#FF0000"]decompressed[/COLOR]

As you can the see above this is the issue with SFC and DISM, this is always one of two things, a file corruption or a registry corruption.

Can you please see if SFCFix runs like 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. 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.
 
View attachment SFCFixScript.txt

Please find attached the results of the SFCFixScript above in the attached file and embedded below:

SFCFix version 2.4.1.0 by niemiro.
Start time: 2015-01-19 08:05:44.418
Using .txt script file at C:\Users\Stuart Johansen\Desktop\SFCFixScript.txt [0]


FileScan::
[0: 1] C:\Windows\System32\MsDtc\MSDTC.LOG
File is untraceable.
Found: ZVe2tEz1AQgARHvrbzOmsqrdtOrxi8rklkE897Hje4Y=
Version number not available.
Trace not available.

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

[2: 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.
FileScan:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-01-19 08:05:50.232
Script hash: yqmxX1j/+8ZyX3y6rPOmoWChAp9FEXuZ4bDqiXrV6rc=
----------------------EOF-----------------------
 
Code:
[1: 1] C:\Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG
File is untraceable.
Found: Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=
Version number not available.
Trace not available.

This is the file that can not be decompressed, the reason being is the file is already decompressed, but SFC is looking for a compressed version. What we will do here is replace the file 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 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 /SCANNOW
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code:
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive

Alex
 
SFC log is good :)

Code:
2015-01-20 11:01:01, Info                  CSI    00000867 [SR] Verify complete
2015-01-20 11:01:01, Info                  CSI    00000868 [SR] Repairing 0 components
2015-01-20 11:01:01, Info                  CSI    00000869 [SR] Beginning Verify and Repair transaction
2015-01-20 11:01:01, Info                  CSI    0000086a [SR] Repair complete

What error message is showing when you are trying to up Windows? is it still the same as before?
 
Thank you for all your help... I ended up reinstalling the operating system and things seem to be working correctly.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top