If you are having a problem with PolicyPak File Associations Manager (PPFAM) not working as expected, you may be asked by tech support to "Revert to Legacy File Assoc Method & Features".

This might be required if you are attempting to use PolicyPak File Associations Manager on an older version of Windows 10, say, LTSB or LTSC. You can still get PolicyPak File Associations Manager to work, but you must utilize the Legacy behavior.

First, be sure you are eligible to use this function by copying the latest PolicyPak ADMX files to your Central Store or using PolicyPak Cloud.

Directions for Central Store: https://kb.policypak.com/kb/article/505-troubleshooting-with-admx-files/

Directions for PolicyPak Cloud (if they are not already pre-placed there): https://kb.policypak.com/kb/article/478-14-policypak-cloud-admx-thru-the-cloud/

Then, the setting you should use if directed by support is entitled:

Computer Configuration | Policies | Admin Templates | PolicyPak ADMX Settings | Client-side Extensions | File Associations Manager | Revert to Legacy File Assoc Method & Features and set to Enabled to return back to the legacy behavior.

What does "Revert to Legacy File Assoc Method & Features" mean?

By establishing to use Legacy File Assoc Method & Features the following occurs:

• PolicyPak File Associations Manager policies will ONLY apply on the COMPUTER side. Note: The MMC and/or Cloud editors cannot know you’ve enabled this setting; and as such those editors will still work, but the CSE will then ignore the USER side directives.
• PolicyPak File Associations Manager policies can only take effect on DOMAIN JOINED machines.
• PolicyPak File Associations Manager policies can only take effect when you log out and back in.