@MSMG, is there any way to bring the official Windows pinball games for us to integrate? One version I remember was the final x86-32 version that continued until Windows XP SP3. I know others came out, but I don't know which ones. If it came out on Vista, I was the one who avoided using it until the release of 7, when I started to migrate from XP.
Hi, How to create only the required iso image from the original MS bundled iso. Ex Windows 10 Pro only or Windows 10 ENT only from the en_windows_10_business_editions_version_2004_updated_june_2020_x64_dvd_cc9defea.iso. Thanks.
Delete unnecessary editions or export only one necessary edition through menu (8) Tools - (1) WIM manager - C or D
Everything will be same as like before, the only change is in the RemovePkgsList.txt content. Before Code: ToolKitHelper:AdobeFlashForWindows ToolKitHelper:InternetExplorer ToolKitHelper:FirstLogonAnimation ToolKitHelper:GameExplorer ToolKitHelper:SnippingTool ToolKitHelper:SpeechRecognition ToolKitHelper:WindowsMediaPlayer ToolKitHelper:WindowsPhotoViewer ToolKitHelper:WinSAT Now Code: AdobeFlashForWindows InternetExplorer FirstLogonAnimation GameExplorer SnippingTool SpeechRecognition WindowsMediaPlayer WindowsPhotoViewer WinSAT There will two new menus in the Remove Windows Components using Package List like [1] Remove Windows Components using Package List (DISM Method) [2] Remove Windows Components using Package List (ToolKitHelper Method) Choosing one will parse each line in the RemovePkgsList.txt and remove each component using the traditional DISM /Remove-Package Choosing two will pass the RemovePkgsList.txt filename as an argument to the ToolKitHelper program which will remove all the components present in the RemovePkgsList.txt at once and there will be no delay like before since the ToolKitHelper program will be called only once. Apart from this, those who use only ToolKitHelper program in their script can use these three methods to call the ToolKitHelper program. - ToolKitHelper <Image-Mount-Folder> <Component-Name> - ToolKitHelper <Image-Mount-Folder> <Component-Name1;Component-Name2;Component-Name3> - ToolKitHelper <Image-Mount-Folder> <RemovePkgsList.txt>
Yes, initially it was added to the Toolkit's games pack but due to folder permission errors it was removed later. I do have the old pack, will correct the pack and re-add them in future.
hey there @MSMG, will there be a new version? does msmg toolkit use install_wim_tweak? if not would be of use if it did? thank!
Yesterday there was a long power outage and so couldn't upload the new version, Yes today will be releasing the new version. Before at start the Toolkit was using the install_wim_tweak.exe but later the same functionality was added inbuilt in Toolkit and now for DISM method it is used.
@MSMG cool no worries! would it be possible for msmg toolkit to allow package names like Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amd64~~10.0.19041.329 when using the dism option? it would make things easia? Majid
@MSMG what I was thinking was use wimtweak to get package list, after makeing all packages vissable, then removeing packages via dism using the package list that is used for dism using the package names vobatem from the wimtweak list? I hope this makes sence, thanks for such a greate tool sir msmg
Yes you can add the full package name in the list, I just add advised to shorten the names so that the list could be used for other Windows versions too. You could use the below command to get the list of packages present in the mounted image, do change the en-US to your language. Code: dir/b Mount\Install\Windows\servicing\Packages\*.mum | findstr /v "en-US" This will copy the list to the clipboard Code: dir/b Mount\Install\Windows\servicing\Packages\*.mum | findstr /v "en-US" | clip then remove .mum text in the copied text using notepad. or use the install_wim_tweak.exe to get the list using the switch /l and to remove using the switch /r