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
In System Category the menu Manual Setup (InPlace Upgrade) will remove the files which are required for installing Windows from with-in Windows so that you can only install the OS by booting from DVD/USB drive. That's why the contents of DVD folders may be missing the files you are looking for. Edit: You can get the list of ToolHitHelper components list by using the command ToolKitHelper.exe <Mount-Path> /? command.
Thanks, I'll wait for your reply. Can I do other tests to understand why it doesn't work for me? if i run this command it works for me. Code: reg load HKLM\TK_NTUSER C:\Temp\WIN10\Mount\Install\Users\Default\ntuser.dat reg import C:\Temp\WIN10\Custom\Registry\w10\x64\test.reg reg unload HKLM\TK_NTUSER through toolkit it still doesn't work, I still don't understand where I'm wrong.
And for one last question , I'm thinking of running this build and not updating anything until I decide it's time to move to next big update. I'm only using the computer for gaming exclusively, I'm well versed with computers and know how to avoid to get the system infected or trashed with malware etc. Do you think it's safe to operate this build for this purpose and not updating the system in a while ? I think it's totally fine, just wanted to know what other people think....
For gaming it's OK unless you don't have any issues with the games running and for other purposes It all depends on the unidentified Windows bugs that may crop up later and gets patched by a new CU.
I used 9.9 version yesterday on a W10-64bit Home ISO. After having removed all that can be removed, and installed with the ISO, W.update did not functioning. I searched for a solution on the net according to the error codes and applied all. No change. Anyone else experiencing this?
Hi, thanks for support this excelent software! I wan to add VCredist to win7 ISO but i cant because this: "Microsoft Visual C++ Runtime Pack file "VCRedist_w7.tpk" not found..." only i have VCRedist_w10.tpk, in the MEGA storage pack dont have VCRedist_w7.tpk, where can i found it?
The Toolkit allows integration of features pack to only the default language set in the image. The Component removal process supports multi-language images.
The GUI is not branded as Toolkit instead comes with a new name and it's always better to have a new thread for a new product to avoid confusion. Once the GUI becomes functional with all features, then the current Toolkit development will be stopped in future.