Default file associations file ignored

[Sheridan]

We've put a default file associations (xml) file on a shared folder for our test W10 suite to set IE11 as the default browser (or chrome - it doesn matter which!) but this seems to be ignored.

 

Whenever a user clicks a internet shortcut on their shared desktop it simply comes up with the 'How do you want to open this website'

 

Unless we specify the the actual executable for the chosen browser in the path we always get this. I never got the start tiles xml files to work so I'm wondering if this is more of the same?

Edited October 21, 2016 by Sheridan

[mrbios]

Did you happen to fix this?

 

Doing all my testing and setup and have the same problem

[Sheridan]

Did you happen to fix this?

 

Doing all my testing and setup and have the same problem

 

Yes - but its a bit of a cludge like most Windows 10 things. We had to copy the default file associations xml file to the local pc using a script, then set the "Set a default associations configuration file" policy to point to the local file. If you try to point to a share or mapped drive for the xml it doesn't work, which is exactly how the start tile seems to handle it.

[mrbios]

Yes - but its a bit of a cludge like most Windows 10 things. We had to copy the default file associations xml file to the local pc using a script, then set the "Set a default associations configuration file" policy to point to the local file. If you try to point to a share or mapped drive for the xml it doesn't work, which is exactly how the start tile seems to handle it.

 

I've just tried this, set a GPP to copy the default file associations file to the default location that the GP specifies (C:\Windows\System32\default\defaultassociations.xml) and i can see that the file has been correctly copied over, however the policy doesn't appear to be forcing its effect on users.

 

What's really bizarre is that i can run a desktop web shortcut multiple times over and over and 1 in 20 tries will gives me chrome and IE as options to open the program in, while every other time is blank with no options.

[Sheridan]

I've just tried this, set a GPP to copy the default file associations file to the default location that the GP specifies (C:\Windows\System32\default\defaultassociations.xml) and i can see that the file has been correctly copied over, however the policy doesn't appear to be forcing its effect on users.

 

What's really bizarre is that i can run a desktop web shortcut multiple times over and over and 1 in 20 tries will gives me chrome and IE as options to open the program in, while every other time is blank with no options.

 

Ahh I've just double checked, I didn't just copy the file over, I used a batch file on machine startup to import the settings using DISM:

 

dism /online /import-defaultappassociations:\\server\share\defaultassociations.xml

 

Then I used the machine policy to point to c:\windows\system32\defaultassociations.xml for the "Set a default associations configuration file" setting.

 

I tried so many things that I'd forgotten how I got this to work!

[mrbios]

Wohoo, it works, thanks

[Sheridan]

Wohoo, it works, thanks

 

You're welcome, it was a complete pain to get working I admit!

[T_Lister]

Hi Guys,

 

I've had no issue with the xml coming from a share on the server until now. I'm using Mandatory profiles for pupils, and in some schools it has been fine. However where I am now they want MovieMaker installed. I have found the legacy version but this has seemed to set off a series of 'can't set the default'. I've made sure the XML contains all the .mov .mp3 .png etc, about 20 odd defaults. Still not. So I tried the put it on the C drive you've been talking about. Didn't take. Roaming profiles pick up the xml no problem.

 

Help?

[Arthur]

I have found the legacy version but this has seemed to set off a series of 'can't set the default'.

Would it be worth adding the DontShowAssociationsDialogExtensions registry setting mentioned in this thread to your mandatory profile to prevent Movie Maker from trying to change file associations.

 

A lot of old applications don't change the associations correctly and cause Windows 10 to display the reset notification.

[T_Lister]

It would seem I have to DISM export and Import my defaults. That's fixed it.