Windows10 Setting Default App associations with DISM after sysprep not working.

[parsons256]

Hi Everyone

 

I'm wondering if anyone has run into a similar issue and could offer some advice.

The help is much appreciated

 

I am working on creating new Windows10 images for our organization. I am using CopyProfile during sysprep to create a default Windows profile with all our settings. For some reason the default app associations are getting cleared during sysprep. I need to find a way to set them after deployment.

 

I have tried using the DISM command to export my app associations to an .xml before sysprep. and again import them after imaging. I have tried running the DISM import command manually and setting it in Group policy under “Set a default associations config file” . Both do not seem to have any effect on Default application settings.

 

I have also tried manually copying the contents of my DefaultApp.xml export to the OEMDefaultAssociations.xml file under system32. This also does not change anything

 

Thank You

Chris Parsons

[ITJS2015]

If you have applied a gpo with the xml then the reason it may not work is that your user could be a local admin which mean it wont apply as it has a super user.

 

What users are being applied to use this xml

[parsons256]

Hi Thank you for the Reply!

 

For example with no group policy set I ran the following command as an admin user after sysprep and imaging. As far as i know this should take the contents of DefaultAPP.xml and apply these settings to all users.

DISM /online /import-defaultappassociations:C:\defaulapps.xml

 

For some reason these changes are not taking effect.

Here is the contents of my default apps .xml

 

[parsons256]

I was using a GPO for testing as another way to try to apply the settings. When the command is run locally under the local admin account with no group policy applied, it is run from an elevated cmd prompt.