Jump to content

How to install Windows 11 on "unsupported" hardware.

GD 2W10

By GD 2W10
in Windows 11

 Share

Recommended Posts

GD 2W10

GD 2W10

Posted
  • Author
Posted
On 5/25/2022 at 3:41 PM, BYTE-ME said:

Using a custom autounattend.xml file is another fairly simple way to to install Windows 11 on "unsupported" hardware.

Placing the answer file, below, in the Root of your Windows 11 install medium will bypass the checks for Trusted Platform Module or TPM, Secure Boot and memory and storage requirements. The answer file will also create a "Main" user whose name and password you are encouraged to change. You must also search for the KMS key for your windows version and substitute it for every instance of "XXXXX-XXXXX-XXXXX-XXXXX-3V66T" in this file. 
Other modification you may or may not wish to use are annotated in the file script comments, e.g. <!-- COMMENT-->.

NOTE: You still must do disk partitioning and formatting prior to installing Windows. But if you create PID.txt and ei.cfg files and place them in  
the Windows "sources" folder on your install medium, Windows 11 setup should otherwise not require user input. 

<!--*************************************************
REV: 04/24/2022
LOCATION: MILKY WAY
USER: XXXXXX
NOTES: Admin Windows 11 Answer File
RETAIL KMS: XXXXX-XXXXX-XXXXX-XXXXX-3V66T
OVER VERSION'S KMS: https://winaero.com/windows-11-generic-keys-for-all-editions
Reference: https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend
           https://www.elevenforum.com/t/sharing-some-helpful-answer-files-to-bypass-win-11-setup-requirements-and-more.3300
           http://www.windowsafg.com
**************************************************-->
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
	<settings pass="windowsPE">
    <!--Language-->
	<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
			<SetupUILanguage>
				<UILanguage>en-US</UILanguage>
			</SetupUILanguage>
			<InputLocale>0409:00000409</InputLocale>
			<SystemLocale>en-US</SystemLocale>
			<UILanguage>en-US</UILanguage>
			<UILanguageFallback>en-US</UILanguageFallback>
			<UserLocale>en-US</UserLocale>
	</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
               <!--Skip Trusted Platform Module / Secure Boot Check-->
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>3</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>5</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>4</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
<UserData>
	<AcceptEula>true</AcceptEula>
		<FullName>MainUser</FullName>
		<Organization>Default</Organization>
<!-- OEM Installer Product ID Key. Do not change/uncomment-->
    <ProductKey>
        <Key>XXXXX-XXXXX-XXXXX-XXXXX-3V66T</Key>
    </ProductKey>
</UserData>
</component>
</settings>
<!-- Skip EULA OEM Installer-->
<settings pass="offlineServicing">
<component name="Microsoft-Windows-LUA-Settings" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<EnableLUA>false</EnableLUA>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-SQMApi" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<!--Turn off Windows Customer Experience Improvement Program; substitute "1" to enable-->
<CEIPEnabled>0</CEIPEnabled>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>PC-NAME</ComputerName>
<ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-3V66T</ProductKey>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<!--Auto Logon-->
<AutoLogon>
<Password>
	<Value>ADD-MY-PASSWOR-HERE</Value>
		<PlainText>true</PlainText>
	</Password>
		<Enabled>true</Enabled>
	   <LogonCount>4</LogonCount>
	<Username>MainUser</Username>
</AutoLogon>
<!--Auto Logon-->
<OOBE>
<!--Customize Windows Out of Box Experience-->
<HideEULAPage>true</HideEULAPage>
	<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
	<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
	<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
	<NetworkLocation>Work</NetworkLocation>
	<SkipUserOOBE>true</SkipUserOOBE>
	<SkipMachineOOBE>true</SkipMachineOOBE>
	<UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
<!--Disable automatic protection and enable certain MS Telemetry; Other values are 1 = Recommended (default) level of protection and 2 = Only updates are installed.-->
	<ProtectYourPC>3</ProtectYourPC>
</OOBE>
<UserAccounts>
<!--User Accounts-->
    <LocalAccounts>
        <LocalAccount wcm:action="add">
			<Name>MainUser</Name>
			<Group>Administrators</Group>
		<Password>
            <Value>ADD-MY-PASSWORD-HERE</Value>
            <PlainText>true</PlainText>
            </Password>          
            <DisplayName>Main User Name</DisplayName>
         <Description>MAIN USER</Description>
	</LocalAccount>
</UserAccounts>
<RegisteredOrganization>Default</RegisteredOrganization>
	<RegisteredOwner>Default</RegisteredOwner>
	<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
	<Description>Control Panel View</Description>
		<Order>1</Order>
	<CommandLine>reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel" /v StartupPage /t REG_DWORD /d 1 /f</CommandLine>
		<RequiresUserInput>true</RequiresUserInput>
</SynchronousCommand>
<!-- Set Control Panel icons small-->
<SynchronousCommand wcm:action="add">
	<Order>2</Order>
		<Description>Control Panel Icon Size</Description>
	<RequiresUserInput>false</RequiresUserInput>
		<CommandLine>reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel" /v AllItemsIconView /t REG_DWORD /d 0 /f</CommandLine>
