Set Foxit as Default PDF Viewer in Microsoft Edge

Some users have issues with default PDF viewer settings. Despite choosing Foxit or Adobe as the default, the system keeps reverting to Microsoft Edge. The issue persists even after repairing Edge or downgrading Foxit. The problem is specifically observed when trying to set the default from within the PDF programs.

Method 1:

• Right-click on the PDF document
• select "Open with" -> "Choose another app" in the right-click menu
• select Foxit PDF Editor, check "Always use this app to open .pdf files"
• click OK.

Method 2:

• Click the "Start" button on your desktop, then select "Settings".
• In the pop-up window, select "Apps".
• In the left-hand menu, choose "Default apps".
• In the list on the right, find and click on the ".pdf" file type.
• In the pop-up window, choose the application you want to set, such as Foxit PDF Editor.

Method 3:

• Find your PDF file, right-click and select "Properties".
• In the pop-up window, choose "Opens with".
• Click the "Change" button, then choose the application you want to set from the list, such as Foxit PDF Editor.
• Confirm your choice, then click the "Apply" and "OK" buttons.

Method 4:

• If you've already opened a PDF file Foxit PDF Editor, click the "Help" menu
• Click “Set to Default PDF Reader”.

The verification results are as follows:

• Among the above methods, only Method 1 can change the default application for .pdf files, but it will reset to Edge after rebooting;
• The changes made in other methods will not take effect.

The Windows system has updated the UCPD service driver, which now restricts modifications to the associated .pdf application. This change was a result of Microsoft implementing a driver-based protection system. This new system prevents third-party utilities from modifying http/https and .pdf associations.

By default, Microsoft enables this service driver and places it in the system's task scheduler to initiate at start-up. This creates an issue where if the UCPD service driver is running, the new version cannot be successfully set after our new version is distributed.

However, there is a potential solution. As a system administrator, it is possible to disable the UCPD operation. This solution is effective for all users in the domain. Thus, disabling or even removing system driver services can be a viable option to resolve this issue.

Step-1: Prepare a XML file named "DefaultAppAssociations_pdf.xml" with content as below:

<?xml version="1.0" encoding="UTF-8"?>  <DefaultAssociations>    <Association Identifier=".pdf" ProgId="FoxitPhantomPDF.Document" ApplicationName="Foxit PDF Editor" />  </DefaultAssociations>

<?xml version="1.0" encoding="UTF-8"?>  <DefaultAssociations>    <Association Identifier=".pdf" ProgId="FoxitReader.Document" ApplicationName="Foxit PDF Reader" />  </DefaultAssociations>

Step-2: Modify registry, via Registry Editor (suitable for individual user) or via GPO policy (suitable for enterprise user).

Via Registry Editor (suitable for individual user)

1. Place the XML file in your PC, for example, C:\DefaultAppAssociations_pdf.xml.
2. Open "Registry Editor". You can press Windows and R key and then enter regedit.
3. Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System.
4. Add a new String value:
   For the new string value, please set the name with "DefaultAssociationsConfiguration", and set the data with full path of that XML file. For example:
   
5. Restart the system.

Via GPO Policy (suitable for enterprise user)

You can also enforce the file type via GPO policies. Using Group policy, admins can force file associations each time a user logs in. This way, even if a user changes the default PDF handler in a particular session or an OS update changes it, the next time the user logs in, it will be changed back to what the admin has specified.

After you prepare the XML file as mentioned in Step-1:

1. Place the XML on a shared network location or push this XML to all your machine-specific locations via a script. For example, C:\Windows\System32 (do not use a user-specific location).
2. Set the XML configured with your preferences in a Windows Group Policy setting, and enable the setting as follows:
   1. Open up the Control Panel\System and Security\Administrative Tools\Group Policy Management on your Active Directory Server instance.
   2. Locate the policy under Computer Configuration\Administrative Templates\Windows Components\File Explorer\Set a default associations configuration file. This policy specifies the path for the XML file, which can be stored either on the client machine or at a network location. This is a machine-level policy and it is not possible to create a user-level policy.
   3. Enable the policy, and specify the location where you have stored the XML file. The corresponding registry entry is HKLM\Software\Policies\Microsoft\Windows\System\DefaultAssociationsConfiguration

Once finished, the register setting in "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System" would be like:

Limitations:

• The end user machine needs to be domain-joined for this method to work.
• Users can change the file associations during the current session. However, admin settings are reinstated at next logon.
• As of 5th Feb 2016, it is a known limitation of Windows 10 that when new user is created on the machine after enforcing the GPO Policy, then on first login ownership is not set. However, the correct settings are applied on subsequent logins.

• https://kolbi.cz/blog/2024/04/03/userchoice-protection-driver-ucpd-sys/
• https://www.elevenforum.com/t/enable-or-disable-userchoice-protection-driver-ucpd-in-windows-11-and-10.24267/
• https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/pdfviewer.html