Thank you for the update. Looking forward to the ability to remove advanced components like cortana and defender. I know the CU's put them back on currently.
Would be so nice to see. For me, and for most of us, I think having system removal [and hopefully being able to do so in batches than one by one] as well as some advanced windows components is most important. I don't even add .NET 3.5 anymore, a lot of software have moved on. By not adding .NET 3.5 I also think it reduces the risk of having 'dirty' images after finalizing. So to say, nice of priority can be on [removals] while [additions] could come later
I know. But still, if I integrate it, my start menu is broken. I'll stick with the ugly metro calculator app.
I'm sorry, I don't understand your answer You mean we cannot cleanup an image after integration of .NET 3.5 ?
Yes, offline enabling dotnetfx35 will set the pending flag, with the pending flag set, no image cleanup will be performed.
These initial cab files available from MS are uncompressed, will replace them once the MS release compressed one. Use version 10.0.14393.0 .NET FX48 cab files for RS1 and RS2 Use version 10.0.16299.15 .NET FX48 cab files for RS3, RS4 and RS5
You can remove the restrictions on the revisions in Toolkithelper.exe to resolve the issue of recovering removed components after Windows 10 version 1903 cumulative update installation. Although there will be problems with toolkithelper to process refreshed Windows 10 versions, you can include some related tips and instructions in various instructions (such as readme files).
Which applications do you refer to? The modern apps that come preloaded like store, camera, alarms etc.? You could try to remove all first, and then download and integrate the updated versions. App installer now comes as a single multi-arch package that is not compatible with the toolkit, so you would have to update that one online. After deployment, open the MS store and let it update. It will update the app installer. Cheers.
First thank the author for this titanic work and the rest of users who contribute with their comments, I follow since 1803. Second apologize for my bad English In the latest version of this tool I am not clear about this new instruction: "[E] - Cleanup the Source Image using [Apply->Cleanup Source Images] menu. (Only if not integrating Windows Updates, do the cleanup image else not required)." The translation into Spanish fails, if I do not install any update and step from [A] directly to [F], whether or not I should perform point [E]? Thanks again! Version to use: 17763.1.180914-1434.rs5_release_CLIENT_LTSC_EVAL_x64FRE_en-us
lol no i know whats going on. just putting latest info on the forum, every page or 2, there is the question or comment stating that something doesn't work or what to use
Dice que el cleanup solo se hace cuando NO vas a integrar actualizaciones, pero si vas a integrar actualizaciones no se requiere hacer este paso. Tu sabes que LTSC EVAL no se puede activar cierto? Saludos.
Gracias! Lo se, prefiero que sea asi, cada mes formateo e instalo desde 0, soy un purista. -------------------- Thank you! I know, I prefer it to be that way, every month I format and install from 0, I am a purist.
how long before this is fixed: The "ToolKitHelper_CEIP_SQM" command does not work in Removal component via Package List still not fixed in 9.3.2
Do check the RemovePkgsList_Template.txt, the syntax has been changed, now ToolKitHelper: is used instead if ToolKitHelper_
:: Checking whether the selected Source OS is a Windows 10 19H1 Client Non-refreshed Image if "%SelectedSourceOS%" equ "w10" if "%ImageBuild%" equ "18362" if "%ImageServicePackBuild%" neq "1" if "%ImageServicePackBuild%" neq "30" ( echo.ToolKit component removal only work with the below Source OS Images... echo. echo.Windows 10 v1809 ^(10.0.18362.1 and 10.0.18362.30^). goto :Stop the text is Windows 10 v1903 ^(10.0.18362.1 and 10.0.18362.30^) instead of Windows 10 v1809 ^(10.0.18362.1 and 10.0.18362.30^). please change this text.because 10.0.18362.* is not 1809,it's 1903