Yes MicrosoftWindows.Client.Photon is not that important to normalise my System Behaivior . . . more they other package when Removed keeping Peace. I can also see them not but im using NTLite to Check Component "Windows Copilot User Experience that also is Discripet as Copilot + Recall" thats includes i think the packages like it is by "Client.CBS or also named Windows Feature Experience Pack". Th@nks for reminder on CBS servicingin !
I think this week. You will know when my signature changes. Note: Signature just doesn't show on mobile. Yes, it is in that path, but the Toolkit folder should be 10.0.22621 not 10.0.22631. Because Toolkit works with the base Build.
Since conversations regarding other topics should be handled in their respective threads (if such a thread exists), I have already redirected our conversation to the IMCK Thread which is the appropriate place .
Code: [2] Integrate -> [4] Windows Updates -> [2] Integrate WHD Update Pack -> [1] Integrate WHD General Updates -> Select one of the options below depending on the images you mounted. [2] Integrate to Windows install.wim Image [3] Integrate to Windows Setup Install & Recovery Image [4] Integrate to Windows Setup Boot, Install & Recovery Image If you have boot.wim image mounted... [2] Integrate -> [4] Windows Updates -> [3] Integrate Windows Setup Media Updates ->
General question regarding the removal of Windows components from an ISO and integrating Windows updates into the ISO: Is it generally better to integrate Windows updates into an ISO first, then remove Windows components after? Or can I get away with removing components first then integrate updates later? I'm interested in people's experience. Thanks!
If we could integrate updates after removal, it wouldn't make sense why we would need this feature. So, we would just need to make the ISO and finish the Windows update after the clean install. If that were the case, we would be very happy with Windows. But the reality is that when we install updates, several components that were already removed come back from the dead. Just follow the sequence of the Toolkit menus, it should be successful (only netfx3 that I usually integrate using Enable Features in the Customize Menu, instead of the Integrate Menu option. But for 24H2 even this is causing problems with Windows Update). The new updates for 24H2 are coming with complicated integration schemes, this is really a mess that changes the pattern every week (now there is a need to integrate a sequence of previous LCUs to follow a dependency checkpoint to work with more FoD updates and not to interrupt the rollback operations). Perhaps MSMG, besides being busy and lacking time, should wait for some stability from MS to change the integration method to 24H2. This is also the main reason why I have not yet released IMCK. In short: Using Windows Update after using component removal doesn't make sense, unless you only "remove components from the removal menu 8 that shouldn't return (big quotes here)". Otherwise, remove the unwanted components, disable Windows Update and do an Inplace Upgrade monthly with an updated ISO. There are users here who also have reservations about Inplace Upgrade. But for me it's the best option to maintain daily use if you have a lot of installations to be done in your work environment. If not, do clean installs and be happy.
Thanks, I'll integrate Windows updates first, then after that is done, remove components after. Makes sense.
After enter [1] Integrate WHD General Updates -> You select ONE of... If you have mounted only install.wim. Please choose [2]; If mounted install.wim & winre.wim (Recovery). You can choose [3] or [2]; If mounted boot.wim, install.wim & winre.wim (Recovery). You can choose [4] or [3] or [2]; It depends if you want to integrate updates for boot.wim or for winre.wim. Option [1] only for boot.wim, from [2] to [4], all of them will integrate for install.wim. This 2 -> 4 -> "[3] Integrate Windows Setup Media Updates" isn't in above options that follows the 2 -> 4 -> 2 -> 1 path.