Forced Exit

[bwelsh_tracker]

I cannot tell if this is a Windows problem or an issue with PDF-Xchange. The issue only happens with PDF-Xchange.

If I leave my computer for any length of time (I'd estimate 10 minutes or more), when I unlock it I am greeted with PDF-Xchange trying to Exit. The only reason it does not do so is because I have files open with unsaved changes. Any idea why this is happening?

[Daniel - PDF-XChange]

Hello, bwelsh_tracker

This would most likely be caused by windows automatically closing apps which are "no longer in use" to save resources which it hibernates. You may want to check your windows configuration and ensure that it only turns your screen off at first, and instead of hibernating after a time, it only goes to "sleep". This mode saves less power, but also should avoid actually "closing" any running apps.

Kind regards,

[bwelsh_tracker]

The PC is NOT hibernating or "sleeping." It remains fully active, with the screensaver running - the screen is not even going off.

[Stefan - PDF-XChange]

Hello bwelsh_tracker,

Could this be happening only with some specific files? (I am thinking of maybe some script in them triggering this.)

Or can you try to run a test with just the Editor opened, with no files loaded inside? Would it then close automatically for you when the Screen Saver activates?

Are you on Windows 10 or 11 and could there be any tools or settings that are e.g. trying to close other products like our own at some time intervals or when the screen saver starts

Kind regards,
Stefan

p.s. - on some further reading - do you go through a Logon screen when you wake your computer from the screen saver?
Would e.g. this help (even if it's a forum for an older version of windows):
https://www.sevenforums.com/general-dis ... ocked.html

[bwelsh_tracker]

Windows 10.

It is not related to specific files.

I am presented with a logon when I clear the screen saver. This is a corporate environment so turning that off is not an option.

There are no settings that I have set to close any apps upon initiation of the screen saver. The only unscheduled closing of apps outside of this PDF XChange issue are from crashes.

I will try a "clean" test as you suggested (PDF Xchange only) the next time M$ forces me to update and restart.

[Paul - PDF-XChange]

Hi, bwelsh_tracker

the next time M$ forces me to update and restart.

Does this explain why the Editor is closing? Was it Windows trying to restart?

At the end of the day, the editor will not send itself a shutdown message unless you tell it to. Something must be sending the Editor the close command - and it sounds to me like a Windows Update may be the culprit.

Have you been postponing the restart perhaps? I am trying to determine if Updates are potentially the cause or if there is some other action/activity going on that would trigger the Editor to close. It clearly is being told to close gracefully else yo would not be prompted to save changed documents.

Something had to send that signal, I am keen to understand if it could have been Windows updates.

Kind regards,
Paul - Tracker Supp

[bwelsh_tracker]

Yes, I postpone updates so that I do not lose work. My job is such that I cannot simply spend 20-30 minutes a day closing all my open items to accommodate Microsoft's ridiculous forced updates.

But I also know that is not the culprit. When I have missed the deadline for the M$ updates in the past, they have NOT waited for user intervention to close open files or Apps. You just lose anything that is open, regardless of whether changes are saved or not.

[Daniel - PDF-XChange]

Hello, bwelsh_tracker

Postponing windows updates, at least in windows 8 and beyond, only works for so long, however windows will try to "politely" restart numerous times before it will perform the forced restart that disregards what is running you speak of.
I expect, if you are delaying updates for more than 30 days, this is what has occurred. Ideally, you will want to ensure that you make time, at least once a month, to update windows manually, so that it does not try to restart when you are not looking.

Please do install your pending windows updates, and see if that prevents the issue from happening further for the next few weeks?

Kind regards,

[bwelsh_tracker]

When I Pause the updates, I am tracking the date they are set to resume so that I can make sure I do not lose any work.

The problem I am experiencing with PDF XChange is occurring BEFORE that Microsoft update is occurring. And even if it was related to M$ Updates, I have those set to occur outside of Active Hours. The XChange issue is happening mid-day, DURING those Active Hours. So this is NOT a M$ Update issue.

Last night I ran M$ Updates, then after the required Restart I opened only XChange with no files opened as per your suggestion. This morning when I unlocked the screensaver, Xchange remained open.

[Stefan - PDF-XChange]

Hello bwelsh_tracker,

We are lately noticing that e.g. Anti-Virus tools are also sometimes updating our products.
So please check whether yours has such a feature - and maybe try to exclude ours from forced updates.

Does your machine hibernate if left inactive for prolonger periods? Or maybe it has some power saving options that could power down non system drives (and is the Editor installed on your system drive or elsewhere)?

Kind regards,
Stefan

[bwelsh_tracker]

The only local AV is Microsoft's. The machine does not hibernate unless the power goes out. The App is installed on the local system drive, and I have my power settings set such that the power remains active at all times for this SSD.

Last night I opened a PDF along with other apps and files, and this was the overnight state. This morning there was no attempted forced close waiting when I unlocked the screensaver. Tonight I will add a PDF with unsaved changes to the mix.

[Stefan - PDF-XChange]

Hello bwelsh_tracker,

Thanks for letting us know it's not AV/Power/Hibernation issue!

And it's good that last night's test was "uneventful" - that's what we are after
Do let us know how the test tonight goes with the file with unsaved changes to it.

Kind regards,
Stefan

[bwelsh_tracker]

Out of the blue last night the issue has returned, as it always does. PDF Xchange is looking to close, asking me about the unsaved changes to one of my files.

No Microsoft update has kicked off - these are still deferred until Jan. 31. No hibernation or sleep; just the screensaver locked overnight.

[Roman - Tracker Supp]

Hello bwelsh_tracker,

Please disable Windows Screensaver and check if the issue still persists when you leave your computer for a while.

[bwelsh_tracker]

Turning off the screen saver has no effect. Locking the PC and leaving it idle for ~ 5-10 minutes produces the same result.

[Roman - Tracker Supp]

Please create a memory dump of the Editor process when you see it in that state next time.
You can use Windows Task Manager for this:

Then upload the resulting dump file (%TEMP%\PDFXEdit.dmp) here.

[bwelsh_tracker]

Done

[Roman - Tracker Supp]

Thanks.
Were any other applications opened when that issue occurred?
If you are unsure, please open MS Office Word application and leave you computer locked for a while. As you did this with the Editor.

[bwelsh_tracker]

Yes, I had multiple other applications open.

[Roman - Tracker Supp]

Hi bwelsh_tracker,
We will contact you later today with further steps.
Thanks for your patience.