Microsoft has spent years debating whether Windows 11 hardware requirements are too high. Now a fresh argument is gaining traction: the red-tape might be exactly what the OS needs. According to an opinion piece on Neowin, Windows 11 should adopt the kind of mandatory enforcement that Google recently rolled out for Chrome, locking out machines that fall below the performance line.
The takeaway is blunt. If a piece of hardware cannot run the modern web smoothly, it should not be able to run Windows 11 either. That is a provocative stance, and it deserves a closer look at what actually changed, who it affects, and how it would land for everyday users.
What Google just made mandatory
Google did not quietly raise its standards. It made them enforceable. Chrome began rolling out a set of minimum hardware requirements, and unlike past notices, these are now baked into the browser itself rather than living on a support page.
Under Chrome’s new baseline, a device needs a 64-bit operating system, a dual-core processor running at 1 GHz or faster, at least 2 GB of RAM, and roughly 4 GB of free storage to keep receiving updates and full functionality.
The enforcement is staged across releases. Chrome 129 started showing a “Your device may stop working” notice, Chrome 132 began blocking fresh installs on non-compliant machines, and later builds move toward rendering limits. The point is deliberate: Google is no longer asking, it is measuring.
Windows 11 hardware requirements today
Windows 11 already lists a hardware checklist, but it has historically treated it as a guideline rather than a gate. The official call asks for a 1 GHz or faster dual-core 64-bit CPU, 4 GB of RAM (raised from 2 GB in the 24H2 update), 64 GB of storage, UEFI firmware with Secure Boot capability, a version 2.0 TPM chip, and a 720p display.
Here is the gap: the box on the installer that says “This PC looks like it meets the system requirements” has often been a suggestion. Power users have long found ways around it, and Microsoft has tolerated the workaround.
The leniency problem
The core of the Neowin argument is that Windows 11’s enforcement is softer than Chrome’s. Tools exist that skip the CPU, RAM, storage, and TPM checks. Registry tweaks such as BypassTPMCheck, BypassRamCheck, and BypassStorageCheck can clear the certification screen, and community media creation utilities have packaged these edits into a one-click install.
From Microsoft’s side, that leniency has been partly intentional. IT admins and enthusiasts who manage older hardware have relied on these paths for years, and a hard cutoff would strand them. But the counterargument is that soft enforcement muddies the experience: you can install Windows 11 on hardware it was designed to run well on, then wonder why it does not.
What this means for you
For most users, nothing changes overnight. If your machine meets the 24H2 spec, you are fine either way. The debate only bites for owners of older or budget hardware who have leaned on the bypass routes to keep a capable-feeling system.
If you are running a build installed through a workaround, be aware that a future feature update or a stricter enforcement policy could flag your installation. The practical risk is not a wipe, but a nagging compatibility notice and a slower, bumpier daily experience on thin hardware.
How to prepare
The sensible move is to know your numbers. Check your CPU, RAM, and storage against the 24H2 requirements, and confirm your firmware supports UEFI and Secure Boot. If you are on a marginal build, keep a clean backup image before any major update, and test that recovery path works.
For IT admins managing a fleet, watch for any shift in how Windows Update handles non-compliant builds. A change here would land differently than a Chrome-style notice: it would touch deployment tooling, WSUS, and Intune policies across your whole estate.
Whether Microsoft adopts a Google-style cutoff remains speculative. The Neowin piece is an opinion, not a changelog, so treat any “enforcement coming” talk as context rather than a confirmed date. But the direction is clear: the bar is being raised, and the question is whether Windows 11 will finally enforce it.
Source: Neowin
Over to you: Would you accept a Windows 11 “Your device may stop working” notice on a low-spec machine, or keep the bypass routes?
You may also like
Windows 11 Cloud Rebuild now wipes drives securely and can be rebuilt remotely by IT admins
Microsoft’s Research Boss Explains Why Windows 11 Features Don’t Show Up — and His Fix Only Partially Works
Hands On: Windows 11’s New Magnifier Contrast Themes Reduce Screen Glare
Windows 11 Start menu changes arrive in Future Platforms build 29671.1000
