Overclock.net - An Overclocking Community - View Single Post - [Various] [Updated] Microsoft Broke Windows 10’s File Associations With a Botched Update

View Single Post
post #15 of (permalink) Old 11-08-2018, 06:28 AM
New to Overclock.net
Ghilly's Avatar
Join Date: Jan 2011
Location: Lancashire Chorley, Uk
Posts: 305
Rep: 8 (Unique: 8)
This is an intended feature to prevent browser and app hijacking . the registry will detect changes to default apps and switch them back if not changed in the correct way . I have been deploying default apps to all my 20 + sites without issue. Windows 10 changed the way you deploy default apps from group policy to the use of default appassociation.xml

Best practice ---- >https://blogs.technet.microsoft.com/...s-for-it-pros/

i know this applies to the Professional /domain environment but its still relevant for home PC's as you could deploy this via gpedit.msc

snippet from the MS article into the reasons for the change

"There were different ways and guidance to set default program prior to Windows 10 (see Managing Default Applications).

Before Windows 10, an application could check default apps, ask for user consent and set default app programmatically using Windows API.

But some programs skip the user consent and set the app defaults into the registry. The main requirement for default file association is often forgotten: the end-user is in control.

Now in Windows 10 checks if registry file extension keys have not been modified to prevent file association hijacking"

Last edited by Ghilly; 11-08-2018 at 06:33 AM.
Ghilly is offline