I can confirm enabling that service completely fixes the problem, without creating any other problem. I used to run a 'workstationized' Windows Server for this purpose, but that's not possible these days, as I need to run a few things that are specific to non-Server IIRC, the only UWP application I had a problem with was Terminal. Off-topic: I'd pay good money for a first-party way to slim down Windows to just the bare essentials, then add things back as needed, with ultra-fine granularity. Now I have yet another seeminly unnecessary service running, but Terminal is working.
I confirm that I was able to prevent the bug by