Skip Navigation

New Windows driver blocks software from changing default web browser

134 comments
  • I understand that software directly and silently changing the default software can be a security issue. But it's only because it happens silently. Does Windows allow for showing a system prompt that confirms the change to the user? If not, then that's just plain ol' anti-competitive. Especially with how pushy Edge and Bing can be.

    • I don't think the goal is to lock you into their browser, since you still can change it through the GUI. It seems to be part of the recent push to block software which changes hidden settings. The end goal being to lock down the OS and prevent users from disabling features MS wants to push onto them.

  • I've said it before and I'll say it again - Windows isn't ready for the desktop. Just use Linux.

    • @Naich @ardi60 Totally agree.

      I mean, Windows is just such a weird proprietary distro.

      It doesn't use the latest Linux kernel, or even a mainstream POSIX-compliant alternative like BSD. Instead, you have a strange CP/M-like monolithic kernel — I think they used to call it DOS — that's been extended to behave more like VAX and MP/M.

      It also doesn't use either X11 or Wayland as a display manager. Instead, you have an incredibly unintuitive overblown WINE-like subsystem handling the display.

      Because it doesn't use Linux, Wayland, or X11, you are limited in the desktop environment that you can use. There's really limited support for KDE, despite the best efforts of volunteers.

      Instead, there's a buggy and error-prone proprietary window manager that ships with it by default. A bit like how Canonical tried to ship Unity as it's default desktop environment with Ubuntu.

      And confusingly, they've named that window manager Windows as well!

      That window manager lacks many of the features an everyday Gnome or KDE user would expect out of the box.

      It also doesn't ship with a standard package manager, and most of the packages ship as x86 binaries, so installing software works differently to how an everyday Linux user would expect.

      There's also only one company maintaining all of these projects. It insists on closed source, and it has a long history of abandoning its projects.

      And sure, if you're a nerd who's into alternative operating systems, toying with Windows can be fun.

      But if your grandpa is used to Linux, frankly he'll be utterly bamboozled by the Windows experience.

      I'm sorry to be glib, because Windows does have some nice ideas.

      But.

      Windows on the desktop just isn't ready for your average, everyday Linux user.

      Linux #Windows #PC

  • 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.

134 comments