• Please review our updated Terms and Rules here

What is the oldest CPU (AMD or Intel) that will enable Windows 11 unofficially?

As far as why - it is enough that Microsoft is increasingly lying and placing artificial requirements on their software, and they need to be called out on it when they do.
 
As far as why - it is enough that Microsoft is increasingly lying and placing artificial requirements on their software, and they need to be called out on it when they do.
My favorite answer to why in regards to trying windows 11 is ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.
 
As far as why - it is enough that Microsoft is increasingly lying and placing artificial requirements on their software, and they need to be called out on it when they do.

I remember SBS 2008 minimum requirement was a low-mid range Proliant. The same ones we used to run for 24/7 image and sensory data processing for outside fire recognition system supporting dozens of devices and sources, was a minimum for 15ish mailboxes per Microsoft.
 
I would classify Linux as a task, not a game. Now. now, never said I "hated" it, just don't want it anywhere on any of my boxum.
 
Since this a vintage computer forum, I'm more interested in what OS I can use to keep my aging PC's and laptops still be able to be used online without being a virus magnet. I'm typing this post on a Gateway MA3 running Zorin 17 Lite which replaced the 32 bit XP install it came with. Limited to 2GB ram and a soldered on Turion 64 Mobile CPU plus a lack of 64 bit Windows 7 drivers sidelined it otherwise. OBTW, try Windows !! on one of these and you'll know you've reached the bottom limits.
 
As far as I'm aware, the CPU must be 64 bit, support the XD bit and SSE3, and support the POPCNT CPU instruction.

I ran a quick search, but did not see this asked already, thanks.

Why 11? Because I want to.
The oldest x86-64/AMD64/Intel64 processor would be the AMD Opteron, around spring 2004. The next one might be an Intel Xeon, or AMD Althon 64, or Intel Pentium 4 around summer 2004. Of course, it doesn't necessary mean that Windows 11 would run on those.

Someone on youtube had it force installed on a P4 Cedar Mill.
 
Lifted from a MS source:

Windows 11 requirements​

  • Article
  • 03/13/2024
  • 9 contributors
  • Applies to:✅ Windows 11
Feedback

In this article​

  1. Hardware requirements
  2. OS requirements
  3. Feature-specific requirements
  4. Virtual machine support
  5. Next steps
This article lists the system requirements for Windows 11. Windows 11 is also supported on a virtual machine (VM).

Hardware requirements​

To install or upgrade to Windows 11, devices must meet the following minimum hardware requirements:
  • Processor: 1 gigahertz (GHz) or faster with two or more cores on a compatible 64-bit processor or system on a chip (SoC).
  • Memory: 4 gigabytes (GB) or greater.
  • Storage: 64 GB or greater available disk space.
    Note
    There might be more storage requirements over time for updates, and to enable specific features within the OS. For more information, see Windows 11 specifications.
  • Graphics card: Compatible with DirectX 12 or later, with a WDDM 2.0 driver.
  • System firmware: UEFI, Secure Boot capable.
  • TPM: Trusted Platform Module (TPM) version 2.0.
  • Display: High definition (720p) display, 9" or greater monitor, 8 bits per color channel.
  • Internet connection: Internet connectivity is necessary to perform updates, and to download and use some features.
    • Windows 11 Home edition requires an internet connection and a Microsoft Account to complete device setup on first use.
For more information, see the following Windows Insider blog post: Update on Windows 11 minimum system requirements.
For more information about tools to evaluate readiness, see Determine eligibility.

OS requirements​

To upgrade directly to Windows 11, eligible Windows 10 devices must meet both of the following criteria:
  • Running Windows 10, version 2004 or later.
  • Installed the September 14, 2021 security update or later.
Note
  • S mode is only supported on the Home edition of Windows 11.
  • If you're running a different edition of Windows in S mode, before upgrading to Windows 11, first switch out of S mode.
  • To switch a device out of Windows 10 in S mode also requires internet connectivity. If you switch out of S mode, you can't switch back to S mode later.

Feature-specific requirements​

Some features in Windows 11 have requirements beyond the minimum hardware requirements.
  • 5G support: requires 5G capable modem.
  • Auto HDR: requires an HDR monitor.
  • BitLocker to Go: requires a USB flash drive. This feature is available in Windows Pro and above editions.
  • Client Hyper-V: requires a processor with second-level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and greater.
  • DirectStorage: requires an NVMe SSD to store and run games that use the Standard NVM Express Controller driver and a DirectX12 GPU with Shader Model 6.0 support.
  • DirectX 12 Ultimate: available with supported games and graphics chips.
  • Presence: requires sensor that can detect human distance from device or intent to interact with device.
  • Intelligent Video Conferencing: requires video camera, microphone, and speaker (audio output).
  • Multiple Voice Assistant: requires a microphone and speaker.
  • Snap: three-column layouts require a screen that is 1920 effective pixels or greater in width.
  • Mute and unmute: from Taskbar requires video camera, microphone, and speaker (audio output). App must be compatible with feature to enable global mute/unmute.
  • Spatial Sound: requires supporting hardware and software.
  • Microsoft Teams: requires video camera, microphone, and speaker (audio output).
  • Touch: requires a screen or monitor that supports multi-touch.
  • Two-factor authentication: requires use of PIN, biometric (fingerprint reader or illuminated infrared camera), or a phone with Wi-Fi or Bluetooth capabilities.
  • Voice Typing: requires a PC with a microphone.
  • Wake on Voice: requires Modern Standby power model and microphone.
  • Wi-Fi 6E: requires new WLAN IHV hardware and driver and a Wi-Fi 6E capable AP/router.
  • Windows Hello: requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or portable Microsoft compatible security key. For more information, see IT tools to support Windows 10, version 21H1.
  • Windows Projection: requires a display adapter that supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct.
  • Xbox app: requires an Xbox Live account, which isn't available in all regions. Go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app require an active Xbox Game Pass subscription.

 
