Hi
I have been using PDF XChange viewer for quite some time. I use the portable (free) version running under WinXP Pro, SP3.
Since the last update (version 2.0.54), it has become unusable.
When I run the .exe, the program runs, but is unable to open a(ny) .pdf file. Any subsequent efforts to open / close the program lead to further (new) processes to be added.
When I try to kill the running process (e.g. with Process Explorer), it refuses to die. Worse still, when I shut down my PC, it goes through the motions but cannot shut down completely. Ctrl+ALt+ Del cannot even get me to force a shut down.
I tracked down an earlier version (v. 2.0.53) but now even that is showing the same problem.
Anyone else had this problem? Solutions?
Thanks
PDFXChange process gets stuck in memory - unable to open PDF
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
-
occam
- User
- Posts: 5
- Joined: Sun Aug 22, 2010 7:35 am
-
John - Tracker Supp
- Site Admin
- Posts: 5225
- Joined: Tue Jun 29, 2004 10:34 am
Re: PDFXChange process gets stuck in memory - unable to open PDF
Hi,
To allow us to investigate - could you please send in a report with the Viewer loaded and use the option :
Help -> Report a Problem
as this provides useful system info - please copy and paste your report already provided into the report message for reference and a link to this forum message.
Thankyou
To allow us to investigate - could you please send in a report with the Viewer loaded and use the option :
Help -> Report a Problem
as this provides useful system info - please copy and paste your report already provided into the report message for reference and a link to this forum message.
Thankyou
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
-
occam
- User
- Posts: 5
- Joined: Sun Aug 22, 2010 7:35 am
Re: PDFXChange process gets stuck in memory - unable to open PDF
Hi JohnJohn - Tracker Supp wrote:Hi,
To allow us to investigate - could you please send in a report with the Viewer loaded and use the option :
Help -> Report a Problem
Thanks for the suggestion - however, when I tried to send the report ('Next' button) via Help -> Report, my PC went into a tail spin, as before. (Even my Kaspersky AV was frozen in its tracks as it was updating its database.)
Everytime I try to run PDFXChange, I am now forced to shut down the PC manually, by brute force (i.e. hold down 'Start' button for 6 seconds) - which I am not willing to do any more.
I will track this forum for similar reports and hopefully a solution will surface. In the meantime, I will sideline the use of PDFXChange.
-
occam
- User
- Posts: 5
- Joined: Sun Aug 22, 2010 7:35 am
[SOLUTION]: PDFXChange process gets stuck in memory -
The problem appears to happen if you are also running Kaspersky AV (11.0.1.400, in my case).
Solution - place the application (PDFXCView.exe) as a 'trusted application' under Kaspersky.
('Settings' > 'Threats and Exclusions' > 'Exclusion Settings...' > Browse... )
Hope this can be of help to other KAV users of PDFXChange viewer.
(Problem reported to Kaspersky - not sure if they will react, and how quickly?)
Solution - place the application (PDFXCView.exe) as a 'trusted application' under Kaspersky.
('Settings' > 'Threats and Exclusions' > 'Exclusion Settings...' > Browse... )
Hope this can be of help to other KAV users of PDFXChange viewer.
(Problem reported to Kaspersky - not sure if they will react, and how quickly?)
-
Stefan - PDF-XChange
- Site Admin
- Posts: 19930
- Joined: Mon Jan 12, 2009 8:07 am
Re: PDFXChange process gets stuck in memory - unable to open PDF
Thanks for the solution occam,
I do hope this will help someone else!
We also tried to contact Kaspersky, and only got automated replies
Please let us know if they send you a real answer
Cheers,
Stefan
I do hope this will help someone else!
We also tried to contact Kaspersky, and only got automated replies
Please let us know if they send you a real answer
Cheers,
Stefan