Installing upgrade changes my File Association preferences

[asherber]

I have Preferences > File Associations set for PDF-XChange not to be my thumbnail handler, for PDF files because I don't want to see PDF thumbnails.

When I recently installed the 10.6.1.397 update, the installer registered PDF-XChange as my thumbnail handler.

It would be nice if the installer recognized that PDF-XChange had previously been installed and did not change these file association settings.

[Paul - PDF-XChange]

Hi, asherber

it shouldn't actually change that. Did you have to use the Editor preferences to restore the functionality you want?

There is a utility called XCShInfoSetup in C:\Program Files\Tracker Software\Shell Extensions that can be used to set this. I am keen to hear if using that sticks if you set it to "None" in there:

image.png

Though you'll need to wait for the next update to test this...

[asherber]

Hi Paul,

I'm sorry I didn't respond last year; I didn't get an email notification that there was a response to my post.

Every upgrade over the last year has reset this preference, including the recent v11.0.1. I have had to go into Editor Preferences to set Thumbnail Handler to No each time.

When I open the shell extension handler, it has:

image.png

I guess I'll see after the next upgrade whether this has any effect.

Thanks,
Aaron.

[Dimitar - PDF-XChange]

Hello, asherber,

To avoid this the next time you install a new version please choose custom installation and untick the option about setting the PDF Editor as the default PDF application.

Regards.

[asherber]

Hi Dimitar,

But I do want PDF Editor as my default PDF application -- I just don't want it to generate thumbnails. Or are you saying that by unticking this box, the install won't touch any of the relevant registry entries, and it will leave the existing default association intact?

Thanks,
Aaron.

[Daniel - PDF-XChange]

Hello, asherber

Unticking that box should only prevent the Editor from attempting to have itself set as the Default for PDF file types. I don't think it is intended to have an effect on the shell extensions.

As Paul noted, the installer should respect your previous shell extensions configuration, if you are updating the software using either; the Updater tool, or running the corresponding latest version installer directly - (do note running the wrong installer file, for example, installing PRO while Editor is already present, could cause this kind of issue).

If your shell extensions are being reset by this process, we will need you to capture an installation log of the scenario. Our newer installers should do this automatically, but V11 did change the paths for both our installations, and registry keys. As such, I will as that you wait for the next release to come out (11.1.0), and if the same issue happens once again, please check that an installation log exists here on your PC:

• %tmp%
  
  Then search for "MSI*", you should see a few results, sort by date, and locate the most recent one:
  image.png

If that is small enough to email (usually they are) Please email [email protected] - Attach that file, and include a link to this post so we can get started on it promptly.

Kind regards,