Ok I did my first test with 17763.1 x64 en us using the new toolkithelper, no update integrations but removed all components. Everything went smoothly, windows update did its thing, sfc showed no errors and I roamed around the operating system seeing if anything is wrong and found nothing..I'll do the same test right now but this time integrate updates after component removal.
Would this be the correct usage? I did not update the list nor tested but just wondering if it is. This is from LTSC 2019 I think. RemoveAppsList Code: Microsoft.AdobeFlashForWindows Microsoft.AssignedAccess Microsoft.CEIP_SQM Microsoft.Cortana Microsoft.DeviceLockdown Microsoft.EasyofAccessThemes Microsoft.EdgeDevToolsClient Microsoft.FirstLogonAnimation Microsoft.HomeGroup Microsoft.KernalDebugging Microsoft.MultiPointConnector Microsoft.RemoteAssistance Microsoft.SmartScreen Microsoft.SystemRestore Microsoft.UnifiedTelemetryclient Microsoft.WindowsDefender Microsoft.WindowsErrorReporting Microsoft.WindowsMediaPlayer Microsoft.WindowsMixedReality Microsoft.ReaderPDF Microsoft.SubsystemForLinux Microsoft.WindowsToGo Microsoft.XboxApp Microsoft.XboxGameCallableUI RemovePksList Code: Microsoft-AADBrokerPlugin-Package Microsoft-AssignedAccessLockApp-Package Microsoft-BioEnrollment-Package Microsoft-ContentDeliveryManager-Package Microsoft-LockApp-Package Microsoft-MapControl-Package Microsoft-ParentalControls-Package Microsoft-PeopleExperienceHost-Package Microsoft-RetailDemoContent-Package Microsoft-SettingSync-Package Microsoft-SkypeORTC-Package
Did the test with updates integrated and got the same results---no problems that i could see. Btw I do all my testing on a separate physical drive
you mean if i choose to work with 17663.437 it will not be supported by the toolkit ?? and I will have to start with the first released which have bugs and delete user files ?!! this is not good, i like to work with the last refreshed image from microsoft and i don't care about integrating anything except for netfx3.5 and directx9 (netfx 4.8 should be integrated in new windows 10 versions) all what's essential is to be able to remove all the bloatware and the junk compnents and apps
The ToolKitHelper method manually removes the component files and registry setting and the initial coding is done based on the base image. With the refreshed images the updated component files and registry setting added by updates also need to be removed manually which differs from one CU to another CU. I tried to automate this process but many registry keys needs the manual intervention and due to this I have to currently dropped it until further new method is worked out. You can integrate the updates after the component removal to have fully updated image which will be more updated than those refreshed images. No the removed components won't be returned, only a few empty directories or resource files may be created.
Due to the code protection added to the ToolKitHelper and the compression used it takes more time to execute, I have reduced the compression level still It's taking time, will check with a better setting. You can use the group command this will reduce the overall time, like using SystemApps to remove All System Apps will reduce the time when compared to removing one by one. Thanks for testing, you used a Pro edition right? Thanks then I think the problem is with my test machine , which sometimes work and sometime give setup error.
No I have devised a new syntax to identify the packages for ToolKitHelper and DISM. For using ToolKitHelper method : ToolKitHelper_ParentalControls The ToolKitHelper_ is prefixed to the component name, the same RemovePkgsList.txt will be used for all components. For using DISM method : Microsoft-Windows-MultiPoint-Connector-Package From next version this will be working.
@MSMG I got the same error while trying to cleanup the image in step 6! ISO Information: Version: Windows 10 LTSC v17763.1 EN-US x64 Download: .iso via Torrent - https://forums.mydigitallife.net/th...rprise-n-ltsc-2019.76325/page-17#post-1467648 Instructions: 1. Disable any anti-virus software 2. Remove Editions [Tools>WIM Manager>Delete] 3. Mount ISO [Source>Select Source from Source <DVD> Folder] 4. Cleanup Image [Apply>Cleanup Source Images] 5. Remove Windows Components and Apps [Remove>Remove Windows Components] 6. Cleanup Image [Apply>Cleanup Source Images] <-- ERROR POPPED UP HERE 7. Customize [Customize>Apply Tweaks] 8. Apply & Save Changes [Apply>Apply & Save Changes to Source Images] 9. Re-Build Image [Apply>Re-Build Source Images] 10. Save Image [Target>Create DVD ISO] Removed Apps: AADBrokerPlugin AssignedAccessLockApp BioEnrollment ContentDeliveryManager MapControl Parental Controls PeopleExperienceHost QuickAssist RetailDemoContent SettingSync SkypeORTC Removed Components: AdobeFlashForWindows AssignedAccess Customer Experience Improvement Program EaseOfAcessThemes EdgeDevToolsClient FaceRecognition GameExplorer InternetExplorer KernalDebugging LocationService MultiPointConnector Paint RemoteAssistance Smartscreen SnippingTool UnifiedTelemetryClient WindowsErrorReporting WindowsMediaPlayer WindowsMixedReality WindowsPhotoViewer WindowsReaderPDF XboxApp XboxGameCallableUI Customized: Disable Cortana App Disable Automatic Driver Updates through Windows Update Disable Automatic Downloading and Installing 3rd Party Apps Disable Automatic Windows Upgrade
Checked with image cleanup and didn't get any errors, here's the steps I did : 1) Mount image 2) Cleanup image 3) Remove all components 4) Cleanup image 5) Saved the image
In the previous version I had implemented a automated method to recognize and remove the language resource registry keys but there was drawback it also removed some of keys bit early and trigger the log to report reg key removal failure and so I had to revert back to old method of removing the language resource registry keys which has increased the code size. And the code protection I have added with compression takes time to load, will checkout for better setting so that the executable will run faster.
@MSMG ,Actually in the regular integration tasks, the Metro Skin Integration Task for Windows Photo Viewer, Windows Media Player, and Win32Calc are work normal. Also, there is no running problem obviously with the components of the integrated skin. maybe you can delete version judge to test corresponding feture.
Since MSMG Toolkit won't support CUs and SSUs for some time, it means I won't need to build my image every month like I did previously. But I am experiencing ~30 second delays currently.
Microsoft are the ones making things hard for everyone with their bloatware. In any case, being able to remove stuff than not is of highest priority i'd say. I'm just waiting for a working 1903 version... even if removal is minimal. Whatever works is better than not work.
Wow, I never thought I would decide to switch to 10, this tool changed my mind Thanks for this great software, appreciate it