Forum Discussion
Doncizks2725
Feb 19, 2024Copper Contributor
How to bypass windows 11 system requirements during installation on an old Laptop?
Hi, I have a Dell XPS 13 laptop bought in 2016. It comes with Intel Core i5-5200U, 4GB RAM and 128 SSD. When I am trying to install Windows 11 from a USB drive on this laptop, an error pops up an...
- Feb 22, 2024
Apparently, the CPU and RAM don't meet the Windows 11 system requirements. The CPU should be Intel 8th Gen and RAM should be 8GB or more.
One of the easier methods to install Windows 11 on unsupported hardware is to modify the Windows Registry during the installation process. This method involves creating a Windows 11 installation media, booting from it, and then making a registry change before the compatibility check.1. Go to the official Microsoft website to download the Windows 11 ISO file.
2. Use tools like Windows Media Creation Tool to create a bootable Windows 11 USB drive from the ISO file.
3. Boot your PC from the USB drive and start the Windows 11 installation process. Follow the prompts until you reach the screen where it says your PC can't run Windows 11.
4. Press Shift + F10. This key combination opens a Command Prompt window during the installation process.
5. In the Command Prompt, type regedit and press Enter to open the Registry Editor. Now, navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup.
6. Right-click on the Setup key, select New > Key, and name it LabConfig. Inside the LabConfig key, create new DWORD (32-bit) Value entries with the following names and values:
BypassTPMCheck and set its value to 1.
BypassSecureBootCheck and set its value to 1.
Create BypassCPUCheck and set its value to 1.7. Close Registry Editor and the Command Prompt, then continue with the installation process. The setup should now bypass Windows 11 system requirements.
Karl-WE
Feb 19, 2024MVP
major concerns are the following:
- Microsoft may not automatically upgrade your version in annual releases
- The device will be very slow and CPU load very high, as it needs to emulate security related tasks that depend on virtualization
- older drivers especially Intel HD graphics do not support Core Isolation
I have stopped using these "tricks" for these reasons, as the performance was greatly reduced. Thus the reasons why the system requirements are not arbitrary, even though the communication about the "why" could have been better. There is lot of rumour about these requirements, still.
Sure thing everyone should use fTPM (in CPU) instead of TPM chips (outside CPU on mainboard).
dbrown900
Aug 20, 2024Copper Contributor
Hey Karl, I was reading the responses and wanted to share my specs for an older Sony VAIO that I occasionaly use with win 10 Pro. I do have a new VAIO since they are being made once again, under license of Sony with win 11. here are my specs, what do you think about 11 on my old VAIO? Thanks!
OS Name Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DOUG-NEWVAIO
System Manufacturer Sony Corporation
System Model VPCEB19GX
System Type x64-based PC
System SKU N/A
Processor Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz, 2400 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. R0300Y8, 7/20/2010
SMBIOS Version 2.6
Embedded Controller Version 3.00
BIOS Mode Legacy
BaseBoard Manufacturer Sony Corporation
BaseBoard Product VAIO
BaseBoard Version N/A
Platform Role Mobile
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.3636"
User Name DOUG-NEWVAIO\Doug
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.86 GB
Available Physical Memory 2.63 GB
Total Virtual Memory 15.9 GB
Available Virtual Memory 8.95 GB
Page File Space 8.00 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
OS Name Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DOUG-NEWVAIO
System Manufacturer Sony Corporation
System Model VPCEB19GX
System Type x64-based PC
System SKU N/A
Processor Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz, 2400 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. R0300Y8, 7/20/2010
SMBIOS Version 2.6
Embedded Controller Version 3.00
BIOS Mode Legacy
BaseBoard Manufacturer Sony Corporation
BaseBoard Product VAIO
BaseBoard Version N/A
Platform Role Mobile
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.3636"
User Name DOUG-NEWVAIO\Doug
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.86 GB
Available Physical Memory 2.63 GB
Total Virtual Memory 15.9 GB
Available Virtual Memory 8.95 GB
Page File Space 8.00 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes