...I have a doubt the tool also modifies or changes the system registry or only removes components and apps without modifying the registry?
Hi MSMG ; I used LTSB 2016 and server 2016 isos for removing windows components with MSMG 7.0 and 7.1 Version 7.0 and 7.1 have errors when removing components section. For example , i am selecting "remove internet explorer UI" but it goes to " remove components by package list".. and a few errors like this Version 6.9 was very stable but all messed up in next versions , i think and thanks again for this beautiful utility
How can I pre-edit "ProgramData\Microsoft\Windows\AppRepository" directory and its files? Once OS is installed, that directory contains XML files for all AppX's and StateRepository-Machine.srd SQL Database file that controls which AppX's can be uninstalled/deactivated/removed with PowerShell and which ones cannot. I want to make an ISO that StateRepository-Machine.srd file already edited for removal of all AppX's except for Immersive Control Panel, Shell Experience Host, and Edge. AFAIK there is a AppXManifest file used to tell the OS which AppX's exist and which ones do not exist. Maybe more bloat-ware can be removed without having to use NSudo + SQL software to edit StateRepository-Machine.srd list of AppX's that can be removed if that AppXManifest file is edited to show just the AppX's the user/customizer wants. After my last customization there was still plenty of non-system bloatware and I think it is best to remove it or to uninstall it ahead of time.
No, I am not talking about simply removing registry keys because that does not remove the actual package and you will not be able to get rid of those "missing" packages using PowerShell since those AppX's would not be in the registry, although it is possible that StateRepository SQL database does not even bother with registry and reads directly from AppRepository directory AppX Manifest XML files.
"Program Files\WindowsApps" are Provisioned Appx. Uninstall is easy: Dism /Image:mount /Remove-ProvisionedAppxPackage /Packagename:"PackageName" = uninstall and delete file in mount wim. SystemApps ("c:\Windows\SystemApps\" and etc.) no Provisioned Appx, no uninstall with Remove-ProvisionedAppxPackage. SystemApps are Appx (without Provisioned). SystemApps install as clasic packages and uninstall as clasic packages: Dism /Image:mount /Remove-Package /PackageName:"PackageName" only packages with mum. Packages without mum = uninslall only manualy. Summary: No registered inbox SystemApps in wim? => Delete: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\InboxApplications\PackageName ( = no in StateRepository-Machine, no shortcut in Start and etc.). No file inbox SystemApps with mum in wim? => uninstall package Dism /Image:mount /Remove-Package /PackageName:"PackageName" No file inbox SystemApps withouth mum in wim? => manualy deleted file and all needed registry ( = individual). PS: "PackageName" (appx) <> "PackageName" (package) ... for the same package (appx)
Nice one Krakatoa! Thank you! Short, concise, to-the-point and yet very informative all-in-one reply! This will make it so much easier! If System AppX's cannot be removed with PowerShell, then why did it "kind-of work" for me? I mean the FILES are still there in "Windows\SystemApps", but the OS was no longer registering System AppX's that I set to "IsInbox=0" in StateRepository-Machine database file after I ran Get/Remove PowerShell commands as Trusted Installer, then as System, then as Administrator, and then as User-Administrator. I guess its more like "deactivation" ??? Also, there was no way to bring those "deactivated" System AppX's back without re-installing the extracted CAB package with SxSExpander from my previous OS install (from backed up Acronis image). I just visited those registry directories and it looks like my registry cleaner does not bother with cleaning anything AppX-related because all and I mean ALL System AppX's I "deactivated" still have registry entries. What's a good registry cleaner for AppX's? Or is it best to just manually search for package name and remove it that way? Are there some specific registry directories to look at?