I have seen it uninstall (at partially) and traced it back to the permissions on the registry for Gameservice becoming "corrupted" due to no longer having an associating with the pso2 exe launcher and game.
MS store provides you an 11 gb MSIX file that is UWP with an external launcher packaged inside of it. It goes to the System owned WindowsApps folder.
Once downloaded, the .exe launcher gets unpacked into WindowsApps as oxyna_blahblah and has the same ownership cause of the location being WindowsApps.
It is supposed to use the TrustedInstaller ownership through admin elevation to install the rest of the game in ModifiableWindowsApps folder, which is not owned by System but rather by "Owner" (linked to local admin i think) which will then allow the external launcher to work properly, be able to patch the game, and use windows dependencies properly (cause Windows doesn't allow external launches to download system files). Well from my observational testing, it puts it in Mutable (inside of WindowsApps, the system owned folder), backs it up in MutableBackup, and then uses a shortcut in ModifiableWindowsApps.
Problem that can arise with that is the game has to use it's one time admin elevation permissions to access different system files through the virtualization and (if inheritance is enabled on any of the System owned permissions) starts creating these caches in Local Apps with the wrong permissions, which can then make it back to the registry for those items.
But if it messed it all up, why does it work til you restart? This part I am not 100% sure, but think it is because the ownership of the original oxyna_blahblah file (where the real external launcher was first launched and how MS Sfore knows to find it) got jacked up from the launcher's incorrect use of permissions and installing the game in the wrong location before shortcutting it out to a different location and losing it's association with the MS store and gameservices.
Pretty much a long winded way of saying that the external launched is supposed to install in the ModifiableWindows environment, which has less strict permissions, but through errors in programming (maybe language barriers?) it is installing the whole game in a System protected area, backing it up in a system protected area, and if your computer isn't squeaky clean, losing the proper association through bad permission set up.
That was my discovering during launch week at least, not sure what has changed or what could have been incorrect assumptions, cause I gave up on trying to assist individuals who consistently place the blame on MS while praying to their SEGA shrines in the basement.