W 7 SFC log error

[mrwoof]

Symptoms : Unable to update W 7, Ran tweaking repair tool twice & SFC several times with detected error unable to fix. Thoughts?
Preparing  for W 10 upgrade

[Boggin]

I've seen where uninstalling KB3022345 as well as installing .NET Framework 4.6.1 has resolved, but have you ran the Pre-Scan in Option 2 of the Windows Repair program to see if it gives any Package corruption.

Use the registry backup option before carrying out any repairs.

https://www.microsoft.com/en-gb/download/details.aspx?id=49981

[mrwoof]

Yep, ran prescan & no coruptions found in packages or enviorn var. Running Surt, "scanning for updates" for 2 hours now.

[Boggin]

If it's still running then end task in Task Manager then download update component reset fixit which will tell you what it has found.

https://support.microsoft.com/en-gb/kb/971058

[mrwoof]

I ran Belarc Advisor, & did a manual install of the detected missing updates & then after multiple reboots, Win updates is working again. hmm.
I see the error flagged in SFC is:
 Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime.
Full line:
 Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.1.7600.16385, 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 is missing.

Steps taken to date:
1.From Folder Options, turn on the "Show hidden files" and uncheck "Hide protected operating system files". Take ownership of the folder: C:\Windows\System32\MsDtc then delete MSDTC.log
2.Reboot the PC and run sfc again.
NOTE: the MSDTC.log will be re-created again the next time Microsoft-Windows-COM-DTC-Runtime try to log to this file.
SFC still detecting error. My reading continues!

[Boggin]

I've seen where that hasn't worked for others also.

That for me would suggest that the problem may not lay entirely with that file and looking to see what Event Viewer has recorded may give a clue as to what else is going on.

I would think this could be a repetitive event error, but should have at least a time stamp for when you carried out that operation to see how the system responded.

[jraju]

Hi, why not try windows readiness tool especially designed for update error,
https://www.microsoft.com/en-us/download/details.aspx?id=3132
run it and then go to checksur.log, you will find the missing if any.