I have noticed a very strange behavior with FTA: when using FTA we can not open PDF files anymore by double-click.
What happens:
I have defined an FTA for PDF files to get opened by Acobat Reader DC. When the user now makes a double-click on a PDF file the Actobat Reader gets triggered and opens itself but does NOT open the PDF file.
But you can go within Acrobat Reader to Files --> Open and then select a PDF to open and it opens. You can also do drag & drop to open a PDF file, that works too ... but not with a double-click.
Acrobat Reader itself seems not to see PDFs associated to itself, because in the top right corner Acrobat itself offers to associate PDF with the program (see screenshot). And if you try to associate you will fail (although it seems to be associated)- the problem remains.
I did a lot of tests:
1. Comparing the output of Dism.exe /online /Export-DefaultAppAssociations:C:\DefaultAssoc.xml with FTA to Acrobat Reader and without (manual association by user): there is no difference, both XML files are identical - without any "Association Identifier=".pdf ..."
2. Comparing Registry settings:
[HKEY_CLASSES_ROOT\.pdf]
@="pdf_auto_file"
"Content Type"="application/pdf"
AND THERE IS THE PROBLEM: In the key [HKEY_CLASSES_ROOT\.pdf] is a default value named "pdf_auto_file". This value breaks everything and it's set by DEMs FTA function.
Removing this value restores the correct functionality: you can reapply the FTA manually to PDF and doing a double-click opens PDF files by Actobat Reader and the Reader recognizes that PDFs are associated to him.
Accepted Solutions
Hi @TomH201110141,
Thank you for the config files.
Can you try setting Arguments to "%1", like this:
When Windows launches the associated executable, it will replace that %1 with the fully-qualified path of the file.
Hi @TomH201110141,
Thank you for the config files.
Can you try setting Arguments to "%1", like this:
When Windows launches the associated executable, it will replace that %1 with the fully-qualified path of the file.