Why does the Photo App and Notepad App fail after joining domain?

Question

I am aware there are dozens of topics on this issue, I really need to find why this is happening.

We have a Windows Server 2022 domain with Windows 11 Pro workstations.  Within the last 2 months we've started having random workstation errors.  When attempting to open pictures the with Photos App and text files with Notepad (new version) we get this error: "Package failed updates, dependency or conflict validations".  We have a wide range of PCs and Laptops and they all suffer from this (Dell, HP, MSI, Panasonic, Surface Pros).

We are normally able to fix this, when it occurs, on a per user profile by doing the following:

a. Uninstall photos in the Apps Settings.

b. Run windowsappruntimeinstall-x64.exe (as administrator, & disable antivirus).

c. From Admin Powershell run> Get-AppxPackage -allusers Microsoft.Windows.Photos | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

d. This usually fixes notepad and snipping tool too.  We have used the powershell to fix notepad as well, replacing Photos with Notepad.

e. If we cannot fix notepad, we just uninstall it from the Apps Settings and it defaults to the {better version} old version of Notepad.

Other things we tried without success, however this never hurts.  Should not be necessary on a fresh install.

----------sfc /scannow
----------DISM /Online /Cleanup-Image /CheckHealth
----------DISM /Online /Cleanup-Image /ScanHealth
----------DISM /Online /Cleanup-Image /RestoreHealth

TROUBLESHOOTING: We tried to narrow down the problem.  Fresh installed the latest version of Windows 11 Pro 24H2 (Late January 2025 download).  Joined it to our domain, into an OU without any computer Group Policies, and with a user in the default domain Users folder without any Group Polices assigned to the user.

We still get this problem. Yes, we can now fix it per user, when it happens.  We need a solution on how to stop it from happening.

I have attempted to open a case with Microsoft, OMG!!! They have all paths to support blocked. I'm willing to pay to have this issue fixed and I cannot even get ahold of anyone.  Any suggestions would be greatly appreciated.