- Joined
- Nov 3, 2011
- Messages
- 701 (0.14/day)
- Location
- Australia
System Name | Eula |
---|---|
Processor | AMD Ryzen 9 7950X |
Motherboard | MSI MPG B850 Edge Ti WiFi |
Cooling | Corsair H150i Elite LCD XT White |
Memory | Trident Z5 Neo RGB DDR5-6000 CL32-38-38-96 1.40V 64GB (2x32GB) AMD EXPO F5-6000J3238G32GX2-TZ5NR |
Video Card(s) | Gigabyte GeForce RTX 4080 GAMING OC |
Storage | Crucial P3 Plus, 4 TB NVMe, Samsung 980 Pro 2TB NVMe, Toshiba N300 10TB HDD, WDC Red Pro NAS HDD |
Display(s) | Acer Predator X32FP 32in 160Hz 4K, Corsair Xeneon 32UHD144 32in 144 hz 4K |
Case | Antec Constellation C8 RGB White |
Audio Device(s) | Creative Sound Blaster Z |
Power Supply | Corsair HX1000 Platinum 1000W |
Mouse | SteelSeries Prime Pro Gaming Mouse |
Keyboard | SteelSeries Apex 5 |
Software | MS Windows 11 Pro |
R5 2500U is 14 nm Zen 1 APU without desktop 14 nm Zen 1's chiplet and CCX-to-CCX latencies.Yes, Microsoft IS cutting out support artificially and is currently letting CPU's that don't proscribe to the DCH standard to run. Its almost like Microsoft are really good at this backward compatibility thing, but wants to ensure a certain security standard going forward. We technically saw the same thing with XP SP3 to Vista, XP SP3 brought in WDM 2.0, but wasn't enforced until Vista. That change still broke tonnes of shit as we all remember.
Pretty certain that the SP4 has an offboard TPM not part of the CPU.
And didn't say anything about Ryzen 2nd gen, only first gen.
I think after all this back and forth however we can agree on one thing, Microsoft's messaging around this is fucking idiotic when we are still all sitting around trying to figure out what the actual reasons are behind min requirements.
I do think it boils down to three things now.
A: TPM 2.0
B: Secure Boot
C: DCH drivers.
The more I think about it though, Microsoft shouldn't have launched Windows 11, and instead set a final feature pack version for unsupported hardware with say a two year security update before EOL.
I'm running Intel's latest DCH IGP drivers on Surface Pro 4's i5 6300U's IGP.
Last edited: