• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

Windows 11 Pro 25H2 (insider preview) free upgrade installation on officially-unsupported outdated PC

I succeeded in upgrading two Windows 10 computers to Windows 11, using rufus-4.11.exe and
26200.6584.250915-1905.25h2_ge_release_svc_refresh_CLIENT_CONSUMER_x64FRE_en-us.iso
Is it possible that Microsoft disabled the upgrade in later versions of the iso?
 
I've seen this upgrade issue as well. I believe it's because you can only upgrade to Windows 11 from Windows 10 22H2 - you can't upgrade to Windows 11 from 21H2.
 
Is it a W10 LTSC version by chance?

Or possibly some incompatible SW that is failing a validation check or similar?
 
At around Windows95 time frame -when employing multiple disk drives became a much less costly option- I had decided that dedicating the primary "C:\" drive just for installing the OS and applications. I wanted to make sure that when those imminent OS crashes (BSODs) and/or drive failures occurred, they would not also take down all of my personal files, applications' settings, etc. away, along with such unrecoverable catastrophes.
@dualazmak, I have just tried your 'setup.exe /product server' method for upgrading my Windows 10 Pro main PC to Windows 11 Pro 25H2, but the option to "keep/preserve all files, settings, applications" is greyed out and not available. I only have the options for preserving user files or preserving nothing available. I am using the Englishinternational_x64.iso image. Is it possible that only the Japanese ISO image allows a full, in situ upgrade to Win 11 using this method?
@Monster, the job to "keep/preserve all files, settings, applications" becomes your personal responsibility by spanning them out to other (HDD/SSD/NVMe) drives that are NOT the primary "C:\" drive.
This will also allow you to keep the primary "C:\" OS drive under 500GB, with faster access and less Read/Write cycles to have it last longer. Data back-ups also become a no-brainer.
 
OK, the problem is mostly sorted.

It seems that when I built this PC about 10 years ago the Windows 7 installation disk had the default language as US English. I have now downloaded the Win 11 English_x64.iso instead of the English international version and followed @dualazmak instructions for using 'setup.exe /product server' and it all sort of worked and it allowed me to do an upgrade preserving all files, settings and apps.

The only problem I need to sort out now is that it boots fine from a cold boot but hangs and reports a boot disk failure on restart. I'm sure it'll all be sorted in the end and, if not, I still have my original Windows 10 system disk that I can just reconnect and go back to square one.
 
Last edited:
The only problem I need to sort out now is that it boots fine from a cold boot but hangs and reports a boot disk failure on restart. I'm sure it'll all be sorted in the end and, if not, I still have my original Windows 10 system disk that I can just reconnect and go beck to square one.
Always helps to be vigorous in making back-ups/archives of OS drives, as well as data drives.
Acronis? Macrium? EaseUS? << Another no-brainer!
 
The only problem I need to sort out now is that it boots fine from a cold boot but hangs and reports a boot disk failure on restart.
You would please check if the OS has/recognizes multiple bootable disks/partitions; you can check it by "msconfig" - "boot".
If you find multiple bootable entries, delete the other ones so that the entry has only "Windows **: present OS; default OS".
 
Last edited:
You would please check if the OS has/recognizes multiple bootable disks/partitions; you can check it by "msconfig" - "boot".
If you find multiple bootable entries, delete the other ones so that the entry has only "Windows **: present OS; default OS".

Just the one bootable partition present.

I did check before I started the upgrade to make sure there was only the one bootable partition then as well.
 
Last edited:
Just the one bootable partition present.

I did check before I started the upgrade to make sure there was only the one bootable partition then as well.
Understood!

By the way,
The only problem I need to sort out now is that it boots fine from a cold boot but hangs and reports a boot disk failure on restart.
Do you mean you have the "boot disk failure" on awake after hibernation/sleep, but none on cold boot after complete "shutdown"?

