Windows 11 21H2/22H2/23H2/24H2/25H2 Upgrade on unsupported 64bit hardware - link

[Tell]

It's that time again with Windows 11 unsupported hardware. The annual release is out 22H2 so to do it you have to do the workaround. This changed from the one I put up last year, although there are others which got you from Windows 10 to Windows 11.

Last years link:

Windows 11 21H.... Upgrade on unsupported 64bit hardware - link (2021 Launch)

Success yesterday on an i3 and i5 64 bit computers going round the houses on WWW advice and hints. The only one that worked for me was a Github project https://github.com/coofcookie/Windows11Upgrade All the rest with regedit parameters didn't. Download your Windows 11 Iso and make sure you...

www.seatcupra.net

New Method for 22H2

This time the one that works if your hardware ticks all the boxes for memory etc but not TPM etc is this:

Notes on Windows 11 Update 22H2 Sept 2022 for Unsupported Machines

1. For work around fix for unsupported hardware

Used the site:

GitHub - AveYo/MediaCreationTool.bat: Universal MCT wrapper script for all Windows 10/11 versions from 1507 to 21H2!

Universal MCT wrapper script for all Windows 10/11 versions from 1507 to 21H2! - AveYo/MediaCreationTool.bat

github.com

for the zip file MediaCreationTool.bat-main.zip

Code and download ZIP

Open using Windows Explore zip viewer rather than 7ZIP

eg. Open with Windows Explorer, go to bypass 11 directory

Click on "Skip_TPM_Check_on_Dynamic_Update.cmd" to run it... didn't need Admin priv to run since set up as that in my case, have admin writes. This makes a change to the registry so that the ISO when run believes you have a compatible machine.

2. Now run the ISO file for Windows 11

For English International it's

Win11_22H2_EnglishInternational_x64.iso

That comes from

Download Windows 11

Make sure you select correct language as existing Windows if not it won't give you the option to retain the apps and files.... that is greyed out and you get a clean install.

There are Youtube videos

People on last years method found this was working and elsewhere. An alternative method is to fiddle with a DLL, opted for this method. The AveYo method above from Github does a RegEdit other GitHub scripts do that... you see alternatives in the comments. The DLL method you fiddle with the ISO by manually taking out the contents of the DLL and re saving with nothing in the file. Said to work. Other helpful souls provide a DLL to substitute. Another method to look at if the RegEdit methods dont work. Mentioned in the AveYo comments and found with Google.

All good for me we the AveYo method for me.

----

Footnote

Some US reports, least I think they are of it failing at the last stage on Windows Server update using the ISO. I believe Microsoft have wrapped the ISO in the Windows Server update app being lazy and the US English version stumbles on this. Completely fine on the English International ISO.

The Microsoft link above also gives the download for the normal update if your hardware is compliant e.g. the Windows Installation Assistant. You might have to run the check of whether your hardware is compliant before. It leaves a marker. One laptop I upgraded last year from Windows 10 to 11 didn't need that check this year since I ran it last year. The one shipped with Windows 11 did before it would do the normal update that will be because it needed the check run. Leave a RegEdit marker. The same markers that the workaround tools adjust.

I like to get all the hardware updated and running on the same Windows OS rather than waiting for Microsoft to offer the update if the machine is compliant. For compliant hardware it's likely to be fine. For non compliant hardware it's likely to be an annual task now to find a suitable workaround. Waste not want that and all that for that hardware that's still got life in it and you don't want to change it.

Running a network you might have fun getting network discovery to work. Vagaries of Microsoft login v Local Account login. Washing the process thru backwards and forwards.

If using a Samba Server on the network using SMB1.0 with commands to it you might have to turn Windows Feature SMB1.0 back on else it messes up Network Discovery. That gets turned off in the upgrade as they move away from SMB1.0. The bug bear for me this time round. Back to my crib sheet notes I keep. FTP I had put in to it then turned off normal network discovery. Back in to Windows Features SMB1.0 and a reboot fixed that.

CAYIN Tech | Connect a SMBv1Device via Windows 10 System

Well these are the user introduced ones rather than the sit back and wait for the update invite.

 

[Tell]

We are onto 23H2 on unsupported 64 bit hardware. Same solution as last year works here. First test the ISO after downloading your language region. If it does not moan go ahead with the install keep data and apps.

Last years Github project method shown above under 1. above holds between years. It's a toggle script. If left as is last year, just install the ISO. If it moans follow the Github project as above with this year's ISO. It's quite easy. I believe some weird processors aren't supported now on unsupported hardware but an i3 or i5 etc is. Another two years updates. We'll have to see whether next year's Windows 12 runs on unsupported hardware. Edit. Well they never released Windows 12 in 2024 it was 24h2>>>

 

