Problem:
Applications often create directories in 'C:\Windows\installer' which is excluded from capturing within newer releases of ProfileUnity FlexApp. These directories sometimes contain icon files (.ico) that are referenced in registry values related to the application. If these registry values reference an icon file that no longer exists, a generic blank icon is used for the specific file types which said registry values reference. In this scenario, PDF files (.pdf) do not display the typical Adobe icon but a generic file icon.
Solution:
To address this issue for PDF files, please reference the example below, editing the registry value shown for the Adobe Acrobat package via the FlexApp Packaging Console Editor.
- Key: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Acrobat.Document.DC\DefaultIcon
- Value: (Default)
- Data: C:\Windows\Installer\{AC76BA86-1033-FFFF-7760-BC15014EA700}\_PDFFile.ico,0
Change the 'Data' string present in the '(Default)' value from the one above to the one shown below, modifying the path and executable name based on the version and bit architecture of your Adobe Acrobat package.
- Data: C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe,1
Once the string has been modified, save the updated package, publish it in a configuration, and deploy the updated configuration INI.
Note: This KB addresses PDF files specifically but there are other registry values under the 'HKLM\SOFTWARE\Classes' key that relate to Adobe Acrobat. If you experience icon issues with other file types related to Adobe Acrobat other than PDFs, the process outlined above can be applied to the other registry keys, referencing the respective executable and icon index.
Product: FlexApp
Product Version: 6.8.4 R2