MSMG ToolKit

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Don't think that will work, extracting cab from the exe.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

That's 4.7, NOT 4.7.1... Why would I want 4.7.0 installed before 4.7.1? The 4.7.1. 300MB+ cab is the full AIO package AFAIK...

BTW, Toolkit does not bother with checking out what should be updated first. It ignores SS... It just uses alphabetical/numerical order to update the image... Toolkit would install SS last if it was numberticall last... Not good. I don't remember that being the case last time...

EDIT: W10UI 3.7 installs SS first . I wish MSMG Toolkit used the same method... Does W10UI 3.7 auto-apply full DISM rebase tweak by default?

EDIT: W10UI 3.7 updated install.wim and winre.wim, but not boor.wim? Why not? Does boot.wim need to be specified for it to update it?

 

You need to login to view this posts content.

 

W10UI 3.7 usage to update boot.wim resulted in an error during boot from USB. It stated I had missing drivers. The same did not happen when using stock boot.wim and when using boot.wim updated with NTLite... All to the same version 1914... LTSB x64...

Where is thread for W10UI? I keep losing the link to it over and over...

 

It works fine on my projects, you may ask yourself why all things go bad when you tinkered with the files.

 

What files? I used nothing, but W10UI 3.7 to update install.wim and boot.wim + rebase. Install.wim and WinRE.wim updating worked fine, but updating boot.wim resulted in missing drivers when booting from USB drive, although the actual W10UI 3.7 process for boot.wim succeeded with no issues.

 

has anybody attempted removing all the toolkit allows from a ltsb iso?

 

ok cool, will try that

do I have to mount everything?

 

The same here on LTSB 2016, boot.wim updated "successfully" via DISM

 

I mounted everything (boot 1+2, winre and install), in my case it was necessary to integrate custom winre.wim. I removed all the toolkit allows with no issue (v 7.7)

EDIT: Ignore removing Edge, on LTSB version it doesn't exist

 

[QUOTE="in my case it was necessary to integrate custom winre.wim
[/QUOTE]

what do you mean by that?

 

On MSMG Toolkit if you need to integrate a custom winre, you have to mount all images (boot 1+2 too); if you do not mount all the images you can not replace the default winre

 

When you mount the winre.wim you can't replace it, when applying the winre.wim from the first mounted wim will be unmounted and copied to all other mounted indices (if there are multiple mounted indices).

If you want to put another winre.wim into an index, just mount the install.wim and browse to the "mount folder\windows\system32\recovery" and paste the winre.wim.

 

Which was the last version that worked with LTBS 2016 and could somebody upload it. Pritty please