0006746: 64bit executables created with makejcldbg.exe tool cause Microsoft's signtool.exe to report "not a valid Win32 application"

ID	Project	Category	View Status	Date Submitted	Last Update

0006746	JEDI Code Library	JclDebug*	public	2022-04-07 17:43	2022-04-07 17:44

Reporter	Sean	Assigned To
Priority	high	Severity	major	Reproducibility	always
Status	new	Resolution	open
Product Version
Target Version		Fixed in Version

Summary	0006746: 64bit executables created with makejcldbg.exe tool cause Microsoft's signtool.exe to report "not a valid Win32 application"
Description	We've been adding code signatures to all our executables since 2018, using the Windows SDK utility "signtool.exe", together with a CA-issued Code Signing certificate. Adding a map file to a 64 bit executable, e.g. ... makejcldbg.exe -e /bin=example64.exe example64.map ... creates an exe that cannot be codesigned by Microsoft's signtool.exe
Steps To Reproduce	1. Build any 64bit executable. 2. Use makejcldbg.exe to add the map as a section with the Portable Executable. 3. Use signtool.exe to apply a code signature (for example, with a suitable code-signing certificate installed in the Local Machine store use command signtool.exe sign /sm example.exe Signtool.exe will report: SignTool Error: SignedCode::Sign returned error: 0x800700C1 For more information, please see https://aka.ms/badexeformat SignTool Error: An error occurred while attempting to sign: Example.exe If the map file _hasn't_ been added to the executable, SignTool will work correctly.
Tags	No tags attached.

Fixed in GIT commit
Fixed in SVN revision
IDE version	All