There are components which I can only remove if I use one of them and I have problems even if I only use one of them, anyway.
I have had no problems when using MSMG ToolKit, but when it comes to NTLite, where do i start, NTLite is bloatware with to many settings, which can and does cause errors.
ahh ok that worked. Thanks Can you also make it so that before doing actions under option 7 the toolkit automatically grabs the Autounattend.xml from the Autounattend folder. So all we have to do is put our copy in that folder and it gets copied over everytime if there isn't one already please.
Problem with nLite, settings are not user friendly, you really need to know what you are doing, and you will definitely mess up Windows 10 using both tools on the same install.wim.
Nlite? You mean NTLite? Ok, but even just using MSMG ToolKit it may break Windows 10. Even without using any of them (or other tool like that) and after doing a clean install and signing in for the first time in to the user account, Windows 10 is broken like I've already told.
No, local account. I have things in english (like msconfig.exe's title) and not in my native language even after doing a clean install with an untouched image and without having set a thing. I have other problems but they're so many I can't remember all of them. And some of them come from earlier RTM Windows 10 Enterprise x64 versions.
hm i cant find the toolkithelper: instructions i wanna customize my removal list.where do i begin? also, i see there are some removeapplist packages that seem similar to the toolkithelper: ones.. do i remove from both lists? update: oh, to my surprise, its in bin/ now
Filename is: 18362.1.190318-1202.19H1_RELEASE_CLIENTMULTI_X64FRE_PT-PT.iso and sha1 is: 31bb4a3c54b6f298173b783090c778f69300ba32. I still don't know which is the 19H1 build, 18362.1 or 18362.32 (maybe if I use the latter I won't have some problems). What's the difference between using the 18362.295 Build or the 18362.1 one with KB4512508 integrated, by the way?
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. With ToolkitHelper when a component is removed then the associated policy definition is also removed and I don't see any errors while opening the gpedit.msc, may be it's due to using both the tools it's corrupting the image. As far a start menu layout I have given enough info about that including the Microsoft own website info about how to use it and yes you have to copy the layout to w10_CustomStartMenuLayout.xml in <Bin\XMLs> folder.
Yes since the pack folder contents was moved out of the main archive, I had to move all XML's and Lists to Bin folder. If you are using ToolKitHelper to remove Apps and components then it's sufficient to use RemovePkgsList.txt
That's what I did and I imported it afterwards and although I no longer have Start Menu tiles I still have unwanted taskbar icons and don't have the Task Manager pinned to it (taskbar). When I clean up the source image for the second time it only reaches 20% (all 4 times).
w10_RemoveStartMenuTiles.xml is a left out item while cleaning, it was used when the DISM method was used to remove apps, it will be removed from next release. You need to add the layout to w10_CustomStartMenuLayout.xml and use the menu Import Custom Start menu layout from XML file. Using the <DefaultLayoutOverride> will remove all default tiles and use the one specified in the XML, do study the links I had posted earlier for further customization. Same as PinListPlacement="Replace" will remove all default icons in taskbar and use the one specified in the XML. For Task manager link, as I have specified you need to create a shortcut link to it in start menu - programs - system tools folder, only then it will show up in the taskbar. You can also use the Autounattend.xml file to add shortcuts to Task bar, do google out, will find more info. Will try to test with Start menu layout when I'm free and will report back. And regarding the cleanup up, it's usual for the DISM to reach just 20% in second run.