MSMG ToolKit

It's a shame, of course, to realize that there is no support for Windows 11 version 24H2.

 

It's a shame? When the dev is MIA, what do you expect?

 

Sorry, I understand that.

 

You need to login to view this posts content.

 

Still worth to use or do you guys prefer other programs?

 

Not relevant for new versions of windows.
I am using PowerShell 7.5.3

 

For Windows 11, is there an offline script that does the same as the below menu choice in MSMG's ToolKit?

 

That's what I did for myself. This script is for PowerShell

Spoiler: Disable Automatic Download and Install of 3rd Party Apps

# Монтирование реестра
reg load 'HKLM\TK_SOFTWARE' 'C:\Image\Mount\Windows\System32\Config\SOFTWARE'
Copy-Item 'C:\Image\Mount\Users\Default\NTUSER.DAT' -Destination 'C:\Image\TempReg\DefaultUser.dat' -Force
reg load 'HKLM\TK_NTUSER' 'C:\Image\TempReg\DefaultUser.dat'

# Отключение предустановленных приложений
reg add 'HKLM\TK_NTUSER\SOFTWARE\Microsoft\Windows\CurrentVersion\ContentDeliveryManager' /v 'OemPreInstalledAppsEnabled' /t REG_DWORD /d 0 /f >nul 2>&1
reg add 'HKLM\TK_NTUSER\SOFTWARE\Microsoft\Windows\CurrentVersion\ContentDeliveryManager' /v 'PreInstalledAppsEnabled' /t REG_DWORD /d 0 /f >nul 2>&1
reg add 'HKLM\TK_NTUSER\SOFTWARE\Microsoft\Windows\CurrentVersion\ContentDeliveryManager' /v 'SilentInstalledAppsEnabled' /t REG_DWORD /d 0 /f >nul 2>&1

# Отключение Windows Consumer Features
reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\CloudContent" /v "DisableWindowsConsumerFeatures" /t REG_DWORD /d "1" /f >nul 2>&1

# Настройка пустых плиток в меню Пуск
$regPath = "Registry::HKLM\TK_SOFTWARE\Microsoft\PolicyManager\current\device\Start"
if (-not (Test-Path $regPath)) {
New-Item -Path $regPath -Force | Out-Null
}
Set-ItemProperty -Path $regPath -Name "ConfigureStartPins" -Value '{"pinnedList": [{}]}'

reg add 'HKLM\TK_SOFTWARE\Microsoft\PolicyManager\current\device\Start' /v 'ConfigureStartPins_ProviderSet' /t REG_DWORD /d 0 /f >nul 2>&1

# Отмонтирование реестра
reg unload 'HKLM\TK_SOFTWARE'
reg unload 'HKLM\TK_NTUSER'

# Копирование отредактированного NTUSER.DAT обратно в образ
Copy-Item 'C:\Image\TempReg\DefaultUser.dat' -Destination 'C:\Image\Mount\Users\Default\NTUSER.DAT' -Force

All of this can be disabled in group policies.

 

Hi dear firend @Jalihahali

Try to use the Install Media Customizer Kitchen - IMCK,
https://forums.mydigitallife.net/th...n-imck-formely-known-as-custom-toolkit.86170/
I and many others are using and works great.

Regards

 

Yes, but you're helping with testing, and I haven't released the new version yet.

But we're on our way to releasing it.

I'll let you know when it's OK!

The version that is available in my signature (visible in the desktop version of the forum) is from last year.

 

Anyone still using WIndows 10? 21H2 LTSC?
Tried applying the november 2025 cumulative update?

I get an error 0x80073713 - The image is not servieable and may be corrupted. Discard the image and try again

Using MSMG toolkit 13.7. Yes, I know that toolkits last supported version was 4291.
I'm using a clean unmodified 19044-1288 ISO as my source.

I tried it outside the toolkit, just using DISM /add-package and the error is of course the same.

Anyway around this?

 

MSMG doesnt support that version so go back to an older ISO and service that one instead
if the error persists even outside MSMG with the older ISO, its the ISO, RAM or disk that fault. Check SHA1

 

@Yanta https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/page-193#post-1896330

 

Thanks for getting back to me.

The ISO and the CU are good. Been using the ISO for years. Since 1288 came out
.
The toolkit DOES service 19044.1288
From the changelog.txt file...

Code:

+ Updated the Feature "Remove Windows Component" to support Windows 10 Client Enterprise LTSC 2021 (v10.0.19044.1288/v10.0.19044.4291 [KB5036892]) Source OS.

Yes, I know that toolkit doesn't allegedly "support" CUs past 4291, but it has been working anyway. The only mention of the CU in the code is at line 2616

Code:

if "%ImageServicePackBuild%" equ "4291" set "IsCustomRemovalBuild=Yes"

Which is completely irrelevant because I am servicing a supported 19044.1288 ISO.

And we can tell 1288 is supported from line 2614

Code:

if "%ImageFlag%" equ "EnterpriseS" if "%ImageServicePackBuild%" equ "1288" set "IsCustomRemovalBuild=Yes"

Any way, getting off topic. The question was why is DISM reporting that the image (install.wim), is not servicable?

The Oct 2025 CU worked (19044.6456), with zero issues. My current windows installataion was created using the toolkit kit with 19044.6456.

Whether supported or not the toolkit has been happily integrating the CUs since 13.7 and all functions of the toolkit including removal work as expected.
Besides, all I am trying to do is to integrate the CU.

So I gather the toolkithelper.exe must use the CU number (perhaps for the component based servicing registry keys for the various packages?

for example;

Code:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages

And package files seem to be getting removed.

I'm at a loss as to why you would think my RAM or DISK is at fault just for this CU?
But I tried it on another computer anyway and the results are the same.

@shhnedo not sure what I'm looking for on the post you linked. Can you give me some contexxt?

 

Updates since November Patch Tuesday will need ESU Suppressor in order to integrate them. The issue isn't in your iso or the updates themselves, it's the lack of esu suppressor, esu updates can't be integrated without it. W10UI script already utilizes esu suppressor. @abbodi1406 even made BypassESU X for cases such as this. See ReadMe file for detailed instructions.

 

My thoughts exactly. I read some stuff on WindowsForum and massgrave and neither suggested anything like needing and ESU Suppressor. "If it's LTSC updates are supports to 2027 for lTSC and 2032 for IoT LTSC".

I wouldn't have guessed LTSC updates are ESU updates. I thought that applied only to Home and Pro, not Enterprise.

Any way, I'll have a look at ESU Suppressor and see what gives.

thanks.

 

You need to login to view this posts content.

 

I'm sorry if my question comes accorss as Naive. I was unaware that EditionID was the only method M$ uses to verify what is installed. I honestly thought it was more complicated than that.
But my question was not meant to be cynical or to sound "entitled" which seems to be how I've come accross.

So then if LTSC and IoT LTSC are supported until 2027 and 2032 respectively how does one get updates?
And apply them "offline"?
Also, correct me if I'm wrong but don't CUs reinstall everything that the toolkit removes?

I'm sorry to have wasted your time.