I recently needed a few isolated, older production machines to run simple standalone tasks. Normally I install Windows 10 on spare Lenovo desktops, but I accidentally booted one from a USB drive created with Microsoft's official Windows 11 Media Creation Tool. To my surprise, Windows 11 installed successfully on a Lenovo with an Intel Core i5-6500, without Rufus, registry changes, or any other workaround.
In the past, I usually saw an unsupported-hardware warning on systems this old. These machines have TPM and Secure Boot available, and after upgrading the memory to 16 GB they seem to run acceptably. Has anyone else seen recent Windows 11 installation media accept 6th- or 7th-generation Intel systems? Is this only a clean-install behavior, and should I expect feature updates or regular updates to fail later?
4 Answers
A clean install and an in-place upgrade don't necessarily perform the same checks. The installer may accept a system with UEFI, Secure Boot, TPM, enough memory, and sufficient storage even if the processor itself isn't on Microsoft's supported list. Windows Update and feature upgrades are more likely to enforce the CPU requirement later, so successful installation doesn't mean the hardware is officially supported.
Some Lenovo desktops from the 6th and 7th generation already included TPM 2.0 and Secure Boot support, although TPM may need to be enabled manually in firmware. That can explain why certain systems install normally while similar-looking machines fail. The Core i5-6500 still isn't on the official supported processor list, though, so this is more of a hardware exception than a change to the published requirements.
The practical requirements are usually less strict than the advertised CPU generation cutoff. Older systems with compatible firmware, TPM, Secure Boot, and adequate RAM can run Windows 11, but performance, driver availability, management tools, and future update behavior are the real concerns. For light-duty or isolated tasks it can be useful, but newer hardware is the safer long-term choice.
That's basically how I'm viewing it. These are spare systems for lightweight jobs, not machines I'd choose for important production workloads.
I've had similar results with older systems using a clean installation. They often work normally at first, including drivers and activation, but later feature updates can fail or require another workaround. One older installation eventually stopped receiving updates correctly, so I would keep reliable backups and avoid deploying these machines where downtime or security support is critical.
That makes sense. These are noncritical machines, so I may keep them in service as a temporary option, but I won't treat the install as proof that future upgrades are guaranteed.