Yes I have uploaded them but without the new Toolkit.cmd you can't use it to integrate the games since the image indexes do change in the pack.
For Extracting drivers from system the standard DISM command Code: DISM /Online /Export-Driver /Destination:<Drivers-Folder> For importing drivers into the image the standard DISM command Code: DISM /Image /Add-Driver /Driver:<Drivers-Folder> /Recurse For built-in drivers you may need to manually search and copy the related files and then import them.
Instead of adding the code in every features integration functions, I moved the code to Select source from DVD function so that while mounting the image the PackageVersion, PackageBuild, PackageServicePackBuild, PackageArchitecture is defined only once.
If the script was terminated while integrating any packages, the DISM mounted image registry hives need to be unmounted before trying to unmount the image. DISM mounted image registry hives are different from HKLM\TK_COMPONENTS, HKLM\TK_SOFTWARE, HKLM\TK_SYSTEM. Usually the DISM uses the full file path of the registry hive as the registry hive name, you can check the HKLM registry hive for the list of mounted.
Thanks for trying The Toolkit. 1) The main Toolkit script is open sourced, but it's sub-tools like component remover is closed source. The Toolkit files and it's add-on feature packs are free from malware, keyloggers, spyware or any virus. Due to the code protection added to the component remover program many Antivirus programs may flag the Toolkit's component remover program as virus or trojan, don't worry this is just false positive sign. You can install and monitor the Toolkit created image on Virtual PC like Hyper-V/VMware/VirtualBox for any suspicious activity and then decide whether to deploy the image to your main PC. 2) Make sure you are using the latest version of Toolkit and also delete other indexes present in the image to get real image size. 3) The Toolkit only supports offline images and yes you can integrate the drivers and updates to the image before removing the components. For component removal you may need to integrate the cumulative update specified in the changelog. Note: Starting from Windows 10 v1903 onwards, the Microsoft implemented new update package format due to which the removed components will return when the system is updated either through Windows update or manual update install using .msu or .cab file. Only the Windows Apps component is not affected by this issue.
Yes, I thought so too. It was one of the Custom 11.4 mods. But to help on this occasion it had to be added in the specific section. We are in sync
THANK YOU Hello dear! I have the HKLM registry hives for a list of connected ones like this: Spoiler %~dp0tools\Mount\Windows\System32\config\COMPONENTS %~dp0tools\Mount\Windows\System32\config\DEFAULT %~dp0tools\Mount\Windows\System32\config\DRIVERS %~dp0tools\Mount\Windows\System32\config\SAM %~dp0tools\Mount\Windows\System32\config\SECURITY %~dp0tools\Mount\Windows\System32\config\SOFTWARE %~dp0tools\Mount\Windows\System32\config\SYSTEM %~dp0tools\Mount\Users\Default\NTUSER Help me please. I am very ashamed for begging, but this is the only site where I can really get a lot of help from you. Excuse me, please.
No usually the DISM will mount the required registry while integrating packages by using the registry hive file path as the registry hive mount name. E.g: c://windows//system32//config//components or c:\\windows\\system32\\config\\components or c:\\toolkit\\mount\windows\\system32\config\\components You need to identify the registry hives and unmount them, one method is to manually do it or use a search query for HKLM to detect list of keys using reg query HKLM command and then skip the default entries and then unmount the remaining entries. The default entries to be excluded are HKEY_LOCAL_MACHINE\HARDWARE HKEY_LOCAL_MACHINE\SAM HKEY_LOCAL_MACHINE\SECURITY HKEY_LOCAL_MACHINE\SOFTWARE HKEY_LOCAL_MACHINE\SYSTEM
From the logs you posted, it seems you have the same duplicate permission entries as I previously posted. In that regard, I think @MSMG will update the packs to avoid such warnings in the future. Otherwise your logs are clean, it doesn't seem to be a critical issue. Cheers.
Cleanup (5 > 1) README.txt: Windows 10 v2004/v20H2/v21H1 Client/Server Usage Order: [K] - Cleanup the Source Image using [Apply->Cleanup Source Images] menu. Note: Not recommneded to use due to SFC bug with recent Latest Cumulative Updates (LCU).
Does not apply, uupdump is clean. He has duplicate permission entries because of the pack he integrated. Cheers.
I haven't looked at CBS. log, but I know for sure that if Cleanup (5 > 1) is executed, there will be an SFC error. Feartamixg indicated that Cleanup (5 > 1) was performed.
Again, does not apply when he was using uupdump source. Please look at the CBS log he posted. And see the answer from MSMG quoted above. Cheers.
An example of the components list can be found in the template at the path:ToolKit\Bin\Lists\DISM_Templates\RemovePkgsList_W10.txt You need to put your custom list into an empty text file on the path: ToolKit\Bin\Lists\RemovePkgsList.txt In the image processing step in Toolkit, select: [3] Remove -> [3] Remove Windows Components Using Package List -> [1] Remove Windows Components Using Package List (DISM Method)