I see no reason to make any decision now. Wait until it comes out.
Personally, I will not be "upgrading" any of my current systems. I built this, my main computer, specifically for W10 back in February 2016 for my birthday using components certified for use with W10. I will probably do the same for W11 this next February.
As a tech with a shop, I can say without a doubt, the biggest problems with W10 has been with systems built with older hardware designed for W7, Vista or even XP where the originally install OS was upgraded to W10. But that is NOT Microsoft's fault. It is up to the hardware makers to ensure compatible drivers are available, not Microsoft's.
Let's not forget the lessons learned from history.
During the development of XP, Microsoft was forced to cave-in to pressures from the corporate world (MS's biggest client base) and include legacy hardware and software support in XP. This was because the corporate world did not want to retool again. And I sure understand their plight here. It is a very expensive process to buy all new hardware and reprogram all their custom software just to ensure compatibility with another new OS. They had to do this moving from CP/M to DOS, and from DOS to Windows 3.x and again from 3.x to 95/98. So they insisted XP support all that DOS/95 era software and hardware.
The problem is, to ensure support of these
less secure legacy hardware and software products, MS was forced to compromise the security that was included in the latest, state-of-the-art technologies of the current hardware and software techniques.
Remember, Microsoft even wanted to include anti-virus code in XP but Norton, McAfee, CA, TrendMicro whined and cried to Congress and the EU that Microsoft was trying to rule the world (they were - but that's another issue) and monopolize the industry (also true, but irrelevant here). They claimed it was their job to rid the world of malware (we see how well that went!
).
Congress and the EU threated to break up Microsoft
Ma Bell-style if Microsoft didn't remove that advanced (for the time) anti-virus code. So Microsoft removed the anti-virus code from the final release version of XP.
Then what happened? The bad guys moved in and exploited the unprotected vulnerabilities in XP. But who got blamed? Users who failed to secure their systems? Nope! Norton & McAfee for failing to stop the bad guys? Nope! The bad guys who perpetrated the offenses? Nope! Microsoft got blamed - relentlessly for the next 10+ years.
So today, Microsoft would much rather ensure compatibility with the latest
most secure hardware technologies and get blamed for failing to support outdated, superseded, legacy products than get blamed for being lax in security. And I don't blame them! In fact, I applaud their decision. Security must take top priority. And we consumers must accept that that means we must retire our perfectly good legacy hardware and stay current with the times. We do it with our cell-phones, TVs, and other products. So too must we with our computers.
Oh bullfeathers! You don't know that. You cannot predict the future and declare it a "fact". You are only guessing, and worse, projecting your biases. The only simple fact about the future that is certain is the sun will rise tomorrow - and even that is not a 100% certainty.
There are over 1 billion W10 systems out there with almost all running with Windows Update settings at the default settings. And "the simple fact" is the vast majority, by a HUGE margin, don't have problems. Why? Because they leave the defaults and Registry settings alone! Why? Because, contrary to what many want us to believe, the developers at Microsoft do know what they are doing. I cannot and will not say the same for the marketing weenies and execs, but the developers are some of the best in the world.
Do some folks have problems? Sure! Nothing human made is 100% perfect 100% of the time. But the fact is Windows Updates works. The problem is, if just 1/10 of 1% of the W10 users have problems, that is still 1,000,000 upset users! That's a lot! And 1 million upset users can make a lot of noise - especially when amplified and repeated over and over again by Microsoft bashers, bloggers, and wannabe journalists in the IT press. Yet, there are not anything near 1 million systems that break every time a new Windows Update comes out. We MUST look at the big picture and not assume our own anecdotal experiences, these rare exceptions to the rule, are normal or make the rule. They don't.