Windows 11 does not support IA-64, as far as I can tell.

Windows 11 on IA-64? 🤣 Windows Server 2008 R2 released in 2009 was the last version of Windows with IA-64 support.

As far as I can remember, Windows XP was the last non-server version with IA-64 support, and non-server IA-64 support was canceled during the extended Windows Vista development cycle.
 
Windows 11 on IA-64? 🤣 Windows Server 2008 R2 released in 2009 was the last version of Windows with IA-64 support.

As far as I can remember, Windows XP was the last non-server version with IA-64 support, and non-server IA-64 support was canceled during the extended Windows Vista development cycle.
Oh hey, I did not realize XP could run on Itaniums. I had been told only the very rare 64 bit windows 2000 ran on them. Been ages since I knew anyone with an Itanium though.
 
As far as why - it is enough that Microsoft is increasingly lying and placing artificial requirements on their software, and they need to be called out on it when they do.
The answer is that they are not (really) lying. When you remove some of those requirements, you also remove compliance with the various security requirements that are now in place around the world. So for example TPM versions less than 2.0 only support SHA-1 signing which is now being depreciated due to vulnerabilities in it. So whilst you can run Windows/11 on down-level hardware it will no longer be (able to achieve) PCI or HIPPA compliance.

So allowing it to run on older hardware would instantly produce a string of security vulnerabilities.
 
But is it not the responsibility of the installer to ensure their hardware meets PCI or HIPPA compliance?

Artificial "requirements" like that are a lot like seatbelt laws. Yes seatbelts save lives, but its still not Microsoft's job to force us to meet HIPPA compliance. Personal responsibility and proper security auditing begin at home. Or at work, in this case.

This metaphor may have gotten away from me.
 
But is it not the responsibility of the installer to ensure their hardware meets PCI or HIPPA compliance?

Artificial "requirements" like that are a lot like seatbelt laws. Yes seatbelts save lives, but its still not Microsoft's job to force us to meet HIPPA compliance. Personal responsibility and proper security auditing begin at home. Or at work, in this case.

This metaphor may have gotten away from me.
I think like seat-belts, its the modern way. For Microsoft to promote windows as being safe and secure it must only run on safe and secure hardware.
 
I think like seat-belts, its the modern way. For Microsoft to promote windows as being safe and secure it must only run on safe and secure hardware.
When I was a child I once had a conversation with my dad about why, if wearing a seatbelt was the law, cars did not have an elaborate series of sensors to detect and prevent the car from starting if everyone inside wasn't buckled up. This is when I first learned about the concept of the nanny state and why seatbelt laws were stupid.

You shouldn't need a law to tell you to wear a seatbelt any more than you should need an artificial systems check to prevent you from using insecure hardware. Its just M$ being nanny-sysadmins and its irritating.
 
MS has been blasted for letting admins install with less than fully secure defaults. If adding security is basically free with all the systems being built now, why not implement it. There just won't be enough users of decade old hardware to make testing on those machines worth the effort.
 
Seatbelts and helmets and stuff I don't see as nanny state, nanny would at least imply some interest of the state to keep you safe from harm, they don't, this is just collecting money, both for insurance companies and directly for state budget via tickets.

I had a mountain bike accident in the forest, and had an ER pick me up, they told me they'll write down I tripped while hiking, because bike equals traffic accident, cops get involved, they'll absolutely find something to file a ticket about, like my bike lacking reflectors and usual shit you just don't put on mountain bikes, etc. No nannies, just free $ for the state.
 
Seatbelts, helmets, and stuff ARE exactly that. We all know they are the right choice but forcing people to use them makes no sense. I dont care if the other driver is not wearing his seatbelt. Thats thier choice. They shouldnt be ticketed for not wearing it either, It doesnt change thier behavior as a driver. NEVER USING YOUR TURN SIGNALS HOWEVER GREATLY IMPACTS OTHER DRIVERS... But that is not a ticketable offence apparently.

Way off track I know. But Im for what @hunterjwizzard stated. Its an awful way of administrating and its highly annoying.
 
Back
Top