MSMG ToolKit

@MSMG
I don't completely understand how ToolKitHelper works, but I assume it is a AIO program for Windows 8, 8.1, 10, 1709, 1803 etc. Would it run quicker if perhaps each version of Windows had it's own ToolKitHelper, ie: ToolKitHelper1903, etc?

 

@MSMG
This is to bring in your notice, Today i tried to integrate drivers with newly build windows 7 ISO (August 2018 Build) [ISO Name:- 7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_PROFESSIONAL_x64FRE_en-us]. Tried with both version 8.8 and 9.4.2, but both failed. While mounting the recovery image for deployment, its getting failed. In 8.8 giving me an error like "Syntax command Incorrect" and in 9.4.2 application got exited while pressing "Y".

 

NTLite has evolved a lot over time. Initially it was not possible to integrate or install updates after removals but now it is possible however with several problems. I will explain with examples.

But the approach of the MSMG Toolkit I think is the safest because it does removals in a fixed build version.

The following examples are with similar or equivalent removals:

* NTLite with Windows 10 version 1809 without updates: No apparent problem.
* NTLite with Windows 10 version 1809 with updates: Error installing cumulative update (language removal seems to be the problem).
* NTLite with Windows 10 version 1607 without updates: No apparent problem.
* NTLite with Windows 10 version 1607 with updates: Error in Windows Setup (I'm still debugging but it looks something related to the BitLocker component).
* NTLite with Windows 7 without rollup update: No apparent problem.
* NTLite with Windows 7 with rollup update: Does not install the most current rollup (removal of the Windows Error Reporting component seems to be the problem).

Removing components and then integrating updates generates a considerably larger image (around 200 MB) than integrating updates and then removing components. Then there are the pros and cons to each approach.

Apparently with each new update, a review of how removals are done is needed, even a mechanism that dynamically detects and removes components like NTLite needs corrections over time. I see it as a cat and mouse game with microsoft.

 

and MSMG has the same problem Nuhi has. Constantly monitoring changes is not limited to removals tools either, ask @pf100

 

Dont forget the monthly bugs too that Nuhi and MSMG have to contend with, they spend time debugging a problem only to find out its an MS bug.

 

@AeonX

 

That's why I just decided to use the month-end updates. Often they correct monthly Tuesday patches. In this particular month there were security fixes related to speculative execution so this should come with many bugs and loss of performance. I will be a long time without updating waiting for corrections

 

Test'em before integrating them, dont bungem in expecting them to work, thats wot i have always said.

 

I think the best solution would be something between the 2 approaches to use a fixed version of Windows but with some updates. With each new version of the program validate with a windows update version. Something similar to what WinReducer does.

 

The problem is that some bugs you only notice after a while of use. I don't mind waiting, I used LTSB 2016 with update from early 2017 until last week

 

@AeonX I dont know to be honest, all i know is what is best for me. do a default install, update, capture, lite then deploy on an airgapped machine. that way i dont have to worry about updating after removals and telemetry.

 

I have limited werewithal to ponce about with windows, i havnt had my workstation on for over a week, just this one for some limited interweb stuff.

 

I personally think it is better to remove Windows Update or disable it and remove everything I want and not worry about updates after removals. In my opinion it will always be a headache to maintain compatibility with Windows Update and removals. For me it is enough to integrate updates remove what I want and not install more updates as long as this works and does not cause problems but this is not always possible if you use an older version of Windows that is not the focus of program development at the moment (all versions of Windows 10 before 1809, Windows 8.1 and Windows 7).

But this is a personal preference and just as your way of doing things is not what most want so MSMG and nuhi will have long work ahead to maintain compatibility with updates I believe in the future this will no longer be possible.

 

Same for me. all i care about is if the end result is stable or not. i accept there may be a bug or two, especially if i have tweaked the living daylights out of the end result, as long as the bugs dont affect what i do or i just dont give a damn.

 

i think people expect too much from @nuhi and @MSMG considering what w10 is like.

 

Exactly. You can't have the best of both worlds, especially in a closed-source OS. If people are not satisfied with the conditions Microsoft imposes on their system then they have to be willing to take the risk of the consequences of removing components and disabling things not designed to be disabled or removed. MSMG and Nuhi do a great job but even they have their limitations.

 

Ive been working with a full bore os for quite a while now so im used to the bloat, if youre gonna tweak you gotta do it on a full install and im pleased with the results so far. If you cant remove, disable.

 

having disables built into the toolkit is something i'd like to see. atm i use my own scripts and may even miss out other possible disables

 

i am always chasing that holy grail of tweaks i dont have yet. bareboning services annd disabling a lot of windows logging, space hogs, hogs and logs gives good results even if you dont do removals. powershell is too complicated for me but i can compile a good bat or cmd file.

I have a ton of tweaks spanning w7 8.1 and LTSC but unfortunately i dont have the energy to compile it all into a single file, its all a higgeldy piggeldy mess and i got to see if all those 8.1 and ltsc tweaks work on 7