Razer warns: Do NOT update to Win10 Fall Creators Update

Topic

New Reply

The Razer Insider blog has this warning: It is known that all Razer laptop systems are incompatible with Windows 10 Version 1709 Build 16299.15 that i
[See the full post at: Razer warns: Do NOT update to Win10 Fall Creators Update]

2 users thanked author for this post.

johnf, Ascaris

Reply | Quote

Replies

That’s just a microcosm of everything that’s wrong with how MS is developing Windows 10, isn’t it?  Why should so many drivers for Windows 10 suddenly stop working when a slightly newer version of Windows 10 rolls down the pike (ready or not, here it comes)?

If the new 10 build breaks those drivers, it probably breaks other ones on other PCs too.  For those, the drivers that are now broken may, in fact, be the only ones that will be available for that hardware device under Windows 10.  While PCs have a much longer useful service life than they ever have before, it doesn’t mean that vendors for the various components within that PC have kept pace.  People may have upgraded to Windows 10 because everything worked at that time, thinking that the issue of driver compatibility was already settled, and then “Windows as a service” strikes again.

Something similar to this happened a few months ago, when it was discovered that the impending Windows 10 build broke laptops with Clover Trail Intel ATOM CPUs because somehow the drivers that had worked with 10 up until now weren’t going to be good enough for *this* version of 10 (Creator’s Update, in that case).  No doubt underestimating the furor that would arise over the issue, MS pledged to continue to offer security fixes for the last build of 10 that would work on those PCs until 2023, the year they would have been supported to if they’d stuck with Windows 8.

Will MS now be doing this with any new PCs it orphans with this, the very next version of 10 after the one that orphaned Clover trail?  At this point, it sound like they’re going to have to make every single build of 10 into an extended-release build for a certain segment of customers who thought they were already safely within the Windows 10 fold.

Changing things so much that Windows 10 drivers no longer work with Windows 10 is crazy enough, but they’re doing it now with every “feature” update.  How much disruption and turmoil are customers supposed to tolerate to continue to receive “Windows as a service?”

This is why I doubt that MS is really trying to keep Windows viable.  They can’t be pulling stuff like this every six months and think that it won’t cause harm to the entire Windows franchise.  This just looks like sabotage too much for it to be accidental.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

8 users thanked author for this post.

dononline, Elly, David F, AlexEiffel, johnf, Richard Allen, PKCano, MrBrian

Reply | Quote

I’ll go so far to say that this is, “planned obsolescence”. Or maybe just pure incompetence, at this point who really knows?

1 user thanked author for this post.

HiFlyer

Reply | Quote

When you think about it, Apple struggle to not create issues each year with their feature updates and they only have a few models of hardware to support compared to the many thousands of different combinations possible with Windows.

It is hard to believe they will be able to pull that off with two times a year updates, thinking that just announcing that this is what they will do was sufficient to create the conditions to make it happen.

Never I saw the folks at Microsoft talk about how they were changing Windows itself to make it easy to be in such a rapid deployment cycle. I don’t see things like “Oh, we have this core that won’t change much and when it does, we will notice the hardware vendors in advance, and we have this UI thing that can keep changing twice a year with no impact on underlying hardware…”. No, it is just a matter of having the customer test better and sooner so they can notify their vendor and if these don’t react fast enough, they have to find better vendors, right?

Microsoft is magical, to say the least, but there’s always a trick.

1 user thanked author for this post.

MrBrian

Reply | Quote

So, now the vendors join the ranks of Microsoft Beta (Alpha?) testers? I wonder if they will get as tired of it as the Windows Beta testers?

Microsoft spins out of control, no matter what regime you follow.

Reply | Quote

Strangely The Register a, at best a Windows skeptic, comes out almost in favour of the latest incarnation.

https://www.theregister.co.uk/2017/10/18/windows_fall_creators_update_is_here_and_the_news_is_both_good_and_bad/

Dont worry folks worry  i’ll be sitting this one out. One disgruntled line of machines this early on in the release is sure be a portent of the storm to come. 😉

Reply | Quote

For all those who try to spin it out with a but Windows 10 works fine for me!, please scratch out all the people who have Razer computers.

… I wonder who’s next on Microsoft’s Russian Roulette…

Reply | Quote