Brian, good news in one way, but not in another. This sfcfix log looks good. Here is it....
SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-04-17 11:21:10.433
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\sandy\Desktop\SFCFix.zip [0]
PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG
Successfully copied file C:\Users\sandy\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG to C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG.
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG
PowerCopy:: directive completed successfully.
Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-04-17 11:21:10.886
Script hash: 45Ng++WKRZwfW8e86PYD7mlsHjLeh5SUKefsD8Ucxl0=
----------------------EOF-----------------------
The cbs.txt is in Dropbox. There is lots of older stuff at the beginning, but the interesting part is today (4/17) at 11:24 until 11:47. It looks good too! I don't see any errors about MSDTC.
https://www.dropbox.com/s/4povkhpsbqz188m/cbs.txt?dl=0
However, Windows Defender is still broken in the same way I described originally. I rebooted, hoping that might clear it up, but no luck. So maybe it's time for me to post in the other area of the forum?
I do appreciate your help. Can you tell me what causes the problem with the MSDTC file that your sfcfix.zip file fixed? Is it something that I myself am causing, or is it a windows bug? And if it's the latter, why doesn't Microsoft fix it? Maybe that's something you cannot answer. But I'm hoping to learn how to not have this problem again, whether it's me or Microsoft!
Thanks again.