Yeah, it’s a great controller overall but the lack of the second analog stick breaks it for a lot of games. It probably is the best one to use for games that don’t really support controllers in the first place.

As far as I know there is no mandatory DRM on Steam either, so if a publisher wants to they can just make their game be portable and not require Steam to even be installed. Pretty sure all the re-releases that use DOSBox or ScummVM are like this, for example.

Don’t hold your breath, 10 already broke the pattern IMO and all I hear about 12 is that they will cram “AI” into everything. Windows the operating system is dead, replaced by Windows the sales platform.

To anyone saying “just use GPOs”, here’s a quote from the SetUserFTA page:

Microsoft offers a solution with GPO, but it is Computer-based and not User-based – and rather complicated. this means, you can not associate your Users on the same Server/Client with different file types. for example:

you have a PDF viewer and a PDF editing software on your XenApp server. Now you want that a certain group opens their PDF’s in the editor and the others only in the viewer (for licensing reasons for example). this is NOT possible anymore and Microsoft states “it is by design” and “this is a security measure”.

Said solution:

1. Set up a reference computer
2. Install applications
3. Go to Control Panel\All Control Panel Items\Default Programs and configure default apps associations.
4. Export/import the custom default app association with dism.exe

[…]

As some recommended applications can manage more extensions with each new Windows 10 version available, it’s a good practice to refresh your XML. For example, in Windows 10 1703, Microsoft Edge registers the epub extension. If you’re using an XML file from Windows 10 1607, epub is missing. As a result, you will get an app reset notification for epub.

[…]

Configure a policy for your domain-joined computer: file association will be configured at each logon. User will be able to change file association, but at the next logon file association will be configured using XML file. This policy works only for domain-joined computer.

This is just about the most convoluted, annoying way they could come up with for doing this, doesn’t help people whose machines aren’t part of AD and isn’t scriptable. If they were mainly concerned about security they’d have an option for not allowing the user to change these preferences even temporarily on domain-joined machines.