is it possible to downgrade while keeping apps to older build by performing inplace upgrade from iso? i have insider canary build 27871 pro, i've patched and tried to upgrade from insider dev iso 26200.5670 pro (to get 25h2) but setup states "Your files, apps, and settings can't be kept because your current version of Windows might be installed on an unsupported directory or you're trying to install an older version of Windows"
Just wanted to say that this tool helped me repair an installation of Server 2025 where an in-place upgrade install of the same version of Server 2025 (26100.1) was failing (not certain why, but from the logs in the C:\$WINDOWS.~BT folder, it appeared to be due to there being "no antivirus installed"). Running this tool on the same build of IoTEnterpriseS resulted in a successful in-place upgrade to the client edition, and subsequent success doing the same with the previously failing server edition.
Hey Enthousiast, I have a few question about your script. 1. Your script seems to run fine without administrator privileges. Is that the case, or should I run it as administrator? 2. Is it best to run your script on the ISO before integrating updates to it, or should I integrate updates into it first and then run your script? In my case, I'm working with 26100.1.240331-1435.ge_release_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso, which is Windows 11 IoT Enterprise LTSC 2024. I will be adding the October updates to it next month using using the UUP dump site, specifically for build 24H2 if I'm not mistaken, along with W10UI to do the integration. 3. Should I stick to using Upgrade Enabler Tool 2.1 beta 3 on the first page, or would it be better to use Upgrade Enabler Tool 2.1 beta 4 on the 4th page? Maybe it doesn't matter but I thought I'd ask. P.S. The "README.txt" file in beta 4 says: Put the source ISO inside the "Source_ISO" folder and run "RunME_Test_3.cmd". It should say: Put the source ISO inside the "Source_ISO" folder and run "RunME_Test_4.cmd". A small mistake, but I thought I'd mention it. Thanks for making the script. It seems to have worked for me. I'll test the new ISO next month.
It should ask for admin priveleges when started by simply doubleclicking, I run it as last step in my projects. When you create virtual editions after inserting the modifief xml then it is not working (in my tests). Use the latest, the one at the OP should be the latest (i now noticed i didn't update the OP) Updating the tool to fix the info in the project folder, releasing v2.1beta5 soon.
Thanks for answering my questions. I did notice that your tool runs just fine without administrator enforced. I'll be sure to run it with admin in the future though, just in case. I'm looking forward to beta 5.
I tried this tool, but it looks like it doesn't work. I'm on 26200.5751 and I've tried to get to regular 25H2 builds (like 26200.6718), but not use, still cannot choose "Keep personal files and apps."
But I'm stuck at this point... I tried everything I could think of... And I still cannot figure out a solution.
Greetings from Lima, Peru !!! I was trying to upgrade to 26200.6718 using ISO download from uupdump.netdump and it failed twice... I then tried installing the KB5054156 EP first and then just the uupdump.net update files using W10UI V55 and it worked..... Just my 2 cents... JCC2
What Enthousiast meant when he said "You should not even need this tool for that" is that you should be able upgrade from a previous Home or Pro edition of Windows (e.g. 23H2 to 24H2 to 25H2) without needing this tool at all. The purpose of this tool is to allow users to force an upgrade of a version of Windows to another version of Windows that was never never meant to get upgraded to (e.g. Windows 11 Home 23H2 to Windows 11 IoT Enterprise LTSC 2024), while still keeping all installed programs, files and folders intact. Microsoft typically prevents this from happening since Home and Pro versions are not designed to get upgraded to an Enterprise edition like the IoT LTSC, but this tool essentially changes the registry settings within the ISO of Windows, such as Windows 11 IoT Enterprise LTSC 2024, so that an upgrade becomes possible. If I've left anything out, I'm sure someone here will add to this, or correct anything I may have said incorrectly.
This tool was initially developed for upgrades to 2019 LTSC, there was no direct path for that and the xml modification made the path possible and to keep all during the upgrade. It is usefull for when the normal upgrade setup doesn't allow to keep all files, apps and such.
https://forums.mydigitallife.net/threads/windows-11-hotfix-repository.83741/page-177#post-1890365 I tried to perform an in-place upgrade to any regular build of 25H2, but the "Keep personal files and apps" option was grayed out for every build of 25H2 I tried. I was stuck on 26200.5751, which is a Dev build, not a regular build of 25H2. In the meantime, I was able to patch setupcompat.dll within the following ISO file: Windows11_InsiderPreview_Client_x64_en-us_26200.iso. So, I forced an upgrade to 26200.5074, and right now I'm on build 26200.6718. Patching setupcompat.dll was literally my only solution.
Is an IP level build, those switches have noting to do with the upgradematrix.xml, this tool won't fix the MSFT mess of switching to and from beta/dev/retail.