Windows 10X has sandboxes for everything, there are no exceptions.

This is a path that started when people voted against UWP, then they went the other way around, bringing the UWP sandbox model to Win32.

First there was Desktop Bridge where Win32 apps would run sandboxed, but with full trust. Then came the MSIX package format that would apply a bit more of sandboxing and less trust than Desktop Bridge introduced.

Now with Windows 10X they are building on top of the picoprocesses that came from Project Drawbridge and were used in WSL 1 to wrap each Win32 application into its own little world.

It is only a matter of time until this expands to other SKUs.

As for the legacy applications, I guess just like with those stuck in Windows XP, either adopt the future or stay behind.

> As for the legacy applications, I guess just like with those stuck in Windows XP, either adopt the future or stay behind.

I have a very strong feeling that it will be Windows 10X that will be "left behind". The entire point of using Windows nowadays is to be able to use existing Windows applications.

I don't think so, given I have been following the evolution of Windows sandbox model for a decade now.

Every time there were any issues, it was dealt with one step back two forward tactic.

That tactic only works for as long as nothing breaks. So far the stuff Windows introduced for better security (ie. UAC) very rarely break things both by trying to emulate the older behavior (ie. UAC tries to virtualize writes to Program Files older programs do) and by allowing you to bypass it and just let the program do what it wants (run as Admin, compatibility flags in registry/settings in shortcut, etc). Even when that isn't possible there are often workarounds to make things work.

In general i'm very confident i can make any older program or game for Windows to run on modern Windows 10 - usually with minor tweaks.

If Microsoft breaks this, i'm certain they'll completely misunderstand why people keep using Windows.