MSMG ToolKit

Yes, rename this file to "ToolKitHelper.exe" , copy it and place it with the replacement of the old file at the path: Toolkit\Bin\

UPD. I'm sorry, it so happened that we sent our messages at the same time as @MSMG

 

Retried the integration earlier, did this one after integrating .NET, and it worked. Thanks a lot.

On which part/step do I need to do this, anywhere after integrating updates?

EDIT:

Noticed that it download "Windows Malicious Software Removal Tool x64 - v5.102 (KB890830)" when I run Windows Update on the VM.

Can I just download this from the MS update catalog and plop it down on the same folder as the updates? Or is there an option in the tool to integrate this?

 

Thank you, I'm waiting

 

It's not fail for integrating CU on my PC, Just SSU .2 or .160 both of them are unstable.
I have a proof, See screenshots.

Spoiler: .160

Code:

C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\160\SSU"

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.22621.1

Processing 1 of 1 - Adding package Package_for_ServicingStack_160~31bf3856ad364e35~amd64~~22621.160.1.0
[==========================100.0%==========================]
The changes due to package Package_for_ServicingStack_160 requires the current servicing session to be reloaded.
All the packages will be processed again.
The operation completed successfully.

C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\160\SSU"

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.22621.1

Processing 1 of 1 - Adding package Package_for_ServicingStack_160~31bf3856ad364e35~amd64~~22621.160.1.0
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\160\CU"

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.22621.1

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.160.1.3
[==========================100.0%==========================]
The operation completed successfully.

Spoiler: Screenshots .160

Spoiler: .105

Code:

C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\105\SSU"

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.22621.1

Processing 1 of 1 - Adding package Package_for_ServicingStack_2~31bf3856ad364e35~amd64~~22621.2.1.1
[==========================100.0%==========================]
The changes due to package Package_for_ServicingStack_2 requires the current servicing session to be reloaded.
All the packages will be processed again.
The operation completed successfully.

C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\105\SSU"

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.22621.1

Processing 1 of 1 - Adding package Package_for_ServicingStack_2~31bf3856ad364e35~amd64~~22621.2.1.1
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\105\CU"

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.22621.1

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.105.1.7
[==========================100.0%==========================]
The operation completed successfully.

Spoiler: Screenshots .105

 

I'm getting a version mismatch error when trying to integrate the x64 SSU and LCU from this post (MSU format):

https://forums.mydigitallife.net/th...-21h1-2-vb_release.80763/page-16#post-1571109

Source image: en-us_windows_10_enterprise_ltsc_2021_x64_dvd_d289cf96.iso

This is what @inTerActionVRI suggested to do, so that i could bump up the base version, to enable component removals to work as intended (all this effort just to fully purge Edge is getting on my GD nerves!).

What other updates am I missing besides these 2?

The installed version of this image in a VM is 19044.1288, no updates installed whatsoever. Yet for some reason the TK identifies it as being 19041. I also manually installed these 2 MSU files in the VM, first the SSU and then the LCU. Both installed without issues, and according to winver the version of the OS bumped up accordingly to 19044.1766. Why do these updates work on a live system, but fail when integrating offline?

Edit: I didnt integrate any features, language packs, etc. I just told TK to mount the source image, then went straight to the update integration step.

 

I didn't use WHD to download the files. I guess you missed my link in my previous post, they are just MSU files that were downloaded from that linked post.

I was using the preview exe, but renamed to just ToolKitHelper.exe

Edit: the update files you mentioned are specifically the ones I need for LTSC 2021 (already dropped the ISO name I'm using, so let's not even get into me not properly establishing my source)?

 

I'm honestly getting quite exasperated trying to resolve this. Esp after I've been told that I need to integrate stupid updates into the image, just to remove components. I'm just about ready to say f the TK and move on, it's becoming more time consuming than it's worth. Nothing personal against you or an insult to your work, but i don't see how you and your folks here at MDL put up with this headache. Constantly having to test and fail and re-test, ad nauseum to infinity and beyond.

Proof that your TK is misidentifying my LTSC version as 19041, when it is in fact 19044.1288:

 

No offence, but I honestly don't think you realise how fortunate and lucky we all are to have @MSMG work and produce this magnificent ToolKit for us. He also works and uses his spare time to produce this ToolKit. He isn't paid for working on the ToolKit and I can imagine that comments like yours can be truly disheartening for @MSMG to read.

Think about what you say and how you say things in the future. We are all human beings at the end of the day.

 

You may be right. I'm not disrespecting his work. And nothing is perfect. But it seems to take alot of patience to use it. Which is a character trait I'm not known for.

All I know is, I'm told that I have to integrate updates before component removals will work as expected. That user gave a link to a post, containing updates that would supposedly increase my LTSC's build # high enough to make it "compatible" with TK's removal process. So I go to try to integrate at least the SSU and LCU as a bare minimum. Those updates apply fine on a real installed OS but won't integrate offline. They must be compatible or they wouldn't have installed.

I'm putting in effort to try to get this to work, but it's not helping that suggestions from some users here have produced unexpected results.

 

Since you're complaining over free s**t why you don't put the effort to do your own trial and error, or you know, since you're so entitled, go and code your own solution?

 

don't waste your time arguing with people -
who doesn't respect people's hard work

 

@AnonVendetta,
such a "problem" is obvious only to you. Stop writing nonsense at last. You have already been explained several times what you need to do.
And WHDownloader has nothing to do with it.
You need to put the all updates on the path: Toolkit\WHD\w10\x64\10.0.19041\
and follow the Toolkit menu:

- Select the source using Toolkit : [1] Source -> [1] Select Source from <DVD> folder

- Choose [2] Integrate -> [4] Windows Updates -> [2] Integrate WHD Update Pack -> [1] Integrate WHD General Updates -> [2] Integrate to Windows Setup Install Image

- Remove the components: [3] Remove ->
1) Select components for removal: [1] Select Windows Components -> [1] Internet -> [2] + Edge Chromium Browser
2) Remove selecting components^: [2] Start Removing Windows Components

- Apply changes to the source: [5] Apply ->

 

You say WHDownloader has nothing to do with it. So, why does the TK have 2 folders from which updates can be processed? The presence of a WHD folder would imply that updates downloaded via WHD are meant to be placed there. But since I merely downloaded 2 MSU files via a Web Browser, the regular updates folder (non-WHD) seemed to be the logical location.

Anyway, I'll try the 4 files he listed. Although I have no idea where to source them from, since only the filenames were given, no links. And I have no idea how he came to the conclusion that those 4 in particular we're the ones I need to use. I was never asking anyone here for a handout, regardless.

You say I should do the work, and I'm perfectly willing to do so. But it's quite hard when you know what you need to do and where you want to go. However, you are told that updates need to be integrated, with no hints given in regards to how to determine the appropriate ones for yourself.

 

You need to login to view this posts content.