Is the Windows 10 version that you are trying to upgrade 32-bit, by chance? There is no 32-bit Windows 11, only 64-bit.
No. My Win 10 Pro Version is 64 bit.
Is the Windows 10 version that you are trying to upgrade 32-bit, by chance? There is no 32-bit Windows 11, only 64-bit.
No, that is not the reason. There is something else afoot specific to your base system.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.@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?
Always helps to be vigorous in making back-ups/archives of OS drives, as well as data drives.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!
You would please check if the OS has/recognizes multiple bootable disks/partitions; you can check it by "msconfig" - "boot".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".
Understood!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.
Do you mean you have the "boot disk failure" on awake after hibernation/sleep, but none on cold boot after complete "shutdown"?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 find it more peaceful to just ignore thatI have been always hating Windows "hibernation" features.
Some Window11 built-in tools besides the TroubleShooting and Diagnostic appletThe 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.
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:![]()
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 was waiting for the TL&DR punchline to be "I dumped WinOS"!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.![]()
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.I was waiting for the TL&DR punchline to be "I dumped WinOS"!
If you do WinKey+R and then type winver << what do you get as an answer?

Win+R
tpm.msc
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.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?
View attachment 487442
You may want to watch the following youtube video:
Your Windows 11 Computer’s Hidden Spy: The Dark Truth About TPM Chips
![]()
