sure you've got the sfc errors, but there's a plus for using media from msft directly. 1. longer times between releaces of media, this gives msmg more time to debug and what have you gain new components, 2. simpler for the end user to get the iso. not sure about 2.
If I'm not wrong you can remove components from monthly refreshed source ISO(say, 19045.3324) but you can't integrated Windows Language Packs/ Drivers/ Features, etc if you follow MSMG ToolKit's Readme.txt
Huge thanks! Any chance of moving away from NSudo? It requires Debug privilege/permission, which many disable to prevent Mimikatz attacks.
@MSMG, I found this detail that could be a potential problem. The finding of the variable "%ImageDefaultLanguage%" with the Windows version "~10.0" in package names ends up forming a parameter output variable in the function that looks like this: "%ImageDefaultLanguage%~10.0." I haven't tested it to be sure if it will cause any damage. But since this was visible, it can be worked around with this: %ImageDefaultLanguage%*10.0. %ImageDefaultLanguage%*11.0. (in the future... who knows?) %ImageDefaultLanguage%*12.0. (in the future... who knows?) So since %~1 is a parameter output. If nothing is passed to it, it will be represented as empty. The solution would be to check each occurrence of: %~10.0. and replace with: %*10.0. EDIT: hehehe %* is the output of all parameters. I don't know how to improve this. It is tricky. Leave it alone. But keep this in mind in case you need to do something about it. If anyone has any ideas...
@MSMG , In Toolkit 13.6 line 27: echo.Current Tooolkit directory contains spaces in its path. it should be echo.Current Toolkit directory contains spaces in its path.
Code: Automated script to install or integrate updates for: - Windows 10 - Windows 11 - Windows Server 2016, 2019, 2022