MSMG ToolKit

Or how about people stop assuming stuff and just go about their day while checking back from time to time? It's almost like people feel obligated to F5 refresh the page every 5 seconds and if there's nothing new from OP then the project must surely be dead...

 

I don't see Microsoft.OutlookForWindows or anything with Outlook in the name in any of the DISM templates supplied with the ToolKit.

Perhaps you are referring to a manual method? If so, I think I would rather wait for MSMG to acknowledge support for the removal of the Outlook app, as I'm not confident enough to do it manually, nor am I confident enough that removal of the app will break something - possibly why it's not listed?

 

are you sure it's installed and not a pinned shortcut?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

[4] Customize → [7] Import Custom Registry Setting from Registry File

Code:

Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\CrossDeviceUpdate]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\DevHomeUpdate]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\OutlookUpdate]

 

You need to login to view this posts content.

 

Yes, kind of manual.
The Removal Method by lists are present since.............................

You can add the Appx in the RemoveAppsList.txt

And remove by the proper Remove Menu Option.

Some of the sugested apps are for the new 26100, but if it is in the list, and not present in the image, it will don't remove anything.
So meke your list and meke the tests. No harm if you make the tests in VMs.

 

I normally use the RemovePkgslist.txt to remove apps, but with 13.7 and 23H2 I'm getting this message "The selected source does not support custom component removal, however is supports DISM component removal"
Should I proceed or get a new source image? I used 22631.3235 from uupdump (told it to include updates and cleanup components - maybe I should change those options?)

 

@miketunes For 22631.3672 you can use manual component removal, it works.

 

You need to login to view this posts content.

 

@Feartamixg
try the file names you mentioned put both of them in the list there's no harm in that,
i'm not on 11,
i'm on iot enterprise ltsc 2021 currently

 

Is there a build that I can still use the RemovePkgslist.txt for?

 

The one mentioned in changelog(most likely).

 

For the DISM list you can manually add it and it will work. I'm not sure how to add it to the Toolkit list, I'm still experimenting with the new toolkit entries trying to figure out what is safe to remove or not. I may try running both removal methods just to see what will happen. I am very glad to have this back.

 

For new apps like a Store Microsoft.OutlookForWindows you just use RemoveAppslist.txt, not RemovePkgslist.txt.
See the names difference?

The other System apps should be removed with RemovePkgslist.txt. But It needs to be fixed in one thing, needs to remove the PackageBuild.1 (22621.1) package to remove other lang or updated files like PackageBuild.3672 Package Build (22621.3672), not Build (22631).
It is kind a tricky, but is in that way.
About the issues after 3672, it is new to me.
I made tests with my changes to remove with 26100 and every thing is fine.
I dont know whats goin on with 3235, I think as it is older maybe some issue with that CU.

 

You need to login to view this posts content.

 

@Feartamixg,
Why do you need to integrate Outlook (and other Apps) when using uupdump script, and then at the next stage look for ways to remove it (them) using Toolkit? Wouldn't it be easier in the case of obtaining an ISO with uupdump, to immediately avoid integrating it into the image using the settings CustomAppsList.txt (supported only in builds 22563 and later.)? Just take the trouble to read what's written there and set it up as you need it. The names of Store Apps that you don't need should be preceded by a # prefix, in your case:

Code:

# Microsoft.OutlookForWindows_8wekyb3d8bbwe

(By analogy, you need to do the same with all the Apps you don’t need)

To use CustomAppsList.txt at the stage of converting UUP to ISO, the Store Apps settings in ConvertConfig.ini should be as follows:

Code:

[Store_Apps]
SkipApps     =0
AppsLevel    =0
StubAppsFull =0
CustomList   =1

Or if you don't need Store Apps together with the Store at all, you can use this setting:

Code:

[Store_Apps]
SkipApps     =1
AppsLevel    =0
StubAppsFull =0
CustomList   =0

 

More than an user, he is a tester.
Every time he brings to us the tests results.


And it is just as important as your solution to prevent the integration of an app through the convert-UUP list.

Even though I use the non-integration of components by convert-UUP a lot, sometimes I don't realize that there are problems when removing something.

 

The latest release works great. I've used it to integrate drivers, and remove packages from the 22631.3447 build. Afterwards, I used AME Wizard to apply the AtlasOS Playbook. From 145 processes and 3.3 GB of RAM usage down to 75 processes and 2.6 GB RAM usage. Thanks for the new update!