Continued 1703 crashes: ALL programs "incompatible"

[Airider]

This now happens every few hours, has only been going on since I tried to get Spotlight to work again 2 weeks ago. Have to use on/off switch to escape and reboot, everything fine then. System Restore will not show restore points before that time! Security Program Compatibility Trouble shooter (claims it is the latest version) indicates Skype (ususally not on when crashed), Firefox, Chrome & Kaspersky are ALL "incompatible" then claims it has "fixed" them. Re-testing first shows "incompatible" then again claims it has "fixed" them.

I cannot re-install WinX or do in-place change. Installed 1703 months ago, continually updated. Everything worked until Spotlight problem .... which is now coming in via Dynamic Theme.

scannow indicates no probs

Reliability Monitor > "no solutions found"

HP EliteBoook 840 G2, new SSD (super) 64-bit WinX Pro v. 1703

 

[Wolfie]

Hi Airider,

have you tried troubleshooting?:

https://support.microsoft.com/en-us...68-021e32467565/windows-update-troubleshooter

 

[Airider]

Yes, MANY times over the past week, incl. that version! What I finally did, after many HOURS (more than 10 hrs) of System Restore and uninstalling and re-installing various versions of Firefox (now running 64-bit) and Kaspersky (now running KIS 16 again till license expires in 3 mos, will then renew w/KIS 17.), was what I had always done with beloved Win7 , namely not use Defender! Period. Just much more effective Kaspersky.

A result of my own "troubleshooting", since I personally checked and saw that HealthService repeatedly showed up in the crash reports (reliability history) ....

since many not-too important and solvable issues came along with 1703 (ex-wife was Group Leader of 40 men in Testing at MS Redmond and I do know about bugs in software w/ millions of lines of code), I found and used, from https://partnersupport.microsoft.co...s/5829f484-939c-4365-8545-770ba0efc66d?auth=1 >
1. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SecurityHealthService
2. Set the start type to 3.
3. Go to Task Manager, Startup, right click on Windows Defender Notification icon, click Disable. Reboot. Problem solved.(from Windows

That seems to be working so far (if not, can easily undo it)

(but will not mark "solved" until so proven over the next days)

 

[Airider]

UPDATE: crashes continue, so have re-activated Defender and it is now again set to do Periodic Scanning

 

[Airider]

here is the latest crash and path, correlated in my observation mostly to the length of time Firefox was running (but it could be also how long the computer was running)

 

[Airider]

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 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'