PDF-XChange Lite 11.1.0 — Longstanding Printer Failure — Development Escalation Stalled

This Forum is for the use of End Users requiring help and assistance for Tracker Software's PDF-XChange Printer Drivers only - Please do not post requests for older versions of PDF-XChange or the PDF-Tools/OFFice2PDF applications here

Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Vasyl - PDF-XChange, Stefan - PDF-XChange

erikstanford
User
Posts: 2
Joined: Mon Nov 16, 2026 4:39 pm

PDF-XChange Lite 11.1.0 — Longstanding Printer Failure — Development Escalation Stalled

Post by erikstanford »

I am seeking assistance from a PDF-XChange developer or senior support representative concerning a longstanding PDF-XChange Lite printer failure on Windows 11. My documented correspondence with PDF-XChange Support began October 6, 2026, concerning a problem that had already persisted for an extended period.

The problem has persisted across multiple software versions despite extensive troubleshooting. PDF-XChange Lite fails to invoke the expected Save As dialog or produce a usable PDF. Microsoft Print to PDF works correctly on the same computer and from the same applications.

Previous symptoms have included:

PrintService events 319, 365, and 808

Error 0x8000ffff

Component-loading errors involving pxclpv.dll, pxcdrvL.dll, and pxcpmL.dll

Error codes 126 / 0x7E

On October 9, 2026, I reproduced the failure while recording synchronized PrintService logs and a full ProcMon trace. PrintService Event 307 recorded one page printed with a size of zero bytes.

I uploaded all requested diagnostic files to PDF-XChange Support that evening.

On October 27, support confirmed that the files had been forwarded to Development on October 9. However, as of November 16, I have received no confirmation that Development has actually examined them, no technical findings, and no investigation timeline.

I have only one affected computer and have preserved its failing configuration pending Development's assessment. Repeated reinstallations, printer resets, and other general troubleshooting have already been performed.

I am requesting assistance with three specific matters:

1. Confirmation that Development has actually reviewed the October 9 diagnostic evidence.

2. An initial technical assessment identifying what the traces establish and what remains unresolved.

3. Assignment of an accountable case owner and a reasonable timeframe for the next update.

I have cooperated fully with the diagnostic process and would appreciate assistance moving this investigation toward a definitive root cause and durable resolution.

The complete correspondence and diagnostic files are already available to PDF-XChange Support. I can provide the existing email subject and upload details privately to help locate the case.

Thank you.
User avatar
Dimitar - PDF-XChange
Site Admin
Posts: 2743
Joined: Mon Jan 15, 2018 9:01 am

Re: PDF-XChange Lite 11.1.0 — Longstanding Printer Failure — Development Escalation Stalled

Post by Dimitar - PDF-XChange »

Hello Erik,

Welcome to our forum as well.

Thank you for reaching out via the forum. As there have been occasional issues with email delivery recently, I wasn't sure if my previous replies had reached you.

First of all, I would like to thank you for your patience and for the considerable effort you have put into documenting this issue and providing the requested diagnostic information.

I can confirm that your case, along with the diagnostic files and logs you supplied, was forwarded to our Development team for analysis.
The information you provided appears to relate to a particularly complex issue that has proven difficult to reproduce and isolate. As such, the investigation remains open.

At present, we unfortunately are unable to provide a specific timeframe for when a detailed technical assessment or resolution will be available.

Our developers are currently handling a substantial workload that includes not only bug investigations, but also overall product improvements, feature requests, compatibility issues involving third-party software and drivers, and maintenance work across the entire PDF-XChange product line.

Additionally, not all issues are straightforward to investigate, and some require extensive analysis before a root cause can be identified with confidence.

While I understand this may be frustrating, the absence of updates should not be interpreted as a lack of attention to your case.
Rather, it reflects the reality that complex issues can take significant time to investigate, particularly when they involve interactions with Windows components, printer subsystems, or third-party software.

Regarding your specific questions:

1.Your case remains with the Development team and has not been closed.
2. We do not currently have any findings or conclusions that we can share regarding the root cause.
3. We are unable to commit to a specific timeline for the next update, as doing so would risk setting expectations that we may not be able to meet.


Please be assured that the information you provided remains available to the team for review.
Should the developers require additional diagnostic data or identify information that can be shared, we will contact you accordingly.

We appreciate your cooperation, your detailed reporting, and your continued patience while this investigation remains under review.

Kind regards,
erikstanford
User
Posts: 2
Joined: Mon Nov 16, 2026 4:39 pm

Re: PDF-XChange Lite 11.1.0 — Longstanding Printer Failure — Development Escalation Stalled

Post by erikstanford »

Thank you, Dimitar.

First, to clarify, I have received and read your previous email responses. My concern is not email delivery or a lack of acknowledgment. It is the continued absence of confirmation that PDF-XChange Development has actually examined the diagnostic evidence I submitted.

This printer failure has persisted for many months, possibly years, across multiple PDF-XChange versions. My documented correspondence with PDF-XChange Support began October 6, 2026.

What I find particularly disappointing is the extraordinary amount of diagnostic work PDF-XChange specifically requested of me as a prerequisite for Development escalation.

The procedures were extensive, technically demanding, and frankly daunting for someone who is a customer rather than a software developer. They required collecting Windows PrintService logs, configuring and operating Microsoft's Process Monitor, reproducing the failure while capturing synchronized diagnostic evidence, and preserving and uploading the resulting files.

I complied fully with every request and submitted everything on October 9. I undertook that work in good faith, with the reasonable expectation that PDF-XChange would reciprocate by examining the evidence with comparable diligence.

Thirty-nine days later, I still have no confirmation that anyone in Development has actually reviewed those files, no technical findings, no identified case owner, and no indication of when an initial assessment will occur.

I understand that developers have competing demands. However, explanations about workloads, product improvements, and resource limitations do not address the fundamental issue: I am a paying customer with an existing product feature that does not work as intended. Internal resource allocation is PDF-XChange's responsibility, not something customers should have to overcome to obtain meaningful support.

I came to this forum because my efforts through the existing support channel had reached an impasse. I hoped to find someone within PDF-XChange who would advocate for me as a customer, take ownership of this longstanding issue, and help see it through to a satisfactory resolution. Instead, I find myself continuing the same discussion without a clearer path forward.

I have only one computer running PDF-XChange and have preserved its failing configuration for investigation. I remain willing to cooperate with reasonable, technically justified requests, but I should not have to continue speculative troubleshooting indefinitely.

I also requested complimentary maintenance extensions in my November 4 email, including access to future updates and upgrades until this longstanding problem is resolved. That request remains unanswered and should be addressed privately by someone with the appropriate authority.

At this point, I am requesting:

1. Independent advocacy and accountability: Involvement from a senior PDF-XChange technical manager or Development representative who will take ownership of this case and advocate for its proper investigation.

2. Confirmation of Development review: A specific answer regarding whether the October 9 evidence has been examined, any findings, and whether a development ticket and responsible investigator have been assigned.

3. A meaningful commitment: If the evidence has not yet been reviewed, a reasonable timeframe for beginning that assessment and a commitment to substantive progress updates.

4. A management response: An answer to my outstanding request for complimentary maintenance extensions until the issue is satisfactorily resolved.

I am not demanding an immediate fix or a guaranteed resolution date. I am asking for accountability, meaningful technical attention, and someone within PDF-XChange who will advocate for a customer seeking to resolve a longstanding problem.

PDF-XChange asked me to undertake a substantial technical effort so its developers could investigate this failure. I fulfilled my responsibility completely. I now expect the company to follow through on its side of that commitment.

Thank you.