@Enthousiast can you enlighten me, if I can use your approach for Windows Server SKUs (of course changing UpgradeMatrix) What am I interested in is: 1) Upgrade ServerDatacenterCore to Server ServerDatacenter (same applies to Standard and Turbine) 2) Upgrade ServerDatacenterCore to ServerDatacenterACorCore (next year when we have new ACor) 3) Upgrade AzureStackHCI to ServerDatacenterCore/ServerTurbinCore And I am looking into UpgradeMatrix.xml on my installed ServerDatacenter 2025 and have a quesion: What is difference between Code: <TargetEdition ID="ServerDatacenterCore" processorArchitecture="amd64" version="10.0.26100.1"> and Code: <TargetEdition ID="ServerDatacenterCor" processorArchitecture="amd64" version="10.0.26100.1"> Both are in original XML Here is the list of editions, I see in Server's UpgardeMatrix. Spoiler Code: ServerTurbine ServerTurbineCor ServerTurbineCore ServerDatacenter ServerDatacenterCor ServerDatacenterCore ServerStandard ServerStandardCor ServerStandardCore ServerDatacenterEval ServerDatacenterEvalCor ServerStandardEval ServerStandardEvalCor ServerAzureStackHCICor ServerAzureCor ServerStandardACorCore ServerDatacenterACorCore
@kibkalo server has not really my interest, but will check this as soon as i have time, trying to keep the generic upgradematrix.xml really generic
We should warn users that editing EditionMatrix.xml can cause CBS store corruption and future dism operations / updates may fail. Sample dism operation DISM /Image:x:\x /Cleanup-Image /RestoreHealth. Same can also be for other files in that folder. There is hashcheck on xml files. Code: 2024-09-25 13:26:10, Info CBS FLOW: Entering stage: CheckCsi 2024-09-25 13:32:49, Info CSI 00000009 Hashes for file member [l:17]'EditionMatrix.xml' do not match. Expected: {l:32 ml:33 b:a02a4096c4e30afb6035af883ac49dc136795089bafa74d93a7219994ea68ca9}. Actual: {l:32 b:731a0b479797b3776d7de2dd9dd8cdc0a193818211df91356373986f4b15261b}. 2024-09-25 13:32:49, Info CSI 0000000a Warning: Unable to repair payload file ([l:17]'EditionMatrix.xml') for component ([l:98 ml:140]'amd64_microsoft-windows-e..verazurestackhcicor_31bf3856ad364e35_10.0.26100.1_none_c46b07d9b87ac085') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
Maybe a batch file can be done. First backup original xml file, change xml that can accept any upgrade options, let upgrade and change xml with original one again.
Is it possible to upgrade from Windows 10 Enterprise 22H2 to Windows 11 IoT Enterprise LTSC while keeping all files & apps? Tried to use this tool to modify UpgradeMatrix.xml but keep all files & apps option still greyed out when running the setup.
You have to edit the registry for that change Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion Edition id Enterprise to EnterpriseS and restart setup from windows
I am trying to upgrade Windows 7 Ultimate to 26100 IoT Enterprise LTSC. The above file doesn't allow me to keep apps and settings. I have used the tool from this post. And there is a "TargetEdition" IoTEnterpriseS with SourceEdition as "*", - tool works to upgrade Pro, but doesn't with Ultimate As that is a test scenario only, I would like to generally understand the behavior of UpgradeMatrix.xml inside install.wim of 26100.1 - why the Ultimate edition doesn't work as "*" of SourceEdition? Do I need to create unique "SourceEdition" strings with "Ultimate" for each Target, I want to be able to upgrade to? Or I need one "TargetEdition" as "Ultimate", so "*" would include "Ultimate" for all Sources?
Sure, I understand that. I asked a question in "UpgradeMatrix.xml Fix Tool" cause am faced with a logical problem, which I can't understand, hope an author can. Why Ultimate upgrade to 26100 doesn't work under "*" for sourceedition? But it does work if I explicitly add Code: <SourceEdition ID="Ultimate" processorArchitecture="amd64" versionRange="win7" dataOnly="true" dataSetting="false" fullUpgrade="true" cleanInstall="true"/> <SourceEdition ID="UltimateN" processorArchitecture="amd64" versionRange="win7" dataOnly="true" dataSetting="false" fullUpgrade="false" cleanInstall="true"/>
@Enthousiast After making this modded ISO can you still make a Rufus installer flash drive with it ? Also, does the script work on a 3rd party AIO ISO that has many version choices in the install list?
I never use rufus for creating a bootable USB, and the amount of indexes should not matter but when the ISO is abused to much i can't stand for it to work.
@Enthousiast I tried this script on an 3rd party AIO ISO and it said it can keep nothing. I'm not knocking the script, but just trying to figure out what went wrong.