the iso size increase just because microsoft integrated edge chromium C:\Program Files (x86)\Microsoft C:\Windows\WinSxS\amd64_microsoft-windows-edgechromium_31bf3856ad364e35_10.0.19041.928_none_ddb08bafba9680e6 C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-edgechromium_31bf3856ad364e35_10.0.19041.928_none_ddb08bafba9680e6.manifest
Thanks for linking, that actually makes sense. So it appears that it's not an issue with the toolkithelper, just a change (embedded WIM) in the way MS included EdgeChromium in the CU. Cheers.
I don't know if that would make any sense in your case. Since you didn't describe how you modify your iso image using the Toolkit - whether you integrate it at this stage .Net 3.5 and .Net Cummulative, or not. Whether you remove some components or not. Whether you plan to use the CU installation from the Update Center in the future, or not. I see it more logical - immediately after installing the OS, enable Net 3.5 and install the latest .Net Cummulative update, as well as other components that you may need (.NET 5, and so on), if all this was not done at the stage of preparing the image using the Toolkit. And then perform image cleanup: Dism /Online /Cleanup-Image /StartComponentCleanup And only then perform a check and fix using: sfc /scannow (After each image cleanup run, you will get an sfc error, which you will have to fix again with sfc /scannow)
Am I missing something? I don't want to remove Cortana/SearchUI but it seems regardless of how I set up MSMG TK, it removes it. I'm also making sure that Speech Recognizer is enabled and Cortana. Trying to optimize a 2019 LTSC image.
This is a rather strange question. You need to read up on features included in LTSC, Cortana isn't one of them. So this is not an issue with the toolkit removing Cortana, it simply wasn't there. If you need Cortana, you will have to use a different SKU. Cheers.
Don't remove SpeechRecognition. In win10 v1809: WindowsSearch -> depends on -> Cortana -> depends on -> Speech Recognition.
You need a 19041.1 base and the respective updates from this post. You COULD use said updates to update your 19042.631 source, obviously without the 20H2 enablement package.
ok so i got it all wrong. I downloaded from microsoft the latest version Win10_20H2_v2_Italian_x64.iso (19042.631) and I was starting from this. I'll have to search for and download a 19041.1 sorry for the inexperience
Sometimes it happened like this (ssu has been added...). I don't know why. I had to cut out all the downloaded updates from the UUPs folder, and then manually run convert-UUP. cmd In ConvertConfig.ini: [convert-UUP] AutoStart =0 AddUpdates =0
I only mentioned the "technical tool usage" method, the reason the option is in the ini file. You could easily have deleted the updates during the initial conversion and wim creation and leave all running.