Hello mate. Dont take those asterisk items in the system apps as a great suggestion by me. In fact i have not a single idea what they do. What i did was to blindly try and remove stuff and test extensively (as much as i could) in the VM. But if you say they can break things i may as well not remove those apps for myself So far i have removed those items and don't see anything broken, but maybe my windows usage is pretty basic
Whitelist? Microsoft.Windows.AssignedAccessLockApp, am I missing something... as far as I know (I may be wrong) but this app's only use is for (locking) one purpose (ie. ATM, roulette) machines ... also Blacklist, Microsoft.Windows.CallingShellAp, System Applications universally safe to remove CallingShellApp (provided no mobile phone will be linked to the device) who in this day and age doesn't link/use their mobile phones on their PC EDIT: actually NO... independent
CallingShellApp - so this is kinda used with Your Phone app? Without that is useless? Microsoft.Windows.AssignedAccessLockApp - i may put this in the blacklist as well, if you say its useless and nothing breaks
latest build 22000.132 has moved Edge regedit location to Spoiler: Microsoft.MicrosoftEdge.Stable_90.0.818.66_neutral__8wekyb3d8bbwe HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Applications\Microsoft.MicrosoftEdge.Stable_90.0.818.66_neutral__8wekyb3d8bbwe
Thank you. I'll quote this in the post. You're recent updates and comprehensive rewrite of the OP to this thread, makes my post is somewhat redundant. I'll keep adding tidbits to it when I have the time.
So I got it automated 100% on LTSC, it works real slick. How do you all handle different versions? (LTSC, 21H1, 11, etc) Different Configuration.json? Different Lists? Thanks
Thanks, I'm only now catching up with the rest of you it would seem. btw, I spotted a small spelling error in the ReadMe: Code: Each version of windows may change the names and entries of it's components. should be Code: Each version of windows may change the names and entries of its components.
And has anyone tested FORCE APPX UNINSTALL by @BAU if after updates the system apps return? I don't mind updates for my personal use but would like to get a Windows 10 ISO with its integrity intact and capable of being updated but without all the bloat to install Windows for others.
Yes, I have (applied to 19041.1052) and it works great! https://forums.mydigitallife.net/th...ows-10-version-1809.78576/page-2#post-1680871 You're motivating me to add a post to the above thread noting possibly unexpected outcomes with the scripts use of wildcards and the suggested blacklist. Here is my suggested correction to the Blacklist: Expand the wildcard name "LockApp" to "Microsoft.LockApp". The short "LockApp" name removes two system apps: "Microsoft.Windows.AssignedAccessLockApp" and "Microsoft.LockApp" also: If you want to disable "Microsoft.MicrosoftEdge", then there is no possible wildcard name expansion of "MicrosoftEdge" that doesn't take out "Microsoft.MicrosoftEdge", "Microsoft.MicrosoftEdgeDevToolsClient" and the UWP Appx: "Microsoft.MicrosoftEdge.Stable_8wekyb3d8bbwe As for the returning system apps, awhile ago I posted scripts to lock and un-lock the System apps registry key. I haven't bothered locking the key on recent builds since the issue seems to have gone away?!. My problem was with updates to build 19041.388. I'm beginning to wonder if the problem was caused by starting from a 19041.388 ESD rather than from 19041.1 and updating forward from there? Have you had "system apps return" problems with recent builds? Do you use something like @KedarWolf 's Guide to build up your images from 19041.1?
the list is just an example, and the edge filter knocking chredge - thats 100% intended but the whole script is just a proof-of-concept that I did not refine further yet (its on my long todo)
... as far as EdgeC (Windows 11) is concerned, thought I'd bring this to your attentiom - @abbodi1406's Post
I haven't tested it. I saw your posts here and I think other people's posts with the same problem on github so I was discouraged from using this method (Optimize-Offline). After I saw this post by @Javanicus and got excited about this other method. I asked in the thread about updates if the system apps return but I didn't get an answer. I always use 19041.1 ISO created with UUP and W10UI script to create my updated ISOs. But for these tests I think I would have to use 19041.1 ISO without any updates and then try to update with Windows Update and see what happens. For my personal use I use NTLite and remove telemetry and Windows Update among other things to totally silence Windows from doing things in the background beyond my control. This approach is easier to implement than the cat-and-mouse game with Microsoft so I went that route first. And also because with this fewer services and scheduled tasks were running in the background, decreasing the use of CPU and RAM in addition to reducing the installation footprint a LOT. I think I have finally managed to get the ideal ISO for my use with NTLite. Now I can turn my attention to a less aggressive and more general-purpose approach You can expect anything from Microsoft I will test it as soon as I can.
I'm getting a "Failed to remove Windows Capabilities" error it'll then clean up and abort. Also it seems to be removing more than what I picked in the lists. I'm supposed to run the populateLists command then add my whitelists and such then run the base script right?
In LTSC (version 1809) there is no problem with system apps returning after installing a CU. This occurs from version 1903 onwards.