Kaby Lake and Zen processors to support Windows 10 or later
Microsoft made a huge effort to convince Windows 7 and 8.1 users to upgrade to Windows 10, and allowing old OS versions to support the Kaby Lake and Zen processors would only encourage users to stick to their older operating systems.
From a technological point of view, Microsoft’s decision is a wise one because these processors haven’t been designed for older operating systems. Moreover, it would be a pity for Microsoft to limit the OS and app development possibilities these two processors offer.
However, Microsoft’s statement only added more fuel to the fire. Windows users have long complained about the methods the tech giant uses to convince them to install Windows 10. The general feeling is that Microsoft is simply robbing PC users of their choice of operating systems.
Intel and AMD totally back Microsoft in this affair explaining that their roadmap is fully aligned with Microsoft’s software strategy. Of course, tech-savvy users could try their luck and install Windows 7 on computers powered by a Kaby Lake processor. However, chances are the user experience will be a catastrophic one.
Since driver support and security updates won’t be available, it’s likely the app and the OS itself will crash. Of course, there is also the possibility that tech enthusiasts develop specially crafted drivers to allow Kaby Lake and Zen processors to run more smoothly on Windows 7 and 8.1 computers. Only time and practice will tell if this strategy is feasible.
RELATED STORIES YOU NEED TO CHECK OUT:
- Qualcomm’s Snapdragon 821 processor is 10% faster than Snapdragon 820
- New IBM processor has 1000 cores and a 1.78GHz clock speed
- Eve’s upcoming Windows 10 convertible Pyramid Flipper to feature Intel’s Kaby Lake processors
Windows 10 error 0x87af000b usually affects the Microsoft Store. This annoying error occurs more frequently than you might think. Whenever users try to download an […]
The error code 0xa00f4271 issue first arose after the Windows 10 Anniversary Update in 2016. Then users posted on Microsoft forums about a Something Went […]