This hardware uses PowerVR GPUs (e.g. rebranded GMA500), which are no longer supported (driver updates) for Windows by both Intel and Imagination, and even on older versions of Windows (and Linux) had barely-to-non-functional drivers. These drivers already had various bugs, and on newer Windows 10 versions an additional bug is apparently 'text not rendering'.
The install base of this hardware is fairly low as the hardware already barely was usable, that it apparently wasn't deemed worth the engineering effort to work around this type of flawed driver.
Of course, this article completely ignores that information, presumably to cause typical baseless Microsoft hate.
I had an Acer Aspire 751 with Atom Z520 and the GMA500 GPU you mentioned. It always had terrible driver support in Windows 7. When I updated to the Windows 10 insider preview before it was released, it was unusable. Huge graphics glitches all over the place, text would disappear entirely in some programs, random scrambled blocks of the screen that changed as you navigated. By the time Windows 10 was officially released it had been improved, but still wasn't great. Not surprising that this piece of hardware isn't a good candidate for support in the future.
So in 12 years time when Windows 10 is as old as Windows XP we'll be back to the same security nightmare that Windows 10 was supposed to put an end to?
That's a bit disingenuous of Microsoft - they've been parading the 'as-a-service' model as a security feature so that users get constant patches.
I wouldn't be so sure until the support actually drops.
1607 is going to receive updates to 2018, and the Acer quote says "Microsoft is working with us to help provide compatible drivers to address this incompatibility", and I can see no official statement from MS saying otherwise.
The "Windows 10 is no longer supported on this PC" message, then, could be explained by simple "if (!systemsupported()) { show message }" that does not properly take into account that support could still be added in the future.
Windows upgrades have worked for decades without manufacturer support. I can't remember the last time in the "32 bit and above" era that a whole class of CPU stopped working release to release. You might be bound by RAM or a particular driver but you were generally ok to upgrade. Is Apple's grip on this community so strong that we now accept hardware deprecation for PCs? (Though even apple didn't cut off my 2009 machine until sierra.)
[+] [-] ntauthority|8 years ago|reply
The install base of this hardware is fairly low as the hardware already barely was usable, that it apparently wasn't deemed worth the engineering effort to work around this type of flawed driver.
Of course, this article completely ignores that information, presumably to cause typical baseless Microsoft hate.
[+] [-] Dylan16807|8 years ago|reply
Windows 8.1 on these devices is still supported until 2023 as far as I can tell.
[+] [-] dabockster|8 years ago|reply
AKA the OEMs could get it super cheaply and throw it on entry level netbooks for max profit.
This isn't Microsoft's fault. All the blame is on the OEMs here for using hardware that was known to be at EOL stage.
[+] [-] nickcoury|8 years ago|reply
[+] [-] jarym|8 years ago|reply
That's a bit disingenuous of Microsoft - they've been parading the 'as-a-service' model as a security feature so that users get constant patches.
[+] [-] twblalock|8 years ago|reply
A line needs to be drawn somewhere.
[+] [-] aaomidi|8 years ago|reply
[+] [-] AnssiH|8 years ago|reply
1607 is going to receive updates to 2018, and the Acer quote says "Microsoft is working with us to help provide compatible drivers to address this incompatibility", and I can see no official statement from MS saying otherwise.
The "Windows 10 is no longer supported on this PC" message, then, could be explained by simple "if (!systemsupported()) { show message }" that does not properly take into account that support could still be added in the future.
[+] [-] lightbyte|8 years ago|reply
In other news, water is wet.
[+] [-] asveikau|8 years ago|reply
[+] [-] ConfucianNardin|8 years ago|reply
[+] [-] castell|8 years ago|reply
[+] [-] Palomides|8 years ago|reply
[+] [-] MikusR|8 years ago|reply
[+] [-] rbanffy|8 years ago|reply
[+] [-] pantalaimon|8 years ago|reply
The problem here lies within the graphics driver for the PowerVR GPU - which was never really supported under Linux either.
There is an experimental 2D driver [0] which is unlikely to receive any mayor updates, I don't know how stable it is at this day and age.
You won't get any 3D or video decoding acceleration though unless you use a now as well unsupported release like Ubuntu 11.10 [1]
[0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
[1] https://wiki.ubuntu.com/PoulsboObsoleteDrivers
[+] [-] gruez|8 years ago|reply
[+] [-] E6300|8 years ago|reply
[+] [-] MikusR|8 years ago|reply