Because people's computers work on Windows 8, and stop working after "upgrading" to windows 10. Those people don't care that it's a 3rd party driver causing the problem. (If it is; it's hard to know sometimes.)

Here's one example, but there are plenty of others: https://www.asus.com/uk/Notebooks/ASUS_EeeBook_X205TA/HelpDe...

Here's the faqs that begin "After installing Windows 10".

https://www.asus.com/uk/support/FAQ/1016168/

https://www.asus.com/uk/support/FAQ/1016490/

https://www.asus.com/uk/support/FAQ/1016169/

https://www.asus.com/uk/support/FAQ/1013137/

https://www.asus.com/uk/support/FAQ/1015923/

https://www.asus.com/uk/support/FAQ/1015947/

https://www.asus.com/uk/support/FAQ/1015970/

And it affects network connectivity, so you'll need to use a different machine to look find these FAQs: https://www.asus.com/uk/support/FAQ/1015954/

Driver issues caused by the OEMs incompetence make the computer the shitty product, not windows.

We don't blame microsoft for superfish either, do we? Or hard drive failures?

As long as it's Microsoft causing the upgrade prompt, it's their problem. As long as the (terrible) drivers worked before the upgrade, it should check that drivers are available for the hardware before trying to go through with the upgrade.

There's an analogous situation with Android phones; Google doesn't try to upgrade every phone to the newest release, because they can't guarantee it will work afterwards.

I'd still blame the OEMs, of course, when the hardware stops working after installing from a retail Windows 10 disc. But in that case it was from a user-initiated action, at least.

Do the OEMs suddenly not have a responsibility to keep their drivers working on the OS they picked?

>it should check that drivers are available for the hardware before trying to go through with the upgrade

From what I've gathered the issue tends to be with drivers not working, rather than not existing. This is again entirely the OEMs fault, there isn't any feasible way for MSFT to verify that the drivers aren't broken.

These OEMs knew very well that microsoft was going to do this but still neglected to fix their drivers.

I've never even used 10 and I can tell you some of the complaints about it:

* bad driver support

* invasive telemetry

* missing accounts/files after upgrading

* slow, wonky UI

These are well known problems even to me.

I personally don't think 7 was "good", but it was tolerable. A lot of people clearly don't want 10, but are being tricked into installing it. Why not just extend the product people are happy with?

For drivers you should blame your OEM instead of pretending that MS completely ignored them when rolling this out.

AFAIK the telemetry has mostly been backported.

I don't really know about the missing files, but it's certainly been a common complaint across all new windows releases. Usually the cause has been user error.

I personally find the windows 10 UI to be a significant improvement.

>Why not just extend the product people are happy with?

And that is how you end up with another XP fiasco.

Your purposely ignoring my point though: People have a working product. Why push them to a non-working product, when they clearly don't want it?

Maintain the current product, take the time to make the product work, and make it appealing to them, then you won't have to push them.

From my previous comment:

>And that is how you end up with another XP fiasco.

k