@MSMG, EdgeChromium_w81(2).tpk duplicated in mediafire. In Toolkit.cmd: NET6 replaced for NET7. Updated the code block, the integration of the InboxApps that had been pending. Fixed a small typing detail in removes components on WalletService. It is not a bug, but corrected will respect the condition of Wallet dependency.
im kinda surprised by that, given that 6 is the current LTS and Core 3.1 is going EOL after next months update, then again, i don't really know how much 3.1 is used generally speaking since i only use 6 myself.
I don't know if NET7 replaces NET6. NET7 was released as stable, 12 days ago 7.0.0. Making an analogy: I think it is like VC ++ 2019 that came out of the cycle, since VC ++ 2022 maintains compatibility with VC ++ 2019. Maybe MSMG keep the 2 options. But if it's like I'm thinking, I don't think so. Let's wait. But in the repository "download.ru", MSMG has already made available the NET7 pack.
I learn every day from @MSMG ... This goes beyond the solutions brought on the Toolkit script, as he always answers a question of people who bring new questions and this always brings me new learning. But the subject of the moment is related to what I do in this learning, for the community here in the forum. The Custom Toolkit. I would like to receive feedback from my Toolkit Fork. And, I think maintaining Custom Toolkit here on his thread, causing a cross the information that even if you don't realize it, may be causing problems both him and me. For, as the new forum users tend to report their problems without saying what their procedures were, without informing which version of Toolkit was used, which built, etc., in my little experience in these years of participation, in the forum, I came to see Some small difficulties: mainly, to identify where the people's problems originated when we release an update. After all, they are people who are just starting their interaction with the forum. So, due to the massive changes that have been made from the transition from version 11.8 to 11.9 so far, Custom Toolkit is based on Toolkit, but very distinct from Toolkit. Thus, in this version 12.9, the one formely known as "Custom Toolkit" is gaining a name and becomes "IMCK - Install Media Customizer Kitchen". This has been thought, so that I can support users directly regarding modifications of IMCK, it is necessary to concentrate the messages directly referring to "IMCK" in a proper and specific place. Just for this reason, I'm creating this new thread. I will continue here, likewise, active and participant. In short: now if there are doubts about "IMCK", post there. This will continue to work the same way you already know. Links in my signature. NEWS (not yet available) The implementation of translation to "IMCK" is in its last phases. The same LOCALES can be used to translate Toolkit if the MSMG wants (the internal change in the script is massive, and I am checking everything, in a way that is readable to anyone who wants to read the code). But I think his plans for this will be applied in another way. Anyone who wants to translate into your language will have a tutorial on how to do it. In this case, you will be the maintainer of translations for your language. After the release, you can contact me or contact @bala1 which was responsible for transcribing script native English messages to create the translation variables, in the "LOCALES.cmd" file and also created translating from English to Portuguese, the "LOCALE_pt.cmd" file. Grateful for the attention!
MSMG ToolKit What can I remove from Windows 10 Enterprise LTSC 2021 if it damages the Operating System?
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.