Hi,
I'm currently evaluating an upgrade of our PDF-XChange Drivers API SDK integration from v5 to v11, primarily to provide support for Windows on ARM64.
During testing of the redistributable installers, I've encountered an issue with exit code 3010, which our application's installer interprets as requiring a Windows restart.
I've tested several versions of the PDF-XChange redistributable on Windows 10 (x64), with the following results:
Redist.________Exit Code ____Restart Windows
v5.0.273.2 ............0 ........................Yes
v7.0.327.1..........3010 .....................Yes
v8.0.334 ............3010 ......................Yes
v11.1.1.0 ...........3010 ......................No
All installations report that the installation process succeeded.
The tests were performed using the /VERYSILENT /NORESTART /LOG parameters, and the results are repeatable, including after restarting Windows.
Our application installer is built using Inno Setup and handles exit code 3010 by asking the user to restart Windows and rerun the installation. Unfortunately, because the redistributable continues to return 3010, this results in an endless restart/install cycle.
I would appreciate some clarification on the following:
1. Why do v7, v8 and v11 redistributables consistently return exit code 3010, whereas v5 returns 0, even when installation appears to have completed successfully?
2. How should we interpret the discrepancy between the exit codes and the setup logs? In particular, v5 returns 0 despite reporting that a restart is required, whereas v11 returns 3010 despite reporting that no restart is necessary.
3. Is there a supported way to determine whether a restart is genuinely required, rather than relying solely on the redistributable's exit code?
Our objective is to ensure that the PDF-XChange driver is installed correctly while avoiding unnecessary restarts or repeated installation attempts.
I've attached the relevant installation logs for reference.
Any guidance would be greatly appreciated.
Kind regards,
Michael
Redistributable Exit Code 3010
Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Vasyl - PDF-XChange, Stefan - PDF-XChange
-
mike11
- User
- Posts: 3
- Joined: Sun Feb 05, 2012 11:32 pm
Redistributable Exit Code 3010
You do not have the required permissions to view the files attached to this post.
-
Sean - PDF-XChange
- Site Admin
- Posts: 1423
- Joined: Wed Sep 14, 2016 5:42 pm
Re: Redistributable Exit Code 3010
Hi Mike,
We received a similar report to this via email—could you please clarify if it was you who sent that email?
Kind regards,
We received a similar report to this via email—could you please clarify if it was you who sent that email?
Kind regards,
Sean Godley
Technical Writer
PDF-XChange Co LTD
Sales: +1 (250) 324-1621
Fax: +1 (250) 324-1623
Technical Writer
PDF-XChange Co LTD
Sales: +1 (250) 324-1621
Fax: +1 (250) 324-1623
-
mike11
- User
- Posts: 3
- Joined: Sun Feb 05, 2012 11:32 pm
Re: Redistributable Exit Code 3010
Hi Sean,
I did initially send the query to Chris, as I was communicating with him at the time, and he said that I should direct my query here.
Cheers
I did initially send the query to Chris, as I was communicating with him at the time, and he said that I should direct my query here.
Cheers
-
mike11
- User
- Posts: 3
- Joined: Sun Feb 05, 2012 11:32 pm
Re: Redistributable Exit Code 3010
**Update – v11 redistributable fails to install on Windows ARM64**
Hi,
A brief update on our testing.
We've implemented a workaround in our application's installer for the exit code 3010 issue described above, so that is no longer preventing us from proceeding with our evaluation.
However, we've now encountered a more fundamental problem when attempting to install the v11 redistributable on Windows ARM64.
Our test device is a Microsoft Surface Pro 12-inch with a Snapdragon X Plus processor, running Windows 11 Pro 25H2 (build 26200.9457).
When running `PDFX11SA_sm.exe`, either from our application installer or independently, the installation fails almost immediately with the following message:
"This program can only be installed on versions of Windows designed for the following processor architectures: x86, x64."
The installation log confirms:
- Inno Setup version 6.2.2
- Windows version 10.0.26200
- Processor architecture: ARM64
My understanding is that ARM64 support was introduced in v9 of the Drivers API SDK.
Could you please clarify whether the v11 redistributable supports ARM64 and, if so, whether a separate installer or different installation procedure is required?
Also, can the v11 SDK's COM interface be used by a 32-bit VB6 application running under Windows ARM64 emulation?
Our objective is to replace our existing v5 integration, which cannot create a PDF printer on this device.
I've attached the ARM64 installation log for reference.
Many thanks for your assistance.
Kind regards,
Michael
Hi,
A brief update on our testing.
We've implemented a workaround in our application's installer for the exit code 3010 issue described above, so that is no longer preventing us from proceeding with our evaluation.
However, we've now encountered a more fundamental problem when attempting to install the v11 redistributable on Windows ARM64.
Our test device is a Microsoft Surface Pro 12-inch with a Snapdragon X Plus processor, running Windows 11 Pro 25H2 (build 26200.9457).
When running `PDFX11SA_sm.exe`, either from our application installer or independently, the installation fails almost immediately with the following message:
"This program can only be installed on versions of Windows designed for the following processor architectures: x86, x64."
The installation log confirms:
- Inno Setup version 6.2.2
- Windows version 10.0.26200
- Processor architecture: ARM64
My understanding is that ARM64 support was introduced in v9 of the Drivers API SDK.
Could you please clarify whether the v11 redistributable supports ARM64 and, if so, whether a separate installer or different installation procedure is required?
Also, can the v11 SDK's COM interface be used by a 32-bit VB6 application running under Windows ARM64 emulation?
Our objective is to replace our existing v5 integration, which cannot create a PDF printer on this device.
I've attached the ARM64 installation log for reference.
Many thanks for your assistance.
Kind regards,
Michael
You do not have the required permissions to view the files attached to this post.