MSMG ToolKit

hmm maybe i'm too hurried to judge the new system i installed Win10 Edu 20H2 x64 but the impression I have is the W10 LTSC is much more responsive for some reason and as i installed it in dual boot it was simple to get rid of it i opened the disk management and I deleted the volume, restarted and everything went back to "normal"

 

Just tried again and Edge Chromium is still there! Fresh install.wim from the VLSC iso. The only things I did were remove the Edge Dev Tools client and Edge, before applying changes (and getting rid of unused versions). Following that, I deployed it via WDS (PXE booted a VM...).

What are the steps that ToolkitHelper takes to remove Edge Chromium? I would like to try these manually and see if a certain bit fails with this particular iso.

I guess it would be take ownership of the "C:\Program Files (x86)\Microsoft\Edge" folder and delete it as well as removing the shortcuts from the default profile start menu and desktop. Is there anything else that needs to be done? (will only doing these things cause issues with SFC?)

Edit: I mounted the modified wim file and "C:\Program Files (x86)\Microsoft\Edge" in this wim is still present and contains the Edge, EdgeUpdate and Temp application files. This is with using the correct options (08 and 07) with removal and seeing the ToolkitHelper success messages.

Edit2: Running the removal process again (just Edge and EdgeDevTools) gives the message "The specified component has already been removed...", yet the above directory is still present - Toolkit thinks it has removed it, but seems to be looking in the wrong place.....

 

Thanks - this works fine - much appreciated What is the component name to use with ToolkitHelper if running this outside of the ToolKit (or adding to the list of apps & components to remove)?

 

1) I also forgot to select and copy by right-clicking, hehehe

2) I implemented this in CustomToolkit 10.8, it always returns to the menu we were in. I'll start the merge with 10.9 today.

If you can test it, when I release Custom 10.9...

For now, just read the latest chagelogs.
https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-874#post-1630630

Thanks!

 

@RaiyvaN

I see your good understanding how to make things friendly to a user, according to your changelog and pretty smart tricks.

I haven't slept more than 30 hours, so I'm going to try out another pleasant "images" for a while.
The laptop was given away, gifts were distributed, the pub is closed

See you tomorrow, friend.

 

ya I have tried several times to "modify" how the operations are done inside the script but it is a very complicated and difficult thing simply the script has at least 30,000 lines of code this really is not a thing for curious people and I as a beginner should only follow what the Master recommends of course I also see and agree with! @rayvan that we can leave the script with a graphical form more or less like this:: click here to do this or click here to do that you can understand my reasoning only the only mys 2 cents...

 

@RaiyvaN
I have another advice for you. Hope this will help to you + all users here as well.
Try to be sticked with short wording in the descriptions, changelogs, help, readme, etc. :
Shorter sentences & less long wording, more (enough) amount of chapters / column ponts / steps to proceed
This will take a less time to read + ability to understand better.

@Tiger-1

 

Okay that this is good for you too...

 

@Tiger-1 - Relax, I'm joking

 

hehe sorry me for something is that I'm having extra Windows problems , I like you very much friend

 

@Tiger-1 - Sorry me too. I'm far not "an English man in NewYork" (C) and my EN language skills sucks.
So reading the endless sausages with no punctuation marks and no paragraphs scares me a bit
Though your tips and experience are always welcome.

 

You need to login to view this posts content.

 

In the ConvertReg.ps1 script, I changed the lines on:

Spoiler: ConvertReg.ps1

"[HKEY_LOCAL_MACHINE\SOFTWARE" = "[HKEY_LOCAL_MACHINE\wSOFTWARE";
"[-HKEY_LOCAL_MACHINE\SOFTWARE" = "[-HKEY_LOCAL_MACHINE\wSOFTWARE";
"[HKEY_CLASSES_ROOT" = "[HKEY_LOCAL_MACHINE\wSOFTWARE\Classes";
"[-HKEY_CLASSES_ROOT" = "[-HKEY_LOCAL_MACHINE\wSOFTWARE\Classes";
"[HKEY_LOCAL_MACHINE\SYSTEM" = "[HKEY_LOCAL_MACHINE\wSYSTEM";
"[-HKEY_LOCAL_MACHINE\SYSTEM" = "[-HKEY_LOCAL_MACHINE\wSYSTEM";
"[HKEY_LOCAL_MACHINE\wSYSTEM\CurrentControlSet\" = "[HKEY_LOCAL_MACHINE\wSYSTEM\ControlSet001\";
"[-HKEY_LOCAL_MACHINE\wSYSTEM\CurrentControlSet\" = "[-HKEY_LOCAL_MACHINE\wSYSTEM\ControlSet001\";
"[HKEY_CURRENT_USER" = "[HKEY_LOCAL_MACHINE\wNTUSER";
"[-HKEY_CURRENT_USER" = "[-HKEY_LOCAL_MACHINE\wNTUSER";
"[HKEY_USERS\.Default" = "[HKEY_LOCAL_MACHINE\wDEFAULT";
"[-HKEY_USERS\.Default" = "[-HKEY_LOCAL_MACHINE\wDEFAULT"}

 

I compiled 20H2 with MSMG10.8. It passes sfc at first, but not after installing updates. This is a Microsoft update issue correct, or does 10.9 address that at all?

 

Can the tweaks (option 4 > option 8 >...) be run with the ToolkitHelper executable only? (i.e. ToolkitHelper D:\Deployment\Toolkit_v10.9\Mount\Install\5 [tweak_name?])?

If so, what are the names for the tweaks?

Thanks

 

@sergey130270,

The use of "if exist" and "if not exist" pointing to the same thing can cause conflicts. I went through this recently. Until I found out what was going on it was a lot of work. Even if it is not causing problems in your script, it is best to avoid it. In the use of "if defined" and "if not defined", it is the same.

Suggestions:

Code:

If exist "%WinDir%\SysWOW64" (
SET "HostArchitecture=amd64"
) else (
SET "HostArchitecture=x86"
)

Code:

SET "InstallWIM=%DVDSOURCES%\install.wim"
SET "InstallTempWIM=%DVDSOURCES%\install_temp.wim"
move /y "%InstallTempWIM%" "%InstallWIM%" >nul

then replace all:

%DVDSOURCES%\install.wim
to
%InstallWIM%

%DVDSOURCES%\install_temp.wim
to
%InstallTempWIM%

if you want to.

Why this for loop without any loop?
for /l %%i in (1, 1, 1) do (
Forget I asked this if you have plans for multi index.

 

I don't think so, because this part of the system is done via script with a system for comparing variables, without going through ToolkitHelper.exe.