MSMG ToolKit

You need to login to view this posts content.

 

I'm having a bit of a problem:

I've tried using TK v9.5.7 several times over the last few days, the main issue is that it doesn't build a complete ISO. Install.wim is there, but Setup.exe and some of the other files from the original ISO are missing. So basically, it's not installable, either in a virtual machine or a real, live install.

The OSes I'm trying to customize are:

Windows 10 Enterprise 1909
Windows 10 Enterprise LTSC

Both of these are original MSDN ISO (not legit, but the SHA1s match the values that Microsoft published). I'm following the steps from the most recent readme.txt in the Mega downloads folder (not the one in the 7z archive). And I'm using the latest Toolkit Helper from Mega. Net Framework 4.8 is installed. I have removed components, integrated components, customized, but that's pretty much it. No driver/updates integration. Everything goes fine right up to building the ISOs. No errors, it builds fine. But they all have the issue I've mentioned above.

I'm not sure what to do to resolve this, except maybe wait patiently on a new TK release. Thanks for any help!

 

@MSMG: I did keep a list of removed components, but not integrated ones. And the TK deleted the logs after I exited, so I couldn't get a copy. In future TK versions, please don't delete the logs on exit, in case of issues. They normally don't take up much space anyway.

I will try another test run tonight on my LTSC ISO.

But there is one thing I should mention that could be playing a factor:

I first used the TK GUI to remove components from each category. Afterwards I selected the option to delete apps/components with a list, which presumably uses a combination of Toolkit Helper and Dism. I also edited the components/apps list template files, to only remove things that hadn't already been removed with the GUI. Sure enough, it caught some extras that the GUI missed. But I do wonder if using both might be the root cause of my issue. I will have to try 2 test runs, first with both options used, and 2nd with only the GUI used to remove.

However, I had done this in past TK versions with no issues.

Thanks again!

 

@MSMG: OK, first I'll try a run with only the GUI. And then another run with just the apps list/package list template. if either or both runs generate an incomplete ISO, then the issue is within the TK, not my method.

i just figured using both wouldnt hurt, since the apps/package list approach covers some components that the GUI misses. But mostly i get "component already removed".

Does one have an advantage over the other? Do both methods cover all apps/components regardless of which is chosen? And in regards to TK Helper removal vs Dism, which is better?

I'm also going to make the assumption that Windows shouldnt be allowed to update because removed components will return. At least, judging by recent comments.

Thanks!

 

Without meaning to put any pressure on you, do you think this removal --> restored issue will ever be solved?

I'm planning to move as many PCs as I can off Windows to Linux, which I'm currently testing, but my sons will always want to use Windows no matter how bad it is because of the fear of change and a learning curve.

So, for them, I'm wondering if I should start writing a script that re-removes or at the very least re-disables everything that gets restored that I can run after each CU. Given all updates here are controlled via WSUS, I could see myself not installing every CU. Microsoft breaks something with every CU, and typically takes 2 -4 months to fix the things they keep breaking, so maybe I will just move to installing CU's once every 3 months.

 

You need to login to view this posts content.

 

@MSMG

How I add MSDaRT in Windows 10 19041.84. It isn't appear in Menu..??

Thanks in advance..!!

 

I never heard that it was possible to remove the defender and SmartScreen packages from windows, as far as I know, this is possible only on the server.

Are there any innovations in removing components in the insider build?
If this is true, I want to see it in my work.

Please write me the build number and the command to remove the defender.

p.s.

Naturally, my assumption turned out to be true, that is, the system becomes more and more closed, on the other hand, third-party developers put pressure on them.

Commands for the command line also do not work, because after a while the system itself does what it wants.

 

can powershell 7 be integrated?

 

can insider 2004 be later 'upgraded' to rtm version without reformatting?

 

Yes, there will be only new updates (CU) that will bump up the 19041.xxx, no new compiled iso.

 

Which is why I said "Without meaning to put pressure on you". I just get a sense, that despite how brilliant you are with this stuff, that Microsoft may have finally made it impossible to remove components permanently. If that's how it is, then that's how it is.

I'm not planning to rebuild the ISO via toolkit every month, that would drive everyone insane. So, a smaller, automated script that I can run after I install a CU will have to be enough. Microsoft's habit of breaking patches every month actually works in my favor. I just install every third or fourth one, then run a cut down script and be done with it.

 

I've been out of the loop for a while, my initial experience with W10 having been so dire that I've been muddling along on W7.

However I need to move to W10 now unfortunately.

Am I to understand that even if we remove components prior to installation, via either this / NTLite / other, or remove them via Power Shell once installed, that all the junk will be reinstalled with each CU? They've completely removed the ability to have minimal installations without constant intervention on the user's part?

How on earth can this work for corporate or education deployments? Or does it not apply to Enterprise / Education / LTSC editions?

Just built a new PC and was dreading sorting the W10 installation enough already before reading this