i am also not registered there as those scripts are shared by one of my friend rajeev via an email & as i changed my hardware 2 months ago i lost any of paul scripts these days . am extremely sorry Kind Regards, Karan Kumar INDIA
Is it normal for Component Store to become corrupt as using MSMG Toolkit? I didn't integrate anything, but removed a ton of stuff. I assumed MSMG Toolkit could preseve Component Store and file integrity. If aditional cleaing from Toolkit Helper is what causes corruption, then can we get an option to not use it and get limited feature removal that preserves Component Store and file integrity? Also, can MSMG Toolkit remove dependence of Windows PE (Index 2) in boot.wim? I remove Windows PE from boot.wim and that results in MSMG Toolkit displaying an error that it can't find Index 2.
Removing too much can always cause errors. MSMG isnt perfect and with MS updating stuff "constantly" its more difficult to maintain a proper working tool I guess.
i think none of the .NET Core / .NET versions are backwards compatible fully, there is always some sort of binary or source incompatibility resulting in various degrees of breakage, which is why they are all co-installable you can target multiple .NET versions in your app, but its safe to assume that it will always require manual changes. for the MSVC case, yes they are (mostly) binary compatible, which is why 2022 shares the major version with 2015, although there are still some restrictions: - an Application built with 2022 must use a 2022 runtime, an app built with 2015 can use a 2015; or anything up to (currently) a 2022 runtime - there are some compiler flags which break this for Static libraries or object files ( namely /GL and /LTCG ), but this is only relevant for building an app, not running iit.
If using the source image with right CU specified in the latest changelog.txt then removing components won't corrupt the component store, do specify the source image used? Using Cleanup Image (DISM /Cleanup-Image /StartComponentCleanup /ResetBase) will give a ghost SFC error. Adding support for skipping Boot.wim (Index 2) needs modification for all Toolkit features related to boot.wim image, will see what can be done.