MSMG ToolKit

With the feedback that the guys are mentioning, I was already thinking about a filter for those who, if they wish, can check dependencies and if their selection is saved from known problems. This way, the advanced users can ignore the dependency filter and can do their own tests.

Now, with that mention of yours, I feel like it's a confirmation of the need for that. Before, I just thought that completely automating dependencies would be a general solution and save everyone time. @MSMG even tried to open my eyes about it, but I didn't understand it at the time.

But there are always exceptions to the previously established rules. These exceptions become new rules and must be implemented, in order to keep everything up to date.

I had already sent a preview of this filter to @MSMG. He's very busy. But always, he comes with an improved idea on the subject, hehehehe

 

You need to login to view this posts content.

 

I got it from uupdump.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I mentioned Microsoft Edge Chromium integration causing pending.xml for anyone doing troubleshooting, if I recall, the readme doesn't mention this, only that .Net 3.5 should be applied after cleaning and not before due to the cleanup error message for pending.xml which is normal. Just providing informat. (LTSC 2019 16377.1637 x64)

Also, I have found the problem causing DISM (dism /online /cleanup-image /scanhealth & /restorehealth. Error: 2. The system cannot find the file specified., it happens when I add Microsoft Visual C++ Runtime packages on LTSC 2019. Even on the base image with no changes. I've been trying to figure it out for a week+. I have not tested Powershell 7 integration, but it's probably fine.

Thank you for your hard work MSMG, hopefully this saves you or someone else some time troubleshooting. I cannot get the logs from the VM, sorry.

 

You need to login to view this posts content.

 

Dear @MSMG,

I created a special script to install fonts into the image.
This script is not mine, I collected it from various existing sites and adapted it to suit the needs of installing fonts.

Put custom Fonts folder to toolkit\Custom\Files\
Put AddOffFonts.ps1 to Bin folder.

Run from batch file (Toolkit.cmd - :IntCustomFiles)

Code:

set "CustomFonts=%CustomFiles%\Fonts"
if exist "%CustomFonts%\*.ttf" (
call :MountImageRegistry "%InstallMount%\%%i"
PowerShell -nop -c "%Bin%\AddOffFonts.ps1 -mountPath %InstallMount%\%%i\Windows\Fonts -fontsPath %CustomFonts%"
call :UnMountImageRegistry
)

Successful when applied to Win10 images 19041 and 17763 builds. I've tried it.

Please feel free to use it or not for more completing your great project.

Enjoy.

Edit:
Add load and unload registry command.

Edit 2:
Forget to commenting the $fExist.Close() line.

 

Silly question but does .NET 5 cover 3.5 as well?

 

Nope. This is not about "components" or removing parts using MSMG or whatever. This is about M$ bad design.
M$ had a several attempts to fix NCSI bugs and "yellow trianlge" with updates, but it still working weird for many people.

Just reconfigure your NCSI - this fix their bad way of working, plus it will become fast and safe.

 

Yes. The fonts will registered and copied to mountImg\windows\fonts.