I copied the windows 10 2019 LTSC crtificates to my computer running windows server 2019 standard. I did hwid activation with windows 10 2019 LTSC product key. all of the server features still work Cumulative Updates work fine
Removing Windows 10 Win32Calc by 7Customizer Code: Z:\remove>remove.exe Checking dependencies.. Read xml files and gather information.. ..reading xml files.. 100% [================================================================================================================] ..resolving folder wildcards.. ..resolving file wildcards.. ..resolving registry wildcards.. ..resolving package dependencies.. 100% [================================================================================================================] ..done! Write batch file.. ..directories.. ..files.. ..deleteLine entries.. ..done! Write .reg file.. ..done! Removing components.. ..backing up permissions.. ..setting permissions and removing files.. 100% [================================================================================================================] ..removing registry entries.. ..editing files.. 100% [================================================================================================================] ..restoring permissions and removing temporary files.. ..done!
Yes for activation and updates. But Server Manager works no more unless you use ServerRdsh. And Server Roles and most Features won't take effect becuase of EnterpriseS' Product policy.
The method is good, but it is still troublesome to make the corresponding XML, and it is easy to miss items and cause incomplete uninstallation.
It has create.exe for creating xml. But you need to contact the author for updates. e.g. Code: Z:\create_v1.0>create -k win32calc -c win32calc Searching for manifest files with the keywords: win32calc. This might take some time... done! Collecting xml data... Removing redundant elements (this might take even longer)... We're done! Xml file saved to xml\win32calc.xml.
securityhealth-sso.xml Code: <?xml version="1.0" encoding="UTF-8"?> <_7Customizer> <Componenet group="not defined" name="securityhealth-sso" requiredForStableSystem="false" size="1"> <Description>Put a meaningfull but short description here.</Description> <DependsOns/> <NeededFors/> <Files> <File method="delete" path="Windows\System32\*-*\securityhealthsso.dll.mui"/> <File method="delete" path="Windows\System32\SecurityHealthSSO.dll"/> <File method="delete" path="Windows\System32\SecurityHealthSystray.exe"/> <File method="deleteLine" path="Windows\WinSxS\Manifests\*microsoft-windows-c..ent01100-deployment_*.manifest" string="Windows-SecurityHealth-SSO.Resources" xmlParents="dependency"/> <File method="deleteLine" path="Windows\WinSxS\Manifests\*microsoft-windows-c..ent03120-deployment_*.manifest" string="Windows-SecurityHealth-SSO" xmlParents="dependency"/> <File method="deleteLine" path="Windows\winsxs\pending.xml" string="Windows-SecurityHealth-SSO" xmlParents=""/> <File method="deleteLine" path="Windows\winsxs\pending.xml" string="Windows-SecurityHealth-SSO.Resources" xmlParents=""/> </Files> <Directories/> <Registry> <Keys> <Key part="software" path="Classes\CLSID\{6D40A6F9-3D32-4FCB-8A86-BE992E03DC76}"/> <Key part="software" path="Microsoft\Windows\CurrentVersion\Run"/> </Keys> <Values/> </Registry> <Manifests> <Manifest id="*windows-securityhealth-sso.resources_*"/> <Manifest id="*windows-securityhealth-sso_*"/> </Manifests> <Packages/> </Componenet> </_7Customizer> SecHealthUI.xml Code: <?xml version="1.0" encoding="UTF-8"?> <_7Customizer> <Componenet group="not defined" name="SecHealthUI" requiredForStableSystem="false" size="15"> <Description>Put a meaningfull but short description here.</Description> <DependsOns/> <NeededFors/> <Files> <File method="deleteLine" path="Windows\WinSxS\Manifests\*microsoft-windows-c..ent01100-deployment_*.manifest" string="Microsoft-Windows-SecHealthUI.AppxMain.Resources" xmlParents="dependency"/> <File method="deleteLine" path="Windows\WinSxS\Manifests\*microsoft-windows-c..ent03130-deployment_*.manifest" string="Microsoft-Windows-SecHealthUI.AppxMain" xmlParents="dependency"/> <File method="deleteLine" path="Windows\WinSxS\Manifests\*microsoft-windows-c..ent03130-deployment_*.manifest" string="Microsoft-Windows-SecHealthUI.AppxSetup" xmlParents="dependency"/> <File method="deleteLine" path="Windows\winsxs\pending.xml" string="Microsoft-Windows-SecHealthUI.AppxMain" xmlParents=""/> <File method="deleteLine" path="Windows\winsxs\pending.xml" string="Microsoft-Windows-SecHealthUI.AppxMain.Resources" xmlParents=""/> <File method="deleteLine" path="Windows\winsxs\pending.xml" string="Microsoft-Windows-SecHealthUI.AppxSetup" xmlParents=""/> </Files> <Directories> <Directory path="Windows\SystemApps\Microsoft.Windows.SecHealthUI_cw5n1h2txyewy"/> <Directory path="Windows\SystemResources\Microsoft.Windows.SecHealthUI"/> </Directories> <Registry> <Keys> <Key part="software" path="Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\InboxApplications\Microsoft.Windows.SecHealthUI_10.0.17763.1_neutral__cw5n1h2txyewy"/> </Keys> <Values/> </Registry> <Manifests> <Manifest id="*microsoft-windows-s...appxmain.resources_*"/> <Manifest id="*microsoft-windows-sechealthui.appxmain_*"/> <Manifest id="*microsoft-windows-sechealthui.appxsetup_*"/> </Manifests> <Packages/> </Componenet> </_7Customizer> PS. The 17763.1757 LCU brought back part of SecHealthUI. i.e. Code: <Directories> <Directory path="Windows\SystemApps\Microsoft.Windows.SecHealthUI_cw5n1h2txyewy"/> <Directory path="Windows\SystemResources\Microsoft.Windows.SecHealthUI"/> </Directories> OK. Done.
server manager works, server roles work. Windows Deployment Services work. EnterpriseS doesn't change the product policy. If I used product keys semi annual channel editions of windows 10, the product policy will change nothing broke
vNEXT Server, now alike latest Windows 10 (since 18362.1): New Structure + New System Update Technology + New PSFX Format
Q: How to customize existent Windows installation by Reset? A: 1. Modify relevant mum file(s) in C:\Windows\servicing\Packages 2. Reset
Q: Can I re-construct my running system into another edition by the OP's way? A: Yes, but OFFLINE only. i.e. in WinPE, WinRE, or from other system in other partition of the device. Or from Windows-To-Go Portable system.
Ask a question, for example, 17763.1, IE, MediaPlayer are not sub-packages of Windows-XXXEdition, they are separate packages, why reset, they are not affected?
You did not pay careful attention. I said relevant mum(s). Code: Yes, this is what a so-called Windows Edition is composed of. Then keep looking into each and every mum file defined in the Edition mum, and all sub-packages in the relevant mums to find your target package name(s). and all sub-packages in the relevant mums to find your target package name(s). And I'd shown Code: e.g. OneDrive in Microsoft-Windows-Not-Supported-On-LTSB-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum Microsoft-Windows-Not-Supported-On-LTSB-WOW64-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum For OneDrive, you can 1. remove OneDrive from Microsoft-Windows-Not-Supported-On-LTSB-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum 2. remove Microsoft-Windows-Not-Supported-On-LTSB-WOW64-Package~31bf3856ad364e35~amd64~~10.0.17763.1 from XXXEdition.mum.
I mean, if I add Microsoft-Windows-win32calc-Package to the professional version, if it is not processed, it will be removed after resetting.Why IE, MediaPlayer will not be removed after reset.
Hint: from 15063.0 forward Settings + Microsoft-Windows-FodMetadata-Package allows you to add\remove Feature-on-demand packages. IE = individual package (install\uninstall manually only) Mediaplayer's sub-package Microsoft-Windows-MediaPlayer-Payload-Package becomes sub-package of Microsoft-Windows-MediaPlayback-OC-Package after installed. So, more complicated. You can remove it by either ways: 1. Remove Microsoft-Windows-MediaPlayer-Package 2. Remove Microsoft-Windows-MediaPlayer-Payload-Package 3. Remove Microsoft-Windows-MediaPlayback-OC-Package (Feature item will be gone from Features menu) 4. Media Feature package Don't remove Microsoft-Windows-FodMetadata-Package, otherwise related FOD install\uninstall functions will not work from Settings.
Those 21H1 packages do not exist in 19041.1. Microsoft adds them to editionpack for 20H2 and 21H1 through LCUs. Without Enablement patch activating it, the new Features won't take effect at all. e.g. microsoft-windows-editionpack-core-package~31bf3856ad364e35~amd64~~10.0.19041.804.mum