Be careful with the "debloat" features in scripts like this.
In my experience, aggressively stripping out AppX packages and disabling services often breaks windows update or the Microsoft store in subtle ways that don't manifest until 3-6 months down the line. You'll eventually try to install a feature update, it will fail with a cryptic error code, and you'll realize it's because you removed a dependency that the new update expects to be present.
If you really want a clean windows environment, you are better off getting an IoT enterprise LTSC license. It is boring, stable, has zero bloat and doesn't require hacking the registry to stop candy crush from reinstalling itself.
That said, it feels like a constant arms race. Microsoft introduces a new user-hostile pattern (like making local accounts harder to create), the community builds a workaround and then Microsoft patches the workaround. I am tired of fighting my own OS.
If you really want a clean windows environment, you are better off getting an IoT enterprise LTSC license. It is boring, stable, has zero bloat and doesn't require hacking the registry to stop candy crush from reinstalling itself.
That said, it feels like a constant arms race. Microsoft introduces a new user-hostile pattern (like making local accounts harder to create), the community builds a workaround and then Microsoft patches the workaround. I am tired of fighting my own OS.