Follow

Saving/Set User Windows 10 Default Applications/File Associations

Product: ProfileUnity

Product Version: 6.5.x

Expires on: 365 days from publish date

Updated: August 29, 2017

 

Problem:

Windows 10 ignores the file association settings that are set in the registry

Symptoms:

After a user logs into a Windows 10 desktop, Default applications will be reset to Windows defaults (e.g. such as Acrobat or Chrome back to Microsoft Edge). The Windows 10 Action Center may also show many notifications saying the file extensions are reset.

Possible Resolution(s): 

Note:The following settings have been included in ProfileUnity 6.7 configuration Templates.

To save the Default App settings that a user has chosen, additional rules will need to be added to export/save and import the user's choices.

Step 1) In the Portability Management page create a new portability rule set:

  • Name:
    Windows 10 File Assoc
  • Registry Rules:
    None
  • File System Rules: 
    • Operation: Merge
    • Folder: User Profile
    • Path: AppAssoc.xml
    • Click on Add then click on Save.

Edit the configuration that is used with your Windows 10 machines.

Step 2) Add a Portability Settings Rule:

  • Select Portability Settings and Add Portability Settings Rule
  • Set and save the rule as follows:
    • Filter: Windows 10
    • Actions: Save, Restore
    • Ruleset: Windows 10 File Assoc
    • Advanced Options: Apply Filesystem Rules
    • Save Path: \\Server\Share\%username%\Portability\Win10 (This should match the save path for your existing portability rules.)

Step 3) To Export the File Association settings create 2 "User Defined Script" rules:

A) To Delete the file association (from previous logon):

  • Select User Defined Script and Add User Defined Script Rule
  • Set and save the rule as follows:
    • Description: Export File Assoc
    • Execute: Before ProfileUnity at Logoff
    • Type: Executable
    • File: %systemroot%\system32\cmd.exe /c attrib -H "%USERPROFILE%\AppAssoc.xml" && del /q/f "%USERPROFILE%\AppAssoc.xml"  >> "%temp%\AppAssoc.log"

B) To export the file association settings add another rule to run after rule above:

  • Select User Defined Script and Add User Defined Script Rule
  • Set and save the rule as follows:
    • Description: Export File Assoc
    • Execute: Before ProfileUnity at Logoff
    • Type: Executable
    • File: %systemroot%\sysnative\cmd.exe /c Dism.exe /online /Export-DefaultAppAssociations:"%USERPROFILE%\AppAssoc.xml"  >> "%temp%\AppAssoc.log"

Step 4)  To import and set the settings upon logon create 2 "Application Launcher" rules:

  • Select Application Launcher and Add Application Launcher Rule
  • Set and save the rule as follows:
    • Filter: Windows 10
    • Description: AppDefaults Restore
    • Filespec: %systemroot%\system32\cmd.exe
    • Arguments: /c Dism.exe /Online /Import-DefaultAppAssociations:"%USERPROFILE%\AppAssoc.xml" >> "%temp%\AppAssoc.log"
    • Timing: During Configuration Execution
    • Hide Progress During Execution Checked
  • Add another Application Launcher rule as follows:
    • Description: Hide Default File Assoc XML
    • Filespec: attrib.exe
    • Arguments: +H "%USERPROFILE%\AppAssoc.xml"
    • Timing: After Configuration Execution
    • Hide Progress During Execution Checked

After the additional rules have been created, update and deploy the configuration ini file.

Note: Following rules will be added to future default templates of ProfileUnity. 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.