MSMG ToolKit

MSMG · May 19, 2020

Will check what's causing the Toolkit to crash, can you specify the ESD info? Is it Store ESD or normal user created ESD?

talicni67 said: ↑

I have a problem with ToolKit 9.9. Convert esd to wim and when choose to mount setup boot and recovery image, ToolKit crash and disappear from the screen. Tried several times and always crashes in same place. Please, can anyone help me about this?

=
| Index | Arch | Name
===============================================================================
| 1 | x64 | Windows 10 Pro
===============================================================================

Enter the Image Index # : 1

Do you want to mount Windows Setup Boot Image ? ['Y'es/'N'o] : Y

Do you want to mount Windows Recovery Image ? ['Y'es/'N'o] : Y

after this ToolKit disappears.
Click to expand...

GianlukK · May 19, 2020

Hello guys, i'm new with ISO customization, was playing a bit with the toolkit and the integrate part...so i was wondering if there's a website or something where i can find some cool and useful registry tweaks and custom windows features to integrate, mostly because i can't do scripts by myself.
Thank you.

MSMG · May 19, 2020

Code:
set "DVD=%~dp0DVD"
set "BIOSBoot=%DVD%\boot\etfsboot.com"
set "UEFIBoot=%DVD%\efi\microsoft\boot\efisys.bin"
set "ISOLabel=W10PRO"
set "ISOFileName=en_Windows_10_pro_x64"
Code:
Oscdimg -bootdata:2#p0,e,b"%BIOSBoot%"#pEF,e,b"%UEFIBoot%" -o -h -m -u2 -udfver102 -l"%ISOLabel%" "%DVD%" "%ISO%\%ISOFileName%.iso"
ceo54 said: ↑
@MSMG bud will it be possible for you to share the command toolkit uses to create the ISO with Oscdimg ?

I have the command but mine doesn't adapt to dynamic paths and neither has the ability to set the Wim name and filename on the fly like yours does. Also I would like to see what optimisation switches you're using. Yours is the best.
Code:
oscdimg -m -o -u2 -us -udfver102 -bootdata:2#p0,e,bd:\iso_files\boot\etfsboot.com#pEF,e,bd:\iso_files\efi\microsoft\boot\efisys.bin d:\iso_files d:\Win_8.1_Pro.iso
Click to expand...

MSMG · May 19, 2020

Don't use that it won't work, I had posted another method later check this post

https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-761#post-1597447
marioalpha said: ↑
this does not return any packages
Code:
Get-AppxPackage *Microsoft.PPIProjection_cw5n1h2txyewy*
I think we should write
Code:
Get-AppxPackage *Microsoft.PPIProjection*
However it wouldn't work, there are apps that we strongly advise against uninstalling.
Click to expand...

mhussain · May 19, 2020

hey @MSMG,
remove apps.txt
where do i get the list of apps that is removable from the image?
like the connect app?
i'm discussing the system apps etc,
Majid

MSMG · May 19, 2020

This method is removing Windows Apps using the DISM /Remove-ProvisionedAppxPackage, it won't work for System Apps.

For System Apps which have Package names, you can use DISM /Remove-Package method but it requires modifying few registry keys before running the command.

The current Toolkit component removal (ToolKitHelper.exe) don't use these two above methods but instead uses the manual method.

mhussain said: ↑

hey @MSMG,
remove apps.txt
where do i get the list of apps that is removable from the image?
like the connect app?
i'm discussing the system apps etc,
Majid
Click to expand...

aruiz · May 19, 2020

MSMG said: ↑

Did you used Start.cmd to run the Toolkit?
Click to expand...

Yes, I always used start.cmd

Ace2 · May 19, 2020

MSMG said: ↑

Ok try this

First run these commands in the command prompt

Code:

reg load HKLM\test C:\Windows\System32\Config\SOFTWARE
reg add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f
reg unload HKLM\test

Then run the below command in command prompt to remove the Connect App.

Code:

Dism /Online /Remove-Package /PackageName:Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.18362.1

If your OS version is different then change the version in the above commands.

PS: In W10 v2004 the Connect App is not present.

