Windows 10 feature updates are coming thick and fast. How do these updates impact on older hardware and why are they being blocked on some PCs?
After reading a lively debate in response to friend and fellow author Marc Thomas’ article,, I decided this topic probably deserved an article of its own. The debate was sparked by comments from regular reader “Tracy” who, if I am not mistaken, runs her own computer repair business, and I do agree with much of what Tracy has to say. A Little History First off; Microsoft is indeed blocking any further feature updates on Windows 10 machines powered by a particular processor, the Intel Clover Trail Atom.
Blackberry Driver For Windows 10. The Clover Trail Atom CPUs were introduced primarily to run 2-in-1 laptops, which represent a relatively small percentage of total PCs. However, in my opinion, this is irrelevant, people bought these little convertible laptops in good faith and with zero warning that their hardware would, within a relatively short space of time, no longer be supported.
How to Update Network Adapter Drivers in Windows 10 without Internet Connection. You need to access Windows 10 Device Manager to check if the driver functions well.
Microsoft is blaming Intel who, it claims, is no longer supporting the Clover Trail Atom processors and therefore no longer providing updated drivers: [These] systems are no longer supported by Intel and without the necessary driver support, they may be incapable of moving to the Windows 10 Creators Update without a potential performance impact. — My question is this; included in these feature updates which should necessitate driver updates anyway? As far as I am concerned, no feature update to date has included anything of particular significance nor, for me personally, added anything of particular interest. The Anniversary Update I was running Windows 10 on modern hardware when the Anniversary update was delivered yet had a dickens of a job trying to install it. After many failed attempts, I finally discovered that a driver issue was preventing the update from completing.