SomeGuy
Veteran Member
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.
VCF East | Apr 04 - 06 2025, | Infoage Museum, Wall NJ |
VCF Southwest | Jun 20 - 22 2025, | University of Texas at Dallas |
VCF Southeast | Jun 20 - 22 2025, | Atlanta, GA |
VCF West | Aug 01 - 02 2025, | CHM, Mountain View, CA |
VCF Midwest | Sep 13 - 14 2025, | Schaumburg, IL |
VCF SoCal | Feb TBD, 2026, | Hotel Fera, Orange CA |
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.
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 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.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.
What about it? Did you mean Unobtanium?.What about Itanium?
Windows 11 does not support IA-64, as far as I can tell.What about Itanium?
Windows 11 does not support IA-64, as far as I can tell.
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.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.
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.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.
Display: High definition (720p) display, 9" or greater monitor, 8 bits per color channel.
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.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.
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.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.