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.
@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!
Microsoft appear to be migrating .appxbundle files to .msixbundles. I've been installing updates for codecs and the Realtek Audio control with DISM. For example; Code: DISM.exe /Online /Add-ProvisionedAppxPackage /PackagePath:RealtekSemiconductorCorp.RealtekAudioControl_1.51.331.0_neutral_~_dt26b99r8h8gj.AppxBundle /DependencyPackagePath:Microsoft.VCLibs.140.00_14.0.33519.0_x64__8wekyb3d8bbwe.Appx /skiplicense How do I install an .msixbundle? Unless I missed something, toolkit doesn't seem to make any distinction?
The changelog says Win11 23H2 is supported, I thought that was build 22631.3235. What is the final 23H2 build number?
i don't such thing will be needed it will not auto start, until you enable it and with bio lock like finger ... so .. and also once you disable AI feature it also disable.
I believe it will, also haven't looked into latest 11 release but it maybe as simple as removing few packages using for example cbsenum to make recall dissappear. also im on win11 22h2 which works great from it will be moving to win 11 iot ltsc no ai and bloat likely recall aint included either
Use dism++ to do sxs etc cleaning. That's what I been using for ages, Also before cleaning run dism scanhealth and sfc scannow so you know if there aren't any errors already.
MS reversed the decision, that this feature should be enabled by default. With the controversy generated, I believe that this feature will become available, but disabled by default. The same should happen with Copilot. Supposedly, I think this is why 26100.712 update isn't available anymore.