Microsoft should make it easy to download, install and update on all non-Enterprise versions of the OS. This will also greatly reduce instances of a random ransomware holding critical data hostage and doing irreparable economic damage to small businesses (as was visible during the WannaCry episode last spring [0]).
[0] https://en.wikipedia.org/wiki/WannaCry_ransomware_attack
I'll take this one step further: Microsoft should make this as easy as "right click > Run in Sandbox". It would make the lives of everyone so much easier.
The alternative is to convince some engineers to create this same feature in their spare time and contribute it for free as a Linux package. Then they can get email about all of the things it doesn't do, and fix bugs in their spare time on a feature that all they see are complaints for. Until they burn out and the repo goes dead for a while and then gets picked up by one of those users who wants the feature to exist, and they make some improvements and get into an argument with another user who forks it and now there are two of them, almost the same but with a few features that are unique to each one. Of course for most of the users they either don't care and load one at random, or they do care and find features from the "other" system they want in the one that is being used. They send mail to the maintainers asking them to copy those features. Which adds more pain as the developers copy each other's features but they put their own special spin on them. This burns out more developers and a third person comes out and writes their own syntactically incompatible version that is functionally identical to the two different 'legacy' versions.
At this point I just pay the man his $100 and appreciate that the people working on the code are on it all day and can spend evenings with their family.
"You told me to use sandbox to be safe, so I wrote critical document X in a sandbox because I want it to be safe, but now that I rebooted I've lost all of my work."
It is an evolution of desktop bridge, appx and msi.
Does it add a simple context menu entry to convert an installer? Bonus points for straight up Install and even more for Run.
I see it's open source, so if it's missing it may be possible to make a distribution of it with those things implemented. Then one could install it and make it a default msi handler.
Edit: from what I see conversion is much more involved. Create a certificate and go through a wizard and fill out some forms. Correct me if the is a quick and easy convert option. Otherwise it's a nice thing that needs more development to be useful for a generic user.
https://blogs.msdn.microsoft.com/sgern/2018/06/18/a-closer-l...
A generic user is supposed to just double click on an *.msix file to get it installed on the Windows Store infrastructure.
This sounds like someone making installer stuff would say. MSI will be supported on modern OSes for much longer than "a few more years".
VB6 apps created in 1998 will be supported until 2025 at least. MSIs will be treated the same.
Also I don't think your parents want to use that particular sandbox. There's no persistence at all: no bookmarks, no cookies, no history, no local documents, ...
That way for your parents they just have to buy the pc, put the usb in and reboot it, and then call you when it's back on so you can remote in and give it a key and finish configuring it for them. I suppose even that might cause issues if you can't teach them or walk them through via facetime how to set the device to boot from the usb instead of the harddrive.
Seriously this is a killer feature needed by everybody. And specially the non-pro users.
Windows SKU has nothing to do with hardware.
https://www.dell.com/en-uk/shop/2-in-1-laptops/new-xps-15-2-...
Actually I can't seem to configure that directly from dell to come with Pro lol. Seems there's a question about that too.
1: https://www.dell.com/en-uk/work/shop/tablets-and-2-in-1-lapt...
2: https://www.dell.com/en-uk/work/shop/laptops/new-xps-15-2-in...