Just for your interest and reference, I have been always hating Windows "hibernation" features. I never trust "sleep (hibernation) mode"!
I always make "OFF/DISABLE" the hibernation features, and also have deleted "hiberfil.sys" at the root of drive C: giving me some more free space in drive C::D
 
I have been always hating Windows "hibernation" features.
I find it more peaceful to just ignore that :mad: hibernation function altogether... as I have been doing, since its introduction in Windows2000.
The only problem I need to sort out now is that it boots fine from a cold boot but hangs and reports a boot disk failure on restart. I'm sure it'll all be sorted in the end and, if not, I still have my original Windows 10 system disk that I can just reconnect and go back to square one.
Some Window11 built-in tools besides the TroubleShooting and Diagnostic applet
• Fast StartUp On/Off
• Restore Points
• StartUp Repair
• SystemFileChecker (SFC) commands
• Disk + FileSystem check/repair "chkdsk" commands
• Deployment Image Servicing and Management "DISM" commands
• Windows RecoveryEnvironment (WinRE)
Best of all, there is the Event Viewer that can be your friend- It can show you which apps are delaying shutdown:
• Press Win + X and select Event Viewer
• Navigate to Applications and Services Logs > Microsoft > Windows > Diagnostics-Performance > Operational
• Look for Event ID 203 (shutdown delays) to see which applications are causing problems
• Once identified, update, reinstall, or uninstall the problematic software
 
Well, the saga continues.

After a bit more research I tried to reboot the PC into Win 11 recovery mode. All this succeeded in doing was making it so the the machine wouldn't reboot at all, neither from the initial restart nor from a cold boot. So I started again by cloning my Win 10 disk.

This time I checked that the cloned disk worked perfectly under Win 10, both restarting and booting from cold. No disk errors are reported by Samsung Magician. Everything was just fine. Then I redid the 'upgrade' to Win11 again.
Do you mean you have the "boot disk failure" on awake after hibernation/sleep, but none on cold boot after complete "shutdown"?

Just for your interest and reference, I have been always hating Windows "hibernation" features. I never trust "sleep (hibernation) mode"!
I always make "OFF/DISABLE" the hibernation features, and also have deleted "hiberfil.sys" at the root of drive C: giving me some more free space in drive C::D

Following the upgrade the restart problem is still there. It boots perfectly from a cold shutdown state. It wakes up fine from 'sleep'. Hibernation is turned off. Fast startup is turned off. I have reset the the BIOS so that the boot disk is the first in the boot order. Nothing I have done makes any difference.

I'm beginning to think that the motherboard BIOS is just not fully compatible with the Win 11 OS.
Best of all, there is the Event Viewer that can be your friend- It can show you which apps are delaying shutdown:
• Press Win + X and select Event Viewer
• Navigate to Applications and Services Logs > Microsoft > Windows > Diagnostics-Performance > Operational
• Look for Event ID 203 (shutdown delays) to see which applications are causing problems
• Once identified, update, reinstall, or uninstall the problematic software

I did have a quick look at the Event Viewer and there seemed to be hundreds of entries, most of which I didn't really understand. I will have another look at some time but I think I need to take a step back for a little reassessment.

Thanks for all the help and assistance. It's much appreciated.
 
Woo Hoo! It's fixed!

I noticed that when restarting there was a long pause, when the system rebooted, where the AMI AHCI BIOS seemed to loading or or was not responding to the Win 11 OS. It then went through the POST memory checks before reporting the boot disk failure.

I have turned AHCI off in the BIOS so now the disks are now run by the standard IDE controller. Now restart works and boot from cold works. All good, if not quite as optimised as it should be.

Thanks again for all the contributions to this.
 
Last edited:
After 30 years of relative smooth working with Windows, I finally hit my first real crash (Windows 10). Usually a restore point saves the day even when it fails, it politely rolls back. Not this time: blue screens everywhere, and nine “helpful” recovery options, all useless.
Sure, I could’ve gone the USB repair route… but honestly? It felt like the perfect (and slightly terrifying) moment to finally jump to Windows 11

