If the reg import gives no error, then the settings are successfully imported. Will check why it's not working for you.
You can get the List by the below commands For ToolKitHelper component names Code: ToolKitHelper.exe Mount\Install /? For DISM package names Code: Dism.exe /Image:Mount\Install /Get-Packages | findstr "Package " | findstr /v "en-US" | findstr /v "en-us" or Check the RemovePkgsList_W10_Template.txt and RemoveAppsList_W10_10.0.18362_Template.txt
Wanted to share about this earlier but was busy with the adding component removal support for W10 v2004. As discussed earlier in my previous posts regarding the GUI development I have resumed the development of Toolkit GUI with a brand new name and was continuously working for two weeks and in-between people wanted the support for W10 v2004 component removal to be added to the current Toolkit and so had to take a break. Still few components need to be added for W10 v2004 component removal, once it's finished will be resuming the GUI development. As said earlier in order to speed up the process of development I have made use of few existing Win32 wrappers available for ManagedDism, ManagedWimgApi, SevenZipExtractor, ManagedWimLib and also made use of NSudo Devil Mode since writing the wrappers from scratch for these components takes more time. The GUI uses Custom UI controls which are owner drawn and so many controls requires more refinement to be done. Currently Source Image->Select/Load/Unload Tab, Add Drivers Tab, Add Updates Tab, Image->Apply/Discard/Export/Rebuild Tabs are working. Still Features, Settings, Tweaks, Packs, Removal and Customization, Image->Apply Status/Progress/Logging features aren't finished yet. Since I don't have the privileges to open a new thread under MDL Projects and Applications category, so will be opening a new thread under Application Software category. Planning to release a test build once the Image->Apply Status/Progress/Logging feature is complete. Do keep a watch on Application Software category, soon a new thread will be opened.
Hello MSMG , what does the command "resetbase" in Tweaks menu do ? I mean I know what the command does , but does it apply the resetbase thing when using the cleanup source image command or ? Would be great to know how to use this tweak[/QUOTE]
Hi MSMG , what does the command "resetbase" in Tweaks menu do ? I mean I know what the command does , but does it apply the resetbase thing when using the cleanup source image command or ? Would be great to know how to use this twea
Microsoft by default disables the option to do full reset base using the DISM /Cleanup-Image /StartComponentCleanup /ResetBase command, this tweak enables the option to perform full reset base when the above DISM command is run. When this tweak is enabled in the Toolkit and the [6]->[1] Cleanup-Image menu is chosen then it performs image cleanup with full reset base.
Thanks , just what I thought , thanks for clarifying this. Also regarding the components that returns after new CU update in the future , do you know if it's only the system apps that get's returned or is it more than that ?
These components categories do return when updates are added later Internet Multimedia Privacy Remoting System SystemApps Windows Apps are not affected since these Apps are updated through Microsoft Store but few Apps like Store and Xbox have back-end files that are updated through the Cumulative Update.
Whatever MS is doing is also pretty inconsistent. I upgraded 3 PCs from 1909 to 2004, all of them with substantial changes through your toolkit. 1 of the systems had virtually everything I had removed return while the other 2 were more or less exactly the same as they were before the upgrade.
@MSMG ,Like the app & compnents,the Windows Edition name in different language.these codes of below from WIMUpgrade: Code: if "%SelectedSourceOS%" equ "w10" if "%ImageBuild%" equ "17763" if "%ImageInstallationType%" equ "Server" if "%SourceEdition%" equ "ServerStandard" if "%TargetEdition%" equ "ServerDatacenter" ( set "Flag=ServerDataCenter" set "Edition=ServerDatacenter" set "Name=%editiona%" set "Description=%editionb%" set "DisplayName=%edtionc%" set "DisplayDescription=%editiond%" ) in language file: Code: set editiona=Windows Server 2019 SERVERDATACENTER set editionb=Windows Server 2019 SERVERDATACENTER set edtionc=Windows Server 2019 Datacenter ^(Desktop Experience^) set editiond=This option installs the full Windows graphical environment, consuming extra drive space. It can be useful if you want to use the Windows desktop or have an app that requires it. As the same as other advise,these codes aren't latest codes,only example. Because make localization simply is the one of the most works for Toolkit.
Thanks for the information! I've just removed all the desired packages through the command remove from packagelist and in the end of the removal processes this was appearing : ------------------------------------------------------------------------------- Removing DISM Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.19613.1000 Image Version: 10.0.18363.815 Processing 1 of 1 - Removing package Microsoft-Windows-CoreSystem-DISM-Package~31bf3856ad364e35~amd64~~10.0.18362.719 [==========================100.0%==========================] The operation completed successfully. This entry isn't in the packages list , so I'm curious what this is. From the file description my guess is that it's something that's not in use anymore ? Is this removal of something that's superseded by the build version of the image ? Hence the buuild number "10.0.18362.719" is older than my "Image Version: 10.0.18363.815". Want to know how this command got executed and what it is because it's not in the list... This is in the end of that list : DISM Component Removal Template =============================== Microsoft-Windows-ContentDeliveryManager-Package Microsoft-Windows-Management-SecureAssessment-Package Microsoft-Windows-Store-Client-Package I'll continue after this and finalize this image anyway, because i'm now inpatient of getting this installation up and running TODAY =) Thanks again for replies and help
Can you advise me which edition of MSGM to use for the windows 10 LTSB 2016 14393.3659 ? Thanks in advance
The template list is a just an example for how to fill the package list, it doesn't contain all the dism package names present in the image. Don't use both the methods to remove the package just stick with ToolKitHelper components or with the DISM packages. Microsoft-Windows-CoreSystem-DISM-Package might be the DISM component used to service the wim images.
Ok. Yes I've used both options 2 and 3 and not removed 1 by 1. But one of those templates had duplicate entries from the other so it shouldn't do any harm I guess it just took more time. Yes the DISM package removal , where does the command come from, it's not in the packagelist. And the build version was older than the current on the image after integrating the updates... So, all the other steps after that went fine I think shouldn't it be good to go anyway ? I dont understand how you can say "might be the DISM component etc" , it's your program and I was hoping you knew what that command came from since it doesn't seem to show in the list..
I just used the options to remove components from the both lists, not removing 1by1. So I shouldn't use both lists`?
Before v8.8, The Toolkit used the DISM /Remove-Package method to remove components and since the Microsoft started merging more packages as main packages, it became difficult to remove the components using the DISM /Remove-Package method. Starting from later versions the Toolkit implemented the manual method to remove the component using a specially built tool called ToolKitHelper and it's usage was restricted to only 1809, 1903/9 and now v2004 builds The ToolKitHelper can also be used standalone from the command line, the ToolKitHelper provides a list of components that can be removed and this list of components names are added to RemovePkgsList.txt, so that the Toolkit can use the list to call the ToolKitHelper program with the component name as it's parameter. Later people started asking to add support for removing the components using the DISM /Remove-Package method too for removing packages with older Windows builds. The ToolKit implemented a method to incorporate both the methods to use the same RemovePkgsList.txt file to remove components by prefixing ToolKitHelper: word to each component name so that the ToolKit will call the ToolKitHelper program if this prefixed word is found in the list and use the DISM /Remove-Package method if that prefixed word is not found. And Hence the RemovePkgsList_W10_Template contains list of components for both the methods, since the DISM package list is huge and varies from one build to another and from one OS to another, so I have just added three package names at the last for user understanding, the user need to get the DISM package using the DISM /Get-Packages command and add the required names to the RemovePkgsList.txt for removal. RemoveAppsList.txt with Microsoft.WindowsCalculator entry removes the Calculator App using the DISM /Remove-ProvisionedAppxPackage command RemovePkgsList.txt with ToolKitHelper:Calculator removes the Calculator App using the ToolKitHelper.exe command RemovePkgsList.txt with ToolKitHelper:WindowsDefender entry removes the Windows Defender using the ToolKitHelper.exe command RemovePkgsList.txt with Microsoft-Windows-DesktopFileExplorer-Package entry removes the Modern File Explorer using the DISM /Remove-Package command Always update the image with the specified the CU version before removing the components to make sure the components are removed properly for each Windows 10 builds.
Yes, thanks I've thought about this and it was about how I thought it was. But I didn't know I could use the Toolkithelper to retrieve the packages, so now I'm trying to remove the packages 1 by 1 and it seems to be working although I think I did some mistake in the process as the sources folder in DVD folder went almost empty, it's the second time I encountered this. I copied the entire iso contents in to the folder before starting the toolkit and when I was on the step to integrate the dotfx3.5 feature it said that the packages were missing.... Went to the sources folder and alot of files were missing again. So either I did mistake or something is not right... Thanks for the help bro