• 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

As of today, October 4 Japan Time, the latest Windows Update for 25H2 KB5065789 (26200.6725) has automatically come onto all of my nine (9) outdated/non-compatible/unsupported Windows 11 Pro 25H2 upgraded (by "setup.exe /product server") PCs (summary ref. #29), and all automatically smoothly applied.
WS1013.JPG


So far, Windows 11 Pro 25H2 (now build 26200.6725) has no issue nor problem at all, at least in my nine (9) officially unsupported PCs including the really outdated audio(-visual) dedicated two PCs in our living-listening room; very stable, robust, and fast enough; it looks considerably better than 24H2.

As I wrote many times before, for security concerns, in all the unsupported Windows 11 Pro 25H2 PCs, I subscribe "ESET Internet Security" and fully utilize it including the identification and elimination of spam and/or virus-infected/poor-security mails/messages/web-pages/software-applications.

Furthermore, I always reject, i.e. set "OFF", against all of (as far as possible) Microsoft's attempts of collecting private data/information, including the features/functionalities of "Copilot" and "One-drive".
 
Last edited:
As shared in #55, just for possible contingency purposes, I again found/retrieved each of the latest "Product Keys" of Windows 11 Pro 25H2 using a tiny application "Windows Product Key Viewer" (now ver.3.03), and save/keep them in a protected text file as well as printed on a paper to be saved in our key-locked "safe".:D
 
Last edited:
^ or simply type
Code:
wmic path softwareLicensingService get OA3xOriginalProductKey
in an admin cmd or powershell console

Yes, I too know well this method (this command) which would possibly look/search specific registry entry (and/or motherboard's ROM/TPM) keeping/hiding Windows (original?) "Product Key".

In some of my Windows PCs, however, this command does not show the Product Key, but only shows message of "OA3xOriginalProductKey" on admin cmd and powershell consoles; very much strange and mysterious! :facepalm:

The tiny tool "Windows Product Key Viewer" (now ver.3.03), on the other hand, always correctly scans registry (and/or other hidden files of Windows OS) to find and report the exact latest and valid 25-digit Product Key.

Furthermore, I also know that original(?) Product Key is stored in the registry;
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform
where the file data of "BackupProductKeyDefault" is the 25-digit "Product Key".

Again, very much strangely and mysteriously, however, the 25-digit Product Key data in file "BackupProductKeyDefault" is not always the same/identical to the key reported by "Windows Product Key Viewer" (now ver.3.03).:facepalm::facepalm:

I did confirmed that, at least in my Windows PCs, "Windows Product Key Viewer" (now ver.3.03) always reports correct and valid (latest?) Windows Product Key with which I have activated the specific Windows OS, and with which I can re-activate Windows when Windows has been deactivated for any unknown (or known) reason.:D

Edit:
I guess (or even believe) that Microsoft itself too has much confusion (and/or inconsistencies) in their "Product Key" storage-bank, control and management. It would be highly possible Microsoft would be simply happy only if the specific "Product Key" (and/or "Registry Key" keeping "Product Key") which activated the specific Windows on one specific PC has been "paid" at least once in the past...
Nevertheless, and in any way, we do need the specific Product Key for reactivation of the specific Windows...
 
Last edited:
The tiny tool "Windows Product Key Viewer" (now ver.3.03), on the other hand, always correctly scans registry (and/or other hidden files of Windows OS) to find and report the exact latest and valid 25-digit Product Key.
A warning:
I just downloaded this from the link above, and my virus pgm (Webroot) flagged it as infected, so I deleted it.
Be advised....
 
Unfortunately, I have to report a failure. I attempted to upgrade an "unsupported" 64-bit Windows 10 Home installation to 25H2, using instructions here. The download took over an hour, after which "Your PC will restart in few moments" appeared on the screen for over two hours before I gave up and shut the computer down using a "long press" of the power button. Upon reboot, "Undoing changes made to your computer ..." appeared. That "undo" is still in progress as I type this.

EDIT: The restoration of the original Windows 10 appears to have been successful. After boot, the following message appeared: "0xC1900101 - 0x20017 The installation failed the SAFE_OS phase with an error during BOOT operation".
 
Last edited:
I would suggest downloading the ISO first from the download page. Then run latest Flyobee, select/mount the ISO (from menu), then run install (aka setup.exe) from the menu. That way everything is local once the install starts. Essentially getting to the same place as the other instructions.

Should work (worked for me).
Upgraded: 2 Beelinks, 2 Zotacs

PS I left out that I chose the setup.exe option to d/l pending updates post-install vs pre-install (to go directly to the disk-based install vs waiting on a long network download before the install proceeds).
 
Last edited:
EDIT: The restoration of the original Windows 10 appears to have been successful. After boot, the following message appeared: "0xC1900101 - 0x20017 The installation failed the SAFE_OS phase with an error during BOOT operation".

I know this failure may happen in case if you have multiple "bootable" partitions in your SSD and/or HDD.

To avoid this, as I wrote in my post #10, prior to apply the Upgrade process, within Windows 10 you need to make it to "only single bootable partition" by using "msconfig" - "boot" - "select present OS boot partition", and delete other bootable indicators/directors.
 
A warning:
I just downloaded this from the link above, and my virus pgm (Webroot) flagged it as infected, so I deleted it.
Be advised....
It may happen if the download ZIP contains executable .exe file (not MS certified installer file).

I carefully virus-scanned the "winproductkey.exe" with the latest "ESET Internet Security v.18.2.18.0" confirming it is free of virus and/or harmful behaviors (malware); it will ask you donation twice or more, though.
 
Last edited:
Only one bootable partition on this system.
OK, then I am sorry that I cannot give you any further suggestions based on my own experiences. :facepalm:

I would like to suggest you trying the "Flyoobe" method, which I have not yet tried though.
 
In my experience, sometimes it's better to just wipe the computer and install Win11 from scratch. Sure it's more work, but it was the only thing that worked with my Lenovo Thinkpad X270, which refused to just do the "regular" Win10 to Win11 update due to some mysterious driver issue that suddenly disappeared.
 
It may happen if the download ZIP contains executable .exe file (not MS certified installer file).

I carefully virus-scanned the "winproductkey.exe" with the latest "ESET Internet Security v.18.2.18.0" confirming it is free of virus and/or harmful behaviors (malware); it will ask you donation twice or more, though.

This post is my self-follow-up regarding the "winproductkey.exe", i.e. zip of "Windows Product Key Viewer" (now ver.3.03).

After launching "winproductkey.exe", you need to push "Reveal Windows Product Key" button to show your own Product Key of the specific Windows OS. You may of course just close the pop-up donation-request web page.

Then, within ca. 20 seconds, you would please go to "File" - "Save..." to save the various information including the 25-digit Product Key into a text file of your preferable file name for your records.

The contents of thus obtained latest Windows license info text are really useful (and interesting?) including Product Key, Product ID, Build Lab, Machine GUID, ReleaseID, Update Build Version (6725), Display Version (25H2), etc., etc.
 
Last edited:
I mean major BUM!
Microsoft Insisting On Microsoft Account Sign-In
Microsoft has recently announced further steps to prevent users from signing in via a local account:
Local-only commands removal: We are removing known mechanisms for creating a local account in the Windows Setup experience (OOBE). While these mechanisms were often used to bypass Microsoft account setup, they also inadvertently skip critical setup screens, potentially causing users to exit OOBE with a device that is not fully configured for use. Users will need to complete OOBE with internet and a Microsoft account, to ensure device is setup correctly ~ <source>
Back in March this year, Microsoft announced that it was blocking a well-known script used for circumventing the internet connection and Microsoft account sign-in requirements. However, it didn’t prevent users from applying other workarounds, such as performing a registry edit to activate the script, hence this new announcement regarding further steps.
As for Microsoft’s claim that by bypassing the Microsoft account setup, users also skip critical setup options, meaning the device is not properly configured. As far as I can recall, none of those additional setup options offer anything critical or important, so I’ve always skipped right through them anyway.

BOTTOM LINE:

Microsoft’s insistence on forcing users to sign in via a Microsoft account is not only anti-freedom-of-choice, but it also creates concerns for many users who prefer to sign in via a local account for privacy and security reasons...
I have never found enough reasons to dump Windows, since Win3.0... but this bonehead move by Microsoft makes it my "Straw that broke the camel's back" moment!:mad:
 
@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?

As I recall, when I was upgrading my garage PC using this method, that too would not allow me to keep all the files and apps. It was no big issue on that PC because I have so few apps installed on it. But on my main, house PC it would be nice to be able to largely leave all the apps and setting as they are.

Thanks for any help and advice.

M
 
At least I myself I have never encountered such "issue" during "setup.exe /product server" method for upgrading my nine (9) Windows 11 Pro 24H2 PCs to 25H2 Pro.

And, I am sorry that I myself have never tried the method on Windows 10 PC to Windows 11 25H2, even though I have many successful reports within Japan and also abroad.

The only suggestion I can give you now is that you would please try the free "FlyOOBE" tool.
 
At least I myself I have never encountered such "issue" during "setup.exe /product server" method for upgrading my nine (9) Windows 11 Pro 24H2 PCs to 25H2 Pro.

And, I am sorry that I myself have never tried the method on Windows 10 PC to Windows 11 25H2, even though I have many successful reports within Japan and also abroad.

The only suggestion I can give you now is that you would please try the free "FlyOOBE" tool.

OK. Just tried the FlyOOBE tool and that has exactly the same problem. The "keep/preserve all files, settings, applications" is greyed out.

It looks like I'm going to have to go with the 'preserve personal files' option and reinstall any apps that I need. It will take a lot more time but I suppose it will clear a lot of the junk apps that I no longer use off the main PC.

Thanks for the advice.
 
Back
Top Bottom