Copy link to clipboard
Copied
We try to use the Adobe PDF Reader ActiveX control in a 64-bit WPF app, but the app crashes every time when I try to move the cursor inside the control. The crash is caused by a BadImageFormatException when the CLR tries to load "comctl32.dll". The root cause of this problem is the embedded manifest in "AcroPDFImpl64.dll" which defines wrong values for processorArchitecture (X86).
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="Adobe Systems Inc.Acrobat.Adobe PDF Browser Control" type="win32"></assemblyIdentity>
<description>Adobe PDF Browser Control.</description>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="X86" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity>
</dependentAssembly>
</dependency>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
If I change the "PreferExternalManifest" registry setting and provide my own manifest as external file with correct values for processorArchitecture (amd64), then there is no crash anymore.
But this change would have to much disadvantages to be usable in production environments.
Is it possible to provide a correct version with the next Acrobat Reader Update?
Copy link to clipboard
Copied
A better place for this would be in a bug report: Feature Request/Bug Report Form