I am encountering a strange issue with a Windows 11 image I am building. I've narrowed down the culprit to being when I run a short script I wrote to remove some of the built-in apps using Remove-AppxPackage -AllUsers. Once I perform this step, I begin seeing File Explorer.exe crash due to faulting module Windows.UI.FileExplorer.dll, but ONLY if I launch it from the pinned taskbar icon, using the computer icon on the desktop, Explorer launches normally. Oddly enough, it seems none of my test users are able to recreate the issue, and with the current published version of the image, if I reset my UPM profile for my domain account, I can no longer reproduce the issue either. However, while troubleshooting this issue I have created other versions of the same image where I can recreate the crash even on a brand new profile, both local and UPM, and I have been able to duplicate it using another domain test account. Has anyone heard of anything like this? Am I going about removing the bloat apps the wrong way perhaps? Hopefully this makes sense, let me know if I need to clarify on anything.

Windows 11 has a lot of AppX packages that are just part of the system itself. Make sure you are being very selective with removing appx packages. Also if you are logged in with a profile that has appx packages defined it will have left over data in it that can interfere, so a new profile starts fresh without the bloat so they should work fine.