[SOLVED] windows update hangs in "preparing to install"; SFCFix info included

[rgmorris]

Hi,

I'm trying to fix an issue on Windows 8.1 where windows update will not install any update. Instead it prints "preparing to install..." forever. There are no visible error messages, it simply never gets anywhere.
I've tried various things to fix this:

clean boot
system restore
windows update troubleshooter
delete SoftwareDistributions folder

None has made any difference. The last thing I tried was sfc /scannow, which reports one error with MSDTC.LOG. I don't know if this actually causes the update problems...

Here's the SFCFix info:

SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-04-01 00:06:59.740
Microsoft Windows 8.1 Update 2 - amd64
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

SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
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.3.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-04-01 00:29:32.337
----------------------EOF-----------------------


The CBS.zip file is 10MB and does not seem to want to add as an attachment.
I will try to send it separately.

I'd really appreciate any help with this.

 

[LogBot]

Logfile submission from rgmorris

Logfile submission from rgmorris.

The logfiles are available at: https://www.sysnative.com/niemiro/fileDistribution/2015-04/5765.zip

 

[BrianDrab]

Hi and welcome to Sysnative. Sorry for the delay. If you are still in need of assistance please let me know.

 

[rgmorris]

Thanks!
I don't have access to that system any more for the foreseeable future.
For the record, several rounds of reboot, running Windows Update Troubleshooter, sfc /scannow and DISM.exe seemed to make the problem go away; though I could not say for sure which if any actually fixed it.
Anyway, feel free to close this topic.