</SynchronousCommand>
<!-- Set User Password Never Expires-->
<SynchronousCommand wcm:action="add">
<Order>3</Order>
<RequiresUserInput>false</RequiresUserInput>
<CommandLine>cmd /C wmic useraccount where name="MainUser" set PasswordExpires=false</CommandLine>
<Description>Password Never Expires</Description>
</SynchronousCommand>
</FirstLogonCommands>
<!-- Set Time Zone-->
<TimeZone>FLE Standard Time</TimeZone>
</component>
</settings>
</unattend>

 

I did not know this was a method. I will try it out- will add this as a method if it ends up working.

Link to comment
Share on other sites

BYTE-ME

BYTE-ME

Posted
Posted (edited)

I recommend you remove my comments before testing. Sometimes Windows gets sensitive about Autounattend.xml file size. Good luck.

Edited by BYTE-ME
Link to comment
Share on other sites
GD 2W10

GD 2W10

Posted
  • Author
Posted
6 hours ago, bookie32 said:

I have to ask....Is there really any point to this?

Microsoft don't want us to use older computers....so why waste the energy?

 

bookie32

 

 

A lot of people can’t afford newer computers, and even some of the newer computers (eg. 2019/20 Intel MacBook Pro) can’t “run” Windows 11. But since Windows 11 technically is like a big Windows 10 update, it works fine.

2
Link to comment
Share on other sites
Dave-H

Dave-H

Posted
Posted
13 hours ago, bookie32 said:

I have to ask....Is there really any point to this?

Microsoft don't want us to use older computers....so why waste the energy?

bookie32

I think the short answer to your question is because we're enthusiasts, and because we can!
(Oh, and we don't like being told by the likes of Microsoft that we can't do something!)
:lol:
 

3
Link to comment
Share on other sites
bookie32

bookie32

Posted
Posted
6 hours ago, Dave-H said:

I think the short answer to your question is because we're enthusiasts, and because we can!
(Oh, and we don't like being told by the likes of Microsoft that we can't do something!)
:lol:
 

Good answer:buehehe:

Link to comment
Share on other sites
bookie32

bookie32

Posted
Posted
13 hours ago, GD 2W10 said:

A lot of people can’t afford newer computers, and even some of the newer computers (eg. 2019/20 Intel MacBook Pro) can’t “run” Windows 11. But since Windows 11 technically is like a big Windows 10 update, it works fine.

I agree but we will never tame Microsoft....they are a bunch of twats that will always go their own way despite user input....

Link to comment
Share on other sites
GD 2W10

GD 2W10

Posted
  • Author
Posted
14 hours ago, kosamja said:

time to buy SSD: https://news.softpedia.com/news/microsoft-planning-to-kill-off-the-traditional-hdd-for-windows-11-boot-drives-535535.shtml

I think a potential workaround for this would be installing Windows 11 with the Windows 10 setup. But I’m sure there’d be some registry hack to bypass this, unless Microsoft puts a recovery error at startup not allowing it to boot from HDD.

Link to comment
Share on other sites
GD 2W10

GD 2W10

Posted
  • Author
Posted
18 hours ago, bookie32 said:

I agree but we will never tame Microsoft....they are a bunch of twats that will always go their own way despite user input....

Very true lol

1
Link to comment
Share on other sites
UCyborg

UCyborg

Posted
Posted (edited)

I saw a discussion on Reddit recently on Win10 subreddit regarding Win10 and HDDs, which applies to Win11 as well due to similarity. It was said it's not so much about Win10 being poor with HDDs, but rather modern HDDs performing poorly due to SMR (Shingled Magnetic Recording) technology and manufacturers not giving a damn because everyone buys a SSD for boot drive or blames Windows for bad performance otherwise.

Not up-to-date on Win11, but with the first release, you could just do "DISM /ApplyImage" to install the OS from the Command Prompt (Shift + F10) in the setup environment without tampering with anything, no system requirement checks were run then.

In my experience, Win10/11 are unusually slower to login, they messed up file enumeration performance since Windows 8.1, at least noticeable in Explorer when you check the properties of a folder, no idea if it's still like this and finally there's some more background noise by default. Seem a bunch of background tasks can be turned off without much compromise on the functionality.

So still humming along with older HDDs and relatively up-to-date OS. Also, I might be one of the more patient people alive today.

Edited by UCyborg
Link to comment
Share on other sites
GD 2W10

GD 2W10

Posted
  • Author
Posted (edited)
On 6/11/2022 at 2:23 AM, UCyborg said:

everyone buys a SSD for boot drive or blames Windows for bad performance otherwise.

However, some people are not able to afford SSDs of large capacity, and some newer computers (such as laptop) don't have SATA cables.

On 6/11/2022 at 2:23 AM, UCyborg said:

Not up-to-date on Win11, but with the first release, you could just do "DISM /ApplyImage" to install the OS from the Command Prompt (Shift + F10) in the setup environment without tampering with anything, no system requirement checks were run then.

