I have a Dell Latitude 5590 with an Intel Core i3-7130U, and it's currently running Windows 11 Pro 21H2. I used Microsoft's Media Creation Tool to make a bootable USB so I could reinstall Windows 11, but running setup.exe from the USB says that my processor isn't supported. I'm worried that booting from the USB might cause problems. If Windows 11 is already installed, why is the installer rejecting my CPU, and what's the safest way to proceed?
4 Answers
Before changing the installation, make sure your important files are backed up. Since the processor is unsupported, the least troublesome route is generally to keep a supported operating system instead of forcing Windows 11 onto the machine.
A tool such as Rufus can create installation media with the CPU, TPM, and other requirement checks removed. That may let you reinstall Windows 11, but it doesn’t make the hardware officially supported, so you could face the same issue with later upgrades or updates.
The i3-7130U is a 7th-generation processor, while Windows 11 officially supports 8th-generation Intel CPUs and newer in this class. Your current installation was probably done using a requirement bypass, which is also why it may be stuck on the older 21H2 release. You can force another installation, but unsupported hardware may have problems with future updates. Staying on Windows 10, with extended security updates if needed, is the safer supported option.
Dell says the Latitude 5590 supports Windows 11, though. Is that not enough?
The model may have been sold with supported 8th-generation processors, but that doesn’t mean every CPU option in the model meets Microsoft’s requirements. The specific i3-7130U is what matters here.
If you want to restore the laptop using Dell’s intended recovery process, try the Dell OS Recovery Tool rather than the generic Microsoft installer. It may provide the correct drivers and recovery image for the Latitude, although it still won’t change the CPU’s official Windows 11 support status.
Those bypasses can get you through setup, but they won’t solve the underlying compatibility problem when a future update checks the requirements again.