SFC definitely seems to be crying, "Wolf!" to me...
NO third party software on Start Menu. To try to minimize problems, this thing's as close to pure as the wind-driven snow as I can make it and still do my work. (And besides, I've never seen any third-party Start replacement that wasn't just awful...)
I used to think profile was related to this, but no longer do. Apparently whatever is causing this is in Windows, not my profile, since the profile was preserved through this Reset cycle and the problem appears to be fixed now. (MS Store suggested the
new user profile juggle and I tried that back in February, but it was just different, not better - if anything, it was *less* stable. This SP4 started with a clean profile except for the Firefox session file.)
The fact that it's better now (and the profile did NOT change) points more to the Registry than the User Profile proper (\Users[username]\AppData\*) as the source of corruption. (I *expect* that part of the Reset process is wiping the Registry and starting
over (or at least wiping or pruning HKLM and probably HKCR, if not all or part of HKCU, too, for those familiar with Registry-speak) and this is one of the big reasons you have to reinstall apps after a Reset, even if you preserve user files and configuration.)
This did start in the day or two (not sure about exact timing) after I installed Corel PDF Fusion for the first time on this machine to assemble a big composite PDF. This may be completely coincidental and not at all related, but it's one of only two things
*I* changed around the time of the corruption showing up again. (The other was the installation of an HP-15C calculator application from HP France (http://www.calculatrices-hp.com/index.php?page=emulateurs
- the apps themselves can be installed to use English.) The calculator is running now with no apparent problems...)
One other possibly relevant datapoint: CorelDraw X4 definitely scrogged Windows 8 (forget the failure mode now...), but I upgraded to X7 a year ago, which fixed that. Is there something new in Win10 that's brought something like the old problem back?