A default app is the program that Windows assigns to automatically open a specific file or link type when you access it. In Windows 11, you can import default app associations for new users to ensure uniformity. This feature is helpful in enterprise environments, educational institutions, and similar settings.
This article explains the different ways to export and import custom default app associations for new users in Windows 11 and discuss other useful information you may need to maximize functionality.
Best methods for exporting and importing custom default app associations for new users
You can export and import custom default app associations using DISM (Deployment Image Servicing and Management), Group Policy, Registry configuration, and PowerShell automation. These methods differ in difficulty and use, so there’s one bound to be more apt than the others in specific situations.
📌 Prerequisites:
- Windows 11
- Administrator rights
- Familiarity with system settings, command-line interfaces, and Group Policy is beneficial.
📌 Recommended deployment strategies:
Click to Choose a Method | 💻 Best for Individual Users | 💻💻💻 Best for Enterprises |
| Method 1: Export, import, and remove using DISM | ✓ | |
| Method 2: Configuring via Group Policy | ✓ | |
| Method 3: PowerShell automation | ✓ |
Method 1: Export, import, and remove using DISM
You can use DISM, a command-line tool built into Windows, to export, import, and remove custom default app associations. This method is relatively advanced and requires more know-how, but it’s still the easiest way to manage default apps.
📌 Use Cases: Individual users looking to export, import, and/or remove custom default app associations on their desktops
Exporting custom default app associations
- Choose your preferred default apps, as they will be the exported apps.
- Press the Windows key, type cmd, and click Run as administrator.
- Click Yes if prompted.
- Copy and paste the command below into the command prompt, then press Enter:
dism /online /Export-DefaultAppAssociations:”
%UserProfile%\Desktop\MyDefaultAppAssociations.xml”
- Go to your desktop. There should be a file there called MyDefaultAppAssociations.xml.
Importing custom default app associations
- Copy the exported MyDefaultAppAssociations.xml file to your desktop.
- Press the Windows key, type cmd, and press Run as administrator.
- Copy and paste the command below into the prompt, then press Enter:
dism /online /Import-DefaultAppAssociations:”
%UserProfile%\Desktop\MyDefaultAppAssociations.xml”
Removing custom default app associations
- Press the Windows key, type cmd, and press Run as administrator.
- Copy and paste the command below into the prompt, then press Enter:
Dism.exe /Online /Remove-DefaultAppAssociations
💡 Notes:
- This removes the custom default app associations you imported. Once removed, the system will use Windows’ default app associations instead of your custom default apps.
- These changes apply to new user profiles created after the import. Existing profiles won’t be affected.
⚠️ Warning: Conflicts with Group Policy could override associations applied with DISM. (For more info, refer to: Things to look out for)
Method 2: Configuring via Group Policy
IT administrators can use Group Policy to enforce default app associations across multiple machines in a domain. This method is beneficial if you’re looking for uniformity across different endpoints.
📌 Use Cases: IT administrators looking to enforce default app associations across multiple endpoints
- Store the exported XML file in a shared network location accessible by all target machines.
- Open the Group Policy Management Console on a domain controller.
- Navigate to: Computer Configuration > Administrative Templates > Windows Components > File Explorer
- Double-click Set a default associations configuration file.
- Enable the policy and specify the UNC (Universal Naming Convention) path to the XML file (e.g., \\Server\Share\DefaultAppAssociations.xml).
- Apply the policy to the desired machines.
💡 Note: This policy applies the specified default associations at user logon. Users can change their default apps, but the policy will reapply at the next logon unless the “Suggested” attribute is used in the XML.
Method 3: PowerShell automation
You can use PowerShell to automate the configuration of default applications on Windows devices. This method is scalable, consistent, and efficient in managed environments.
📌 Use Cases: IT administrators looking to enforce consistency across devices in an enterprise environment
- Press the Windows key, type PowerShell, right-click the app, and click Run as administrator.
- Copy and paste the script below, then press Enter:
Start-Process -FilePath “dism.exe” -ArgumentList “/online /Import-DefaultAppAssociations:C:\DefaultAppAssociations.xml” -Verb RunAs
⚠️ Things to look out for
Risks | Potential Consequences | Reversals |
| Malformed XML file | Default app associations aren’t applied to new users. | Use XML validators to verify the structure before deployment or test it on a staging machine first. |
| Group Policy conflicts | Imported default app associations are ignored or overwritten. | Review Group Policy settings and deployment order. |
| Forcing defaults against user preferences. | Users won’t be able to use preferred apps as defaults, degrading the user experience. | Use XML’s Suggested=”true” attribute to allow users to override or communicate the changes through documentation. |
| Failure to target new user profiles | Inconsistent experience across profiles or devices. | Use Group Policy to automate and enforce the setting at each login if needed. |
Additional information regarding managing custom default app associations
The following information will help you manage custom default app associations more effectively.
Versioning and Suggested attributes
You can use the Version and Suggestion attributes in the XML file to control how and when associations are applied. Increasing the Version value can reapply associations, while setting Suggested to “true” only applies the association once per version.
Do this when you want to propose defaults without locking them in, allowing for user flexibility.
Deployment scenarios
Imaging: You can include the import command in deployment scripts to apply associations during system setup. Do so using tools like MDT (Microsoft Deployment Toolkit), SCCM (System Center Configuration Manager), or third-party imaging software during system provisioning. This method ensures all systems are initialized with consistent default apps.
Intune: You can use configuration profiles to deploy the XML file to managed devices. Do so by using a custom OMA-URI or PowerShell script. You can also copy the XML to a known location and run a script via Intune or NinjaOne.
Leverage the power of NinjaOne’s software deployment to systematically install software on endpoint devices. Read how Ninja’s software deployment system works
User experience
Note that enforcing default app associations can override user preferences. Before implementing these configurations, consider organizational policies and user needs.
Troubleshooting common custom default app association issues
If the custom default app associations aren’t working for new users, you can troubleshoot the issue by referring to the information below.
Associations are not applying
- A common reason default app associations don’t apply properly is a malformed XML file. It’s crucial to verify if the file is structured correctly and doesn’t have missing tags. Use schema tools or XML validators to identify and correct formatting issues before deployment.
- Similarly, a failure in the DISM process may result in unapplied associations. Try to execute the command with administrator privileges first. If that doesn’t work, check the DISM log located at C:\Windows\Logs\DISM\ to get a detailed insight into the errors.
- File accessibility also plays a key part in the exporting and importing process. The XML file should be accessible on the local system. Network paths can be problematic if they’re improperly mapped or user permissions are insufficient.
- Lastly, conflicts with Group Policy could override associations applied with DISM. Review and adjust these policies if needed to prevent them from negating custom configurations.
Users are unable to change defaults
- Review Group Policy settings to determine if user changes are being overridden at logon.
- Consider using the Suggested attribute to allow user customization after initial application.
Ensure consistency by customizing default app associations for new users in Windows 11
Managing default app associations in Windows 11 provides a consistent user experience and aligns with organizational standards. Utilize DISM, Group Policies, and PowerShell to efficiently configure and deploy custom default app associations across multiple devices.
Related articles:
