Just an FYI...
I used Help|Check for Updates to attempt to update to v2.0.0037 and ended up with a second install. I believe this happened because my initial install was not in the default location of C:\Program Files\Tracker Software\PDF-XChange Viewer which is where the updater installed v2.0.0037. I may have mis-responded to a "where do you want this update installed" prompt though I don't believe one was ever presented. As a precaution I uninstalled both versions then installed v2.0.0037 from a download.
--
BrianG
AutoUpdate installs second instance
Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Paul - PDF-XChange, Vasyl - PDF-XChange, Ivan - Tracker Software, Stefan - PDF-XChange
-
John - Tracker Supp
- Site Admin
- Posts: 5225
- Joined: Tue Jun 29, 2004 10:34 am
Re: AutoUpdate installs second instance
Hi Brian,
could it be that you originally downloaded one of our PDF-XChange driver evaluation products as well as a standalone version?
This would result in a different install location from the standalone install ?
could it be that you originally downloaded one of our PDF-XChange driver evaluation products as well as a standalone version?
This would result in a different install location from the standalone install ?
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.
Best regards
Tracker Support
http://www.tracker-software.com
Best regards
Tracker Support
http://www.tracker-software.com
-
BrianG
- User
- Posts: 83
- Joined: Thu Aug 23, 2007 1:46 pm
Re: AutoUpdate installs second instance
I believe I've only installed standalone versions although it's possible that I may have taken a look at a driver product in the past. My original install of PDF-XChange Viewer was to c:\program files\pdfxcview ( I'm not big on installs being multiple folders deep in the program files folder).
Is there a registry key that the updater looks to for the install location? If so, I'd love to take a look to see if there is something residual there.
Is there a registry key that the updater looks to for the install location? If so, I'd love to take a look to see if there is something residual there.