For historical reasons, the pdf printer in our Windows 7 x64 enviroment is named "PDF". Starting with the PDF-XChange PRO 6.0.317 x64 MSI package, a custom named pdf printer doesn't get removed if PDFX gets uninstalled. It works fine with the PDF-XChange PRO 5.5.315 x64 MSI package.
This is especially annoying since a GPO deployed PDF-XChange PRO MSI package, scheduled for reinstallation (upgrade/changed settings etc.), fails to install due to a already existing pdf printer with the same name.
This issue can be reproduced using the following config file and install string:
Thanks for the feedback mkr. I'm sorry to hear that you are seeing this issue.
We are going to need a log of the install that failed. Can you log this and send us the log file to firstname.lastname@example.org with a cross reference to this forum thread so we know what it's about please?
Meanwhile, we will attempt to reproduce the issue here.
If posting files to this forum - you must archive the files to a ZIP, RAR or 7z file or they will not be uploaded - thank you.
I have used the following wmic command to delete a custom named printer. In this case the printer was renamed "PDF-XChange Customized". The command requires admin privileges and I found it very effective when pushed through a Group Policy:
Unfortunately not. I mean, the problem is that a re-installation fails because of an existing pdf printer which wasn't removed during uninstall. Running WMI queries (maybe as custom msi actions) might work but isn't more than I hack.
I consider this as an error of the installer. Even the latests PDF-XChange PRO 6.0.319.0 installer has this bug. It allows to create an custom named printer but fails to remove the very same printer on uninstall.
I'm really not in the position to say what tracker software should do but I would strongly suggest to either remove support for the PNAME property or fix the (un)installer.