t5181825 (Terry),
First of all, great additions to this thread. You clearly have some testing genes. I've been wrestling with Windows 10 for quite some time and when troubleshooting issues, use this and other forums and few seem to include the thought you put into this
one. Its not to say the others are bad, just more of a plea for help without the same testing strategy you deployed.
Second, most replies and recommendation are to revert to an earlier version or reinstall windows. As a home based user and not a corporate one, the management pattern for updates is largely controlled by Microsoft. Its automatic based on their push and
less controlled by my pull. That being said, their recommendation to revert or reinstall is disingenuous, and yes, it does fells like we are testing for them. But that has become the norm for most software development organizations - even in corporate setting
unfortunately.
The problem we are facing and is not being discussed is that Windows 10 had grown too large and complex. Its supporting desktops, tables and phones all at once and isn't separating the differences. I had problems with a Dell laptop and the Intel graphics
drivers on Windows 10. Finally resolved it by disabling the touch screen that I suspected caused the problem. No definitive cause but the problems started with updates supporting Surface tablet/PC gesture changes. Older, non-MS stuff didn't work with the
change and MS had their targets set.
Unfortunately, and likely to upset the MS staff, this is the challenge we face as customers going forward. Not every customer is identical. Some use local accounts, other MS accounts. We vary in usage patterns, devices and expectations. The prudent approach
is to identify user patterns and create system configuration markers within the OS to provide a run-time controlled user experience. But that is OS infrastructure and not feature/function that excites Product Mangers or executives. Its invasive to the OS,
expensive and a testing nightmare. It also should have been a strategy for the product's foundation when the decision was made to support not only the traditional PC, but phones and then tables.
Thanks again Terry for your posts and the effort you've provided before making them. It certainly helped my efforts on the same problem. I sure hope MS, at some level, starts to realize that their customer base depends on them to be more crisp in the future
and that the features/functions some have requested or envisioned may not be as important as consistency of use for the masses. Clearly the tail is wagging the dog here.