(Disclaimer, work for Microsoft - made LuaJIT run on UWP in my free time, this definitely works :) )
[1] - https://docs.microsoft.com/en-us/windows/desktop/api/memorya...
Maybe to limit sandbox attack surface? Or working around KnownDLLs pinning perhaps? But even then, why not provide forwarding stubs instead of forcing all UWP devs to write their own or #ifdef spam? Time constraints before shipping Windows 8?
This style of API churn - not limited to VirtualProtect, and often with only newfangled COM C++/CX bindings for replacement APIs - definitely put me off UWP App dev, and I just don't see what the upside was supposed to be for anyone. Lots of extra work, mostly just to lose functionality.
Fun fact: your UWP app also links in gdi.dll and user32 as well.
Also, I remember deploying some code to a surface Hub, my C# build for that took 40 minutes to an hour. Not fun.
On the other hand, it did make me learn some web development to do UIs.
(Excluding the platform-holder’s own JIT’s, of course.)
DVD players, microwaves, and even game consoles are single-purpose computing devices, designed to do one thing. I'm having a lot of trouble putting iPhones and iPads in that category. As terribly locked down as they are, they're still very much "general purpose".
And BTW, I think Microsoft's goal was quite clearly for UWP to be as locked down as iOS.
I’d only call the last element of that chain “general-purpose” — to me, one requirement for earning that label is the ability to write and compile programs. If I can’t write iOS apps from inside iOS, it isn’t general-purpose.
Among other things UWP didn't allow PAGE_EXECUTE on the memory mapping calls, meaning that JITs were disallowed. That's pretty core to general purpose computing in a real way, IMO.