A few months ago, I’d actually bought a new 2 TB SSD, made a perfect copy of my old 1 TB HDD, and upgraded that old drive from Windows 10 to 11 — just in case. Still, I’d been reluctant to migrate for real. The thought of losing my DAW workflows the delicate ecosystem where Ableton, Traktor, and a zoo of plugins somehow cooperate sounded like a week of reinstalling, re-authorizing, and regretting. One wrong desicion not backuped data and around 15 20 years of sets, re-edits, remasters an automation like, reverb, panning etc etc, and sanity could vanish. :facepalm:

When Windows 10 finally gave up, I flipped the drives made a Win 11 image on the SSD , booted 11, and… everything just worked. To make things smoother, I even used ChatGPT to help me with the restore and migration steps and to my surprise, it was spot-on: efficient, accurate, and apparently aware of every twist in Windows, Ableton an Native instruments logic. All workflows, projects, and automation survived perfectly intact. 100% stable. Honestly, for a version leap and an AI assist done in a few hours that’s pretty impressive.

After all that hesitation, Windows 11 turned out to be the least dramatic part of the story.:cool:

.
 
Last edited:
After 30 years of relative smooth working with Windows, I finally hit my first real crash (Windows 10)....
After all that hesitation, Windows 11 turned out to be the least dramatic part of the story.:cool:
I was waiting for the TL&DR punchline to be "I dumped WinOS"!:rolleyes:

If you do WinKey+R and then type winver << what do you get as an answer?
 
I was waiting for the TL&DR punchline to be "I dumped WinOS"!:rolleyes:

If you do WinKey+R and then type winver << what do you get as an answer?
You mean in my new ssd win 11 laptop: 24H2 ID26100.7019 Windows 11 Pro under system i see the ID codes license. It's migrated from a legal Win 10 Pro. However by passing all Windows headache using Rufus. :facepalm:
 
Last edited:
You be the judge if this is OT:
You (me/we) want to be nice and secure and keep all y/our data in Win10/11 private.
You (me/we) made sure to have a TPMv2 chip inside y/our pc/laptop; since we desire to use Bit-locker encryption of y/our data drives.
ChinkTPMOhDear.jpg

^This is what the Asus 14-1pin TPM-M R2.0 board looks like.
Remembering that the 'TPM' stands for "Trusted Platform Module"; why would you think otherwise?:oops:
Win+R
tpm.msc
ChinkTPMohDear2.png
o_O
You may want to watch the following youtube video:
Your Windows 11 Computer’s Hidden Spy: The Dark Truth About TPM Chips
:mad:
 
You be the judge if this is OT:
You (me/we) want to be nice and secure and keep all y/our data in Win10/11 private.
You (me/we) made sure to have a TPMv2 chip inside y/our pc/laptop; since we desire to use Bit-locker encryption of y/our data drives.
View attachment 487440
^This is what the Asus 14-1pin TPM-M R2.0 board looks like.
Remembering that the 'TPM' stands for "Trusted Platform Module"; why would you think otherwise?:oops:

View attachment 487442o_O
You may want to watch the following youtube video:
Your Windows 11 Computer’s Hidden Spy: The Dark Truth About TPM Chips
:mad:
Thats scary as already mentiond above my Lenovo X230 is upgraded last week from 10 to 11 with critical data (postponed it as long as possible) done with Rufus by passing all sorts of Microsoft requirement like TPM 2.0 check. In the X230 TPM 1.2 is installed. To be sure i also choose in the Bios-security Chip from the 3 options enable disable the Inactive choic so it is dormit (for now) but keeps the existing keys atleast if eventually recuierd. Did some diging was not really neccecary but also could not hurt (like Microsoft backdoors) i may Hope. :facepalm:
 
Last edited:
Back
Top Bottom