A function that can generate manifest's file name. In fact, you can use the official version in keyform.dll.
[Fact] Microsoft Activation Server blocks "10586.0" "Starter". (Be aware: Two conditions.) To activate 10586 Starter(N)? Well, it is imposible, because of 1. It is blocked. 2. Its License technology is different to the latest builds. Therefore, I make a package to add any other "EditionID" than "Starter" in other "Build" to cheat Microsoft Activation Server. e.g. Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package~31bf3856ad364e35~amd64~~10.0.10586.0.mum. Code: <?xml version='1.0' encoding='utf-8' standalone='yes'?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved." manifestVersion="1.0"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.10586.0" versionScope="nonSxS"/> <package identifier="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package" releaseType="Feature Pack"> <update name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Deployment"> <component> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="10.0.14393.0" versionScope="nonSxS"/> </component> </update> </package> </assembly> Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package~31bf3856ad364e35~x86~~10.0.10586.0.mum Code: <?xml version='1.0' encoding='utf-8' standalone='yes'?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved." manifestVersion="1.0"> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" version="10.0.10586.0" versionScope="nonSxS"/> <package identifier="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package" releaseType="Feature Pack"> <update name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Deployment"> <component> <assemblyIdentity buildType="release" language="neutral" name="Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" version="10.0.14393.0" versionScope="nonSxS"/> </component> </update> </package> </assembly> ---> "14393.0" "EnterpriseS" (Any non-Starter EditionID will be OK.) Be aware: 1. To make sure that the installation can activate, you have to add it "after updates" if there is CU. 2. Don't run "Resetbase" before it is being activated. Otherwise, after installation, it will fail to activate. Code: if defined PATCHED ( echo. echo ------------------------------------------------------------ echo Install Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package echo ------------------------------------------------------------ dism /english /image:%MT% /add-package:files\sxs\Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package~31bf3856ad364e35~%ARCH%~~%LVER%.mum ) echo. echo :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: echo Save and Unmount %CURRENT% image echo :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: dism /english /unmount-wim /mountdir:%MT% /commit
26100.1_Unstage_amd64_LTSC.7z (10,114,304 KB) + 26100.1_Unstage_amd64_WNC.7z (3,340,945 KB) = 26100.1_Unstage_amd64 (10,206,889 KB)
Thanks for help. I was reading whole thread to find some info about it. Today i was also analyzing how dismhost remove capabilities/packages its quite simple i think. Doing a script for mum files also and connect it to my already almost made manifests script. So u guys trying to change edition to get other featureset right? Most stripped featureset is "core" ? I can make stripped latest windows 11 ltsc that im using to get other featureset? It will save me some removal
NXT is soul of WNC. WMC package is just a wrapper of NXT package. If NXT package is removed, nothing left at all. It won't activate even the official Client is reconstructed with WNC EditionSpecific package. Because WNC Spp which is NXT components has gone. Q: How to modify NXT package for an activated WNC Desktop?
Hm, if i understand it right Sessions.xml file represents what was installed already right? So changing edition doesn't remove any files or registry etc etc. ? It just switch the packages that are used, and the rest things stay like was before? I don't get it really.
Q: Hm, if i understand it right Sessions.xml file represents what was installed already right? A: Yes. You are right. But you have to be aware of following things. 1. Some features are controlled by License Product policy. We can not change anything defined by Product policy. e.g. Group Policy is not allowed on Core and Starter. Windows Defender is not allowed on EnterpriseG. 2. AC features which are controlled by Enablement can not be active on LTSC.
26100.1, initial build, problematic ---> 26100.1 + 26100.1742 Baseline CU ---> Public Release + 26100.XXXX CU . . . 14393.0 Server, initial build, problematic ---> Public Release ---> 14393.XXXX CU . . .
[Extracting whole WMC individual packages in 38 languages from Ramdisk to Hdd] [Windows Defender: On] Code: Mission took 1:30:20.64 (5420.64s total) [Windows Defender: Off] Code: Mission took 1:6:16.72 (3976.72s total)