Yes that is another method to install Windows 11. I will add that. You also need to run diskpart or some program to make the partitions, bcdboot, and potentially bootrec. You are able to install Vista-11 like that.

Edited by GD 2W10
Link to comment
Share on other sites
GD 2W10

GD 2W10

Posted
  • Author
Posted
On 8/1/2021 at 6:08 PM, GD 2W10 said:

These are methods that can be found anywhere on the internet, but I wanted to post it here. With this tutorial you should be able to install Windows 11 on any PC that supports Windows 10 x64.

Method 1: Install Windows 11 with the Windows 10 Setup (clean install ONLY method, does not work with the modern setup, therefore it cannot upgrade) (best clean install method):

1. Get a Windows 10 x64 ISO. You can do this with the Media Creation Tool, or with Windows ISO Downloader.

2. Copy the contents of the ISO to a folder. Go to sources and delete "install.wim" or "install.esd".

3. Get a Windows 11 ISO

4. Mount the Windows 11 ISO.

5. Go to the sources folder, and copy "install.wim" or "install.esd"

6. Paste the install.wim/esd file into the Windows 10 x64 sources folder.

Here’s how to make it into an ISO:

7. Download and install NTLite. https://www.ntlite.com/ 

8. Once you have installed it, select "Free", unless you have a license.

9. Click "Add" > "Image directory"

10. Select the Windows 10 setup with the Windows 11 "install.wim/esd" folder.

11. Right click on "install.wim/esd", and click "Create ISO"

Method 2: Upgrade/Install Windows 11 with the Windows 10 "appraisesres.dll" file (upgrade + clean install method, this method ONLY works with the Modern Windows Setup, using the other setup will still give you the "This PC can't run Windows 11" error) (best method for upgrading):

1. Get a Windows 11 ISO. 

2. Copy the contents of the ISO to a folder. Go to sources and delete "appraisesres.dll"

3. Get a Windows 10 x64 ISO. You can do this with the Media Creation Tool, or with Windows ISO Downloader.

4. Mount the Windows 10 x64 ISO.

5. Go to the sources folder, and copy "appraisesres.dll" to the sources folder into the Windows 10 ISO.

6. Paste the file into the "sources" folder in the Windows 11 directory. When you run the setup, it should check to see if it is capable for Windows 10 and not 11.

If you want to make this into an ISO, refer to the instructions in Method 1. If it still doesn't let you install Windows, try turning off the Wi-fi and then run the setup.

Method 3: Install Windows 11 using DISM, DISKPART, and BCDBOOT (clean install only)

This method only requires a Windows 11 ISO. If you are trying to dual boot on the same hard drive, the partitioning steps will be different.

1. Boot your Windows 11 media

2. Open a command prompt window (You can do this by pressing Shift+F10)

3. Open diskpart by typing in "diskpart" in the command prompt window. If you are installing on BIOS, refer to the Legacy commands. If you are installing on UEFI, refer to the UEFI commands.

Legacy:

diskpart

sel dis 0

clean (this wipes your hard drive)

conv mbr

cre par prim size=100

form quick fs=ntfs label="System Reserved"

assign letter w

active

cre par prim

form quick

assign letter c

exit

UEFI:

diskpart

sel dis 0

clean (this wipes your hard drive)

conv gpt

cre par efi size=100

form quick fs=fat32 label="System Reserved"

assign letter w

active

cre par prim

form quick 

assign letter c

exit

4. After partitioning the drive, go to the sources folder by typing in "cd /d D:(where your Windows 111 media is)\sources

5. Type in the following commands:

dism /apply-image /imagefile:install.wim(.esd) /index:(1 for Home, 6 for Pro) /applydir:C:\

bcdboot C:\Windows /s W: /f ALL

bootrec /scanos

bootrec /fixmbr

bootrec /fixboot

bootrec /rebuildbcd

6. Now reboot. Windows setup will then continue normally. If it doesn't boot, run Startup Repair. 

 

 

 

 

I added a third method.

Link to comment
Share on other sites
UCyborg

UCyborg

Posted
Posted
30 minutes ago, GD 2W10 said:

You also need to run diskpart or some program to make the partitions, bcdboot, and potentially bootrec. You are able to install Vista-11 like that.

Indeed, I wrote the post with the assumption that anyone familiar installing Windows using DISM is familiar with preparation steps.

30 minutes ago, GD 2W10 said:

However, some people are not able to afford SSDs of large capacity

True.

Windows tends to preload a bunch of files that are used frequently and maybe some less frequent ones, Vista in particular will cache whatever it can, Windows 7 is easier on caching, but it seems by Windows 10 they made it more active again. That can help in a way that files might be ready by the time you need them. Best to wait after login for stuff to get loaded.

Maybe it doesn't work so well with highly diverse workflows. Some also find RAM disks useful for certain things.

Link to comment
Share on other sites
bookie32

bookie32

Posted
Posted

Another thing I noticed...end of life Windows 11 next year? It has been out five minutes and now end of life?!!

I think it should be end of life for Microsoft and be done with it...

What crap will they demand to install Windows 12?

 

bookie32

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...