New
#11
I am fairly sure I found out what was going on. In sequence, the nice man who sold me the "pre-owned" HP840 had put a Toshiba HD (spinning around kind) in the HP in such a way that the connections were loose. After a long while finally I discovered that loose connection issue and in the process of that nice man dealing with it he easily convinced me to put in a SSD in its place. I didn't know at the time that the "HP" HD he removed was actually a Toshiba till I got home with that HD as an emergency backup. Nor that the SSD he replaced it with was from Samsung, but it is tested by me as "PERFECT".
It turns out that the missing log files that could not be repaired were from the pre-1703 version and my research today showed those files are not transferable from computer to computer. And that if MS-DTC is disabled or has a problem it can cause occasional system freezing. Further, the nice man had forgotten to make me Administrator in the WinX he put into the SSD and he had to re-install that version again. So I can guess that somewhere in the process the MS-DTC got turned off during transfers and/or numerous software incompatibility conflicts which caused the freezing and finally resulted in giving me the only option of what turned out to be a less-than-perfect Refresh the first time.
Trying to solve the "unable to repair" scc /scannow results led me to the MS-DTC which was not running and I turned it on, first manually, checked later and it was not running, so set it to automatic and it seems to be still running when I check. Just now checked again: yep, still running.
So the freezes are at least a lot less "occasional", as in NO freezes since!
And the two "irreparable files" which turn out to be associated with the original pre-1703 version 10.0.15063.0 would be useless anyway now I guess, so "unrepaired" they shall remain I guess (my research today showed that MS-DTC does current logging anyway and so I suppose the old log info would only be useful for analysis of a basically removed version)
or ....?
reference:
2017-08-08 16:32:35, Info CSI 000016d0 [SR] Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.15063.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
This component was referenced by [l:161]'Microsoft-Windows-Client-Features-Package-AutoMerged-com~31bf3856ad364e35~amd64~~10.0.15063.0.Microsoft-Windows-Client-Features-Package-AutoMerged-com-Deployment'
Quote