[Tell]

We are onto 24h2 now. Product server method works on unsupported hardware.

 

[Tell]

Now we are onto Windows 11 25h2 on unsupported hardware. The server method to install it as per last year can be used.

First get your Windows 11 25h2 ISO. Thats here:

Download Windows 11

Use this option in the text

Download Windows 11 Disk Image (ISO) for x64 devices​

Then you can use the product server method covered in the video from Pureinfotech on this ISO:

Note when it asks to update drivers during the update you say no, keep all files and apps. It's faster not to update the drivers at installation, then just do the updates at the end.

You toggle give updates ASAP. That's normal. The sliding bar to the right. Gives you the monthly updates plus the test updates towards the end of the month. On a fully supported PC it would also check for the annual feature update when the time is right. Unsupported PC you have to do the feature update yourself which is what this is, by triggering an ISO based update.

This slider bar:

Get Windows updates as soon as they're available for your device - Microsoft Support

Learn how you can get the latest available features and enhancements if you have Windows 11, version 22H2 or later.

support.microsoft.com

If on installation it picks up that you need updates to .net frames 3.5 etc, say no to that (it's a panel, not the normal update message). First time I have seen that on one of these updates at this stage. It offers you the update for that normally within the normal check for updates. This new screen hung. Say no to that, but take the update off the normal Windows update screen later - that worked.

Reference to this:

.NET Framework - Wikipedia

en.m.wikipedia.org

At the minute with the file covered above you hit update twice, once to get the update to the release, then to the next update and again. This is sort of normal. The release update (feature update), gets updated after installation.

Installed on two tower units circa 2012 manufactured, updating to 16gb of memory with 1tb SSDs. No issues as before.

Updated with the product server method to get the annual feature update on unsupported hardware. No need to buy new kit and two more years of anti virus / hacking stuff, eg. Microsoft support or three if on the Pro release. That takes us to October 2027 for the standard Home release. 24h2 runs out next year. 23h2 next month... why you update.

Those poor Windows 10 people that haven't bitten the bullet yet. You can use this method on 64 bit machines with Windows 10 also to update to 25h2. Only processors manufactured prior to 2008 don't satisfy the unsupported hardware workaround of Windows 11 as long as you have circa 16gb of memory and SSD. There is a published base on that. Utility you can run to check the processor, but generally above 2008 you are OK. The server method is put in for corporates that don't want to throw away decent hardware. Downside, the annual feature update you have to do this way. Keeps your old hardware running that you might use as print server, office PC etc.

You need to make sure that when you pick the ISO file you specify your current installed language if you get that wrong it wont offer keep files and apps... you want to keep them else you get a fresh installation. You abandon that and get the correct ISO.

Alternatively there is a way where the ISO is manufactured for you by letting Microsoft examine your current parameters. Thats this option:

Create Windows 11 Installation Media​

More long winded thou. Best to just download the ISO and ensure you specify the current language you are on. You'll know if wrong since it won't offer you to keep files and apps.

So anyhow it seems the final release will have build 26200.6584 or greater. These builds should update to that.

If you already have fully supported Windows 11 hardware with 24h2 on you can jump start to 25h2 using this link prior to Microsoft officially releasing it:

Windows 11 25h2 Early Release if on 24h2 with fully supported hardware

It's out and you can install it. Did it on two laptops. It's in the pre release test mode as those late month updates. If you follow the instructions and the servers are good. Slight 5 minute delay till you get enrolled. You need to do the final step in the video else you'll get other builds...

www.seatcupra.net

That is just a migration package.

24h2 was more tedious to update than this release for some (driver issues). This one if on 24h2 should be straightforward for most...

Exciting times . .

Footnote. The version that will come with your Xmas PC if you were to buy one is 26200.6584 which is the one that the two unsupported PC are on here, so evidently I've found the shipping copy off their servers which is linked. That's the version provided to OEMs. That's the RTM ISO. Ive now edit that out with the actual Microsoft link.

The fully fledged Windows 11 25h2 compatible PC see the other thread.

Edit. Monday 29 September. The pre release 2nd Tuesday of the month came out. 26200.6725 is the same release now for the fully fledged Windows 25h2 early release - see other thread and this. So they have come together now on the release code. We await the 2nd Tuesday of the month now. Circa 8pm on.

Edit. Tuesday 30th September its out now... edit carried out on the text was to where the ISO is:

Download Windows 11

You do need the server method for non compatible Windows 11 hardware as described. The feature update ie. The annual update on non compatible hardware has to be done this way.

Finally after the feature update dont for get to make the Recovery Drive USB. You are suppose to rewrite that after each annual feature update.