Click to expand...

Windows-Defender.cmd

Code:

@Echo Off

reg load HKLM\S C:\mount\Windows\System32\Config\SOFTWARE

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f
reg add "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f
reg delete "HKLM\S\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f

reg unload HKLM\S
Pause

dism /image:C:\mount /Remove-Package /PackageName:Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~~10.0.18362.1
dism /image:C:\mount /Remove-Package /PackageName:Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1
dism /image:C:\mount /Remove-Package /PackageName:Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.18362.1
dism /image:C:\mount /Remove-Package /PackageName:Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.18362.1
dism /image:C:\mount /Remove-Package /PackageName:Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.18362.1
Pause

@MSMG thanks for posting these commands, now i can replace install-wim-tweak.exe with dism. :cool:

marioalpha · May 19, 2020

I have tried and tried many times, but I can't do step 6> 1
when adding updates i always get errors with sfc / scannow.

MSMG ToolKit : 9.9 with ToolKitHelper.exe 1.0.3132.0

x64 ISO : 18363.418.CCCOMA_X64FRE_IT-IT_DV9.ISO

x64 SSU : windows10.0-kb4552152-x64_705fda69935538eab5054d9d616e1761742816ec.msu

x64 CU : windows10.0-kb4556799-x64_9de920d8738612baa81a751b003ff98f0ce7156b.msu

x64 FlPlayer : AMD64-all-windows10.0-kb4537759-x64_ea293539b86301f3c89abbae0d4cc70060d00848.msu

x64 NetCU : windows10.0-kb4552931-x64_2db4f6d9a62833406875986aae69351f82f3ca2b.msu

Extract ISO (1 > 3)
Select source (1 > 1) (only mount image)
Apply updates (3 > 4 > Y > 2 > 1 > 2)
Cleanup (6 > 1)
Apply changes to image (6 > 2 > Y)
Rebuild (6 > 1)
Make ISO (7 > 1)

I still don't understand where I'm wrong

MSMG · May 19, 2020

Then check if there is any AV interference with the Toolkit or Mount Directory.

or

aruiz said: ↑

Yes, I always used start.cmd
Click to expand...

MSMG · May 19, 2020

Welcome, the credit goes to MDL user lite8 for providing this trick.
Ace2 said: ↑
Windows-Defender.cmd
Code:
[USER=231182]@MSMG[/USER] thanks for posting these commands, now i can replace install-wim-tweak.exe with dism.:cool:[/QUOTE]
Click to expand...

MSMG · May 19, 2020

Check skipping the cleanup step and see if SFC error occurs, in many previous CU's there were SFC scan bugs which were fixed at some point.

marioalpha said: ↑

I have tried and tried many times, but I can't do step 6> 1
when adding updates i always get errors with sfc / scannow.

MSMG ToolKit : 9.9 with ToolKitHelper.exe 1.0.3132.0

x64 ISO : 18363.418.CCCOMA_X64FRE_IT-IT_DV9.ISO

x64 SSU : windows10.0-kb4552152-x64_705fda69935538eab5054d9d616e1761742816ec.msu

x64 CU : windows10.0-kb4556799-x64_9de920d8738612baa81a751b003ff98f0ce7156b.msu

x64 FlPlayer : AMD64-all-windows10.0-kb4537759-x64_ea293539b86301f3c89abbae0d4cc70060d00848.msu

x64 NetCU : windows10.0-kb4552931-x64_2db4f6d9a62833406875986aae69351f82f3ca2b.msu

Extract ISO (1 > 3)
Select source (1 > 1) (only mount image)
Apply updates (3 > 4 > Y > 2 > 1 > 2)
Cleanup (6 > 1)
Apply changes to image (6 > 2 > Y)
Rebuild (6 > 1)
Make ISO (7 > 1)

I still don't understand where I'm wrong
Click to expand...

Windows 10 User · May 19, 2020

MSMG said: ↑

Yes remaining components will be removable, I have already added the support for removing cortana app, it needs further tweaking to fix the start-menu search but the explorer search is working fine.

If you want an easy fix then use the Remove Apps using Apps List method and add the below entry to RemoveAppsList.txt file

Microsoft.549981C3F5F10
Click to expand...

Thanks. After removing the Cortana with NTLite some items showed up with the wrong icons in the Start Menu search and after typing some words I got no results.

marioalpha · May 19, 2020

MSMG said: ↑

Check skipping the cleanup step and see if SFC error occurs, in many previous CU's there were SFC scan bugs which were fixed at some point.
Click to expand...

if skipping the cleanup step i have no errors, this happened to me also with KB4549951

So am I not the one who misses the steps?

I kept doing it because I read many who succeed without problems, how is it possible?

MSMG · May 19, 2020

In v2004 there are no two separate things like Cortana Component and Cortana App, only Cortana App is present.

The ToolKitHelper method used for removing Cortana App needs further tweaking to fix the Start Menu search and that's why I did gave a temporary solution to use DISM's remove provisioned apps command to remove the Cortana App until a fix is implemented in ToolKitHelper.

Windows 10 User said: ↑

Thanks. After removing the Cortana component (not to be confused with the Cortana app) some items showed up with the wrong icons and after typing some words I got no results. I thought one can only have these issues after removing the Cortana component, not the Cortana app.
Click to expand...

MSMG · May 19, 2020

May be the latest CU might have brought back the SFC bug again which the Microsoft had fixed earlier.

marioalpha said: ↑

if skipping the cleanup step i have no errors, this happened to me also with KB4549951

So am I not the one who misses the steps?

I kept doing it because I read many who succeed without problems, how is it possible?
Click to expand...

Windows 10 User · May 19, 2020

MSMG said: ↑

In v2004 there are no two separate things like Cortana Component and Cortana App, only Cortana App is present.

The ToolKitHelper method used for removing Cortana App needs further tweaking to fix the Start Menu search and that's why I did gave a temporary solution to use DISM's remove provisioned apps command to remove the Cortana App until a fix is implemented in ToolKitHelper.
Click to expand...

By using the DISM method to remove the Cortana app would it break the Start Menu search?

MSMG · May 19, 2020

In W10 v2004 the Cortana UI and Search has been separated.

The Search part is now a System App (Microsoft.Windows.Search_cw5n1h2txyewy) and is present in <Windows\SystemApps> folder.

The Cortana App which is the Cortana UI is now normal Provisioned Appx Package (Microsoft.549981C3F5F10) and is present in <Program Files\WindowsApps> folder.

Windows 10 User said: ↑

Weird, because I was able to remove the Cortana component with NTLite and I still had the Cortana app. And by using the DISM method to remove the Cortana app would it break the Start Menu search?
Click to expand...

raptorddd · May 19, 2020

i been away for few months. i was getting power offs randomly i still need to send motherboard to warrantt. so i have no PC LOL. question does using toolkit now still reinstalls rwmoved apps when windows update is used.?

Windows 10 User · May 19, 2020

MSMG said: ↑

In W10 v2004 the Cortana UI and Search has been separated.

The Search part is now a System App (Microsoft.Windows.Search_cw5n1h2txyewy) and is present in <Windows\SystemApps> folder.

The Cortana App which is the Cortana UI is now normal Provisioned Appx Package (Microsoft.549981C3F5F10) and is present in <Program Files\WindowsApps> folder.
Click to expand...

If they're separated in 2004, then why removing Cortana messes up the Start Menu and the Settings app?

MSMG ToolKit

MSMG MDL Developer

GianlukK MDL Novice

MSMG MDL Developer

MSMG MDL Developer

mhussain MDL Member

MSMG MDL Developer

aruiz MDL Novice

Ace2 MDL Addicted

marioalpha MDL Novice

Attached Files:

CBS.txt

MSMG MDL Developer

MSMG MDL Developer

MSMG MDL Developer

Windows 10 User MDL Expert

marioalpha MDL Novice

MSMG MDL Developer

MSMG MDL Developer

Windows 10 User MDL Expert

MSMG MDL Developer

raptorddd MDL Junior Member

Windows 10 User MDL Expert