Known Issues: ============= - Using ToolKit with Antivirus Programs enabled can affect the ToolKit's operations. - ToolKit's ToolKitHelper.exe may be flagged as a Virus/Trojan/Malware Program, Don't worry it's just a False Positive Sign. - The ToolKit won't support Post-Servicing of ToolKit serviced source images with other similar tools. - Windows 8.1 - Default Metro Apps Pack missing Office OneNote Appx file. - Windows 8.1 - Integrating Windows Remote Server Administration Tool (RSAT) along with other features will break the Integration with an error code 0x80092004. - Windows 7/8.1/10 v1507/v1511/v1607/v1703/v1709/v1803 Component removal has been removed temporarily. - Windows 10 v1809 - Integrating or Installing Windows Updates after the component removal can restore removed components empty resources files/folders. - Windows 10 v1903 - Integrating or Installing Windows Updates after the component removal will restore the removed components and this is due to the recent change in Microsoft Updates mechanism. - Windows 10 v1703/v1709/v1803/v1809/v1903 - Custom User Account Picture Integration is not working in Logon Screen although it's been displayed in Start Menu User Icon. - Windows 10 v1809/v1903 - Windows Media Player/PhotoViewer/Win32Calc Skins features are not working. - Windows 10 v1709/v1803/v1809/v1903 - It has been reported that in the Format USB Function, the Diskpart command "list" is not working when used within the Script.
Using Image cleanup for W10 v1903 is having issues with recent updates, you need to wait till MS fixes it. Will add a feature to enable/disable features using a list.
I've just made an image with the newest Toolkit 9.4. My findings: Source: LTSC x86. Order: As in the readme, Integrate features, remove components, integrate updates. Spoiler: Packages removed: ToolKitHelper:FirstLogonAnimation ToolKitHelper:GameExplorer ToolKitHelper:SnippingTool ToolKitHelper:CEIP_SQM ToolKitHelper:WindowsInsiderHub ToolKitHelper:EaseOfAccessThemes ToolKitHelper:SecurityCenter ToolKitHelper:AADBrokerPlugin ToolKitHelper:ContentDeliveryManager ToolKitHelper:Cortana ToolKitHelper:NarratorQuickStart ToolKitHelperarentalControls ToolKitHelpereopleExperienceHost ToolKitHelper:QuickAssist ToolKitHelper:RetailDemoContent ToolKitHelper:SmartScreen ToolKitHelper:WindowsDefender ToolKitHelper:WindowsReaderPDF ToolKitHelper:XboxGameCallableUI ToolKitHelper:AdvertisingXaml Result: Flawless. Image came out 100MB bigger (2280MB) than my previous image made in march. I attribute this to the integration of .net 3.5 and the CU that has grown in size. Findings: - The packages template has a lot of packages that are not valid for ltsc. Mainly bottom half. - The .net updates are now all integrated, three of them and in the correct order (net 4.8, lang pack and net cu). - Modern app integration now accept the multi arch desktopappinstaller. - It would be easier to have an empty folder structure in the Toolkit to be able to know where the downloaded packs go. It has changed since last version. The only question I have is about the Microsoft.NET.Native.Runtimes and the Microsoft.VCLibs, can we just pull the latest versions from the adguard site or do some modern apps need specific versions of the runtimes? The integration with the Toolkit was OK, but I still need to test it on a live system. Cheers.
- Yes package template may have some packages names not present in not just LTSC but also other editions, so didn't thought to create template for each edition. - Yes the .Net 4.8 Pack should be integrated using the Integrate Windows Features->Integrate .NET Framework 4.8 Menu and then use the WHD updates pack to integrate the rest of updates. - Yes have add the support to use the latest DesktopAppInstaller, but haven't tested it on live systems, hope it's working. - You just need download the required folder and drop them in the pack folders, will think about the place holder. - I just stuck with the default run-times available with each Windows 10 OS and used the same in Toolkit, may be the latest apps available may require the latest run-times to work on older Windows 10 OS, if it is required then I would update the ToolKit Apps pack to use the same run-time files for each Windows 10 OS.
Ok but the .net 4.8 folder on Mega does not have the files for 1809. Only files there are for 1607 and 1803. Furthermore, Microsoft states that for version 1809 the .net 4.8 will be offered as an update. This is consistent with WHDownloader, it effectively lists .net 4.8 as an update. It may be possible to extract the cab file from the msu (the same for the language pack) and then copy those two files to the packs folder in the toolkit. Where should I put the .msu that contains .net 4.8? Cheers. Edit: Oh well. I must be getting too old for this. Extracted the .cab file from the .msu file and compared the hash of this cab file with the hash from the file on Mega. As it turned out, it is exactly the same file. So never mind the build number, it is OK for at least 1809.
maybe easier to list packages in excel and then other columns list yes/no if the packages is in that edition. Then can use excel filter to sort packages for a version and copy the list
The .NET Framework 4.8 (KB4486129) cab file is same for v1607, v1703 Microsoft-Windows-NetFX48-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab The .NET Framework 4.8 (KB4486153) cab file is same for v1709, v1803 and v1809 Microsoft-Windows-NetFX48-Package~31bf3856ad364e35~amd64~~10.0.16299.15.cab Most of the packs of ToolKit even the language packs, should be considered as updates since they do all use the /add-package to integrate, I have just separated them as feature packs with additional language pack files for which the WHD Tool provides the links but don't download them. DOS Batch programming is limited and may require more work to processing the list. Removing the package using the DISM is no longer recommended since it breaks many functions and WU particularly with W10.
no more like people can copy the filtered list in RemovePkgsList.txt/RemoveAppsList.txt same as they do now, but it makes it easier for you to manage the lists of templates and update it. re: edge ok
@MSMG - Thanks a lot for this wonderful tool sir. I have a question. The end of RemovePkgsList_W10_Template.txt contains the following lines. I just dont understand this, as it says DISM component removal template. DISM Component Removal Template =============================== Microsoft-Windows-ContentDeliveryManager-Package Microsoft-Windows-DesktopFileExplorer-Package Microsoft-Windows-Management-SecureAssessment-Package Microsoft-Windows-Store-Client-Package In order to remove the above, is it sufficient to add these lines along with other entries to the RemovePkgsList.txt ? For ex. ToolKitHelper:YourPhone ToolKitHelper:ZuneMusic ToolKitHelper:ZuneVideo Microsoft-Windows-ContentDeliveryManager-Package Microsoft-Windows-DesktopFileExplorer-Package Microsoft-Windows-Management-SecureAssessment-Package Microsoft-Windows-Store-Client-Package Thanks a lot
Thanks and congrats to @MSMG for Toolkit. The store issue is solved by using RemovePkgsList, I have modified the sample list to my liking as below: Code: ToolKitHelper:FirstLogonAnimation ToolKitHelper:GameExplorer ToolKitHelper:SnippingTool ToolKitHelper:SpeechRecognition ToolKitHelper:WinSAT ToolKitHelper:AssignedAccess ToolKitHelper:CEIP_SQM ToolKitHelper:FaceRecognition ToolKitHelper:KernelDebugging ToolKitHelper:LocationService ToolKitHelper:PinEnrollment ToolKitHelper:UnifiedTelemetryClient ToolKitHelper:WiFiNetworkManager ToolKitHelper:WindowsErrorReporting ToolKitHelper:WindowsInsiderHub ToolKitHelper:HomeGroup ToolKitHelper:MultiPointConnector ToolKitHelper:RemoteAssistance ToolKitHelper:DeviceLockdown ToolKitHelper:WindowsToGo ToolKitHelper:AADBrokerPlugin ToolKitHelper:AssignedAccessLockApp ToolKitHelper:BioEnrollment ToolKitHelper:CBSPreview ToolKitHelper:ContentDeliveryManager ToolKitHelper:Cortana ToolKitHelper:ECApp ToolKitHelper:FileExplorer ToolKitHelper:LockApp ToolKitHelper:MapControl ToolKitHelper:NarratorQuickStart ToolKitHelper:OneDrive ToolKitHelper:ParentalControls ToolKitHelper:PeopleExperienceHost ToolKitHelper:PPIProjection ToolKitHelper:QuickAssist ToolKitHelper:RetailDemoContent ToolKitHelper:SecureAssessmentBrowser ToolKitHelper:SecurityCenter ToolKitHelper:SkypeORTC ToolKitHelper:SmartScreen ToolKitHelper:Win32WebViewHost ToolKitHelper:WindowsDefender ToolKitHelper:WindowsMixedReality ToolKitHelper:WindowsReaderPDF ToolKitHelper:XboxGameCallableUI ToolKitHelper:3DViewer ToolKitHelper:Alarms ToolKitHelper:BingWeather ToolKitHelper:Camera ToolKitHelper:CommunicationsApps ToolKitHelper:DesktopAppInstaller ToolKitHelper:FeedbackHub ToolKitHelper:GetHelp ToolKitHelper:Getstarted ToolKitHelper:Maps ToolKitHelper:Messaging ToolKitHelper:MixedRealityPortal ToolKitHelper:OfficeHub ToolKitHelper:OfficeOneNote ToolKitHelper:OneConnect ToolKitHelper:Paint3D ToolKitHelper:People ToolKitHelper:Print3D ToolKitHelper:ScreenSketch ToolKitHelper:SkypeApp ToolKitHelper:SoundRecorder ToolKitHelper:StickyNotes ToolKitHelper:WalletService ToolKitHelper:XboxApp ToolKitHelper:YourPhone ToolKitHelper:ZuneMusic ToolKitHelper:ZuneVideo
I can't find on NTLite the Take a Test, Films & TV, Microsoft Pay and My Office apps. Maybe they have different names since apparently MSMG ToolKit's Groove Music apps is related to two Zune NTLite apps since after removing the first the latter didn't appear on NTLite. MSMG ToolKit can't for now prevent removed components from returning after installing updates (as well as removing them afterwards) but what if after using it I use NTLite to remove other components (or maybe it's not even necessary), install Windows 10 and after the components return I use NTLite's Remove Reinstall feature? Will it prevent the components MSMG ToolKit removed from returning?