- Remove From My Forums
-
Question
-
— OS:
Windows 7 32 bit.
— Development
environment : VS 11I am building a sensor UMDF driver for Windows8.
After building the driver, error was occured during the signing process:
SIGNTASK : SignTool error : SignedCode::Sign returned error: 0x800700C1
Unfortunately, I can’t find the signtool command line that defined in VS11 GUI or the vcproj file.
But I can turn the
SignMode to OFF in vcproj file and sign the driver manually and it works.My question is :
1. What does the error code mean for signtool.
2. Where can I modify the signtool command line using VS11?
Thanks.
Answers
-
-
Marked as answer by
Monday, April 18, 2016 10:44 PM
-
Marked as answer by
-
Well it is an HRESULT code and 7 is the Win32 subsystem, and C1 (193) is
ERROR_BAD_EXE_FORMAT so I suspect that somehow you have a 32bit/64bit conflict in the tools.
Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr
-
Marked as answer by
Doron Holan [MSFT]
Thursday, June 7, 2012 5:32 AM
-
Marked as answer by
-
Layne Zhang wrote:
>
>- OS: Windows 7 32 bit.
>- Development environment : VS 11
>
>I am building a sensor UMDF driver for Windows8.
>
>After building the driver, error was occured during the signing process:
>
>SIGNTASK : SignTool error : SignedCode::Sign returned error: 0x800700C1
0x800700C1 is decimal 193, which is ERROR_BAD_EXE_FORMAT. You must be
grabbing a version of SignTool that doesn’t understand the changes from
VS11.
—
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
Tim Roberts, VC++ MVP Providenza & Boekelheide, Inc.
-
Marked as answer by
Doron Holan [MSFT]
Thursday, June 7, 2012 5:32 AM
-
Marked as answer by
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Assignees
Comments
- Which version of WiX are you building with?
3.11.2
- Which version of Visual Studio are you building with (if any)?
Visual Studio 2019, v.16.3.2
- Which version of the WiX Toolset Visual Studio Extension are you building with (if any)?
1.0.0.4
- Which version of .NET are you building with?
4.0
-
Describe the problem and the steps to reproduce it.
- Build custom action dll
- Try to codesign the dll, you will get the error:
%1 is not a valid Win32 application.
-
Describe the behavior you expected and how it differed from the actual behavior.
Codesigning of a generated CA dll should be possible
Downgrading package to WiX 3.11.1 solves the issue. It looks like regression.
How are you building the custom action DLL? How are you signing it?
I’ve stripped down the existing project, please check attachment. The issue is reproducible if I just manually build this project in VS 2019.
Code signing command looks like:
C:signtoolsigntool.exe" sign /f "C:signtoolkey.pfx" /p keyPass /t "http://timestamp.comodoca.com/" /v "C:ReleaseSetup.CA.dll"
This command output looks like:
The following certificate was selected:
…
Done Adding Additional Store
SignTool Error: SignedCode::Sign returned error: 0x800700C1
%1 is not a valid Win32 application.
SignTool Error: An error occurred while attempting to sign: C:ReleaseSetup.CA.dllNumber of files successfully Signed: 0
Number of warnings: 0
Number of errors: 1
I also tried to use signtool.exe from the most recent Windows 10 SDK. The output, in this case, looks a bit different but it basically refers to the same error (it refers to http://aka.ms/badexeformat instead).
Setup.zip
I tried to compile the project in the Setup.zip using Visual Studio 2019 and it does produces Setup.CA.dll file which cannot be signed, nor it can be viewed by tools like PE Explorer (even when recompiled as 32-bit DLL).
> peverify.exe /VERBOSE Setup.CA.dll
Microsoft (R) .NET Framework PE Verifier. Version 4.0.30319.0
Copyright (c) Microsoft Corporation. All rights reserved.
File not found or has bad headers.
1 Error(s) Verifying Setup.CA.dll
I tried this with WiX Toolset 3.10 which we use to compile our installer project and the custom action produced by it has the same issue. We never signed the CA dll in this project…
PEVerify is for managed assemblies. *.CA.dll are native DLLs.
I am also having this issue with exactly the same output as Andrey. Tested signtool from winsdk 8 and 10. I just recently upgraded to wix 3.11.2 from 3.8 so not sure when it started. Unsure if this is helpful but I am able to open the *.CA.dll of my pre-upgraded project using 7zip to see the contents. Trying to open a new *.CA.dll with 7zip results in an error saying it is not seen as an archive.
If sfxca.dll is signed before makesfxca runs, the resulting *.ca.dll cannot be signed, nor can the previous signature be removed (I forget what the error was, but it may have been the one your reporting).
I suspect that the fact that sfxca.dll was signed in the most recent v3 publicly released build may be the cause of this.
@andrey-ivanov, @jozefizso, @WesleyFudala please try to remove the digital signature from the sfxca.dll file in your WiX toolset files, try your build again, and report back to this issue if that resolved your issue or not.
@BMurri I’m not sure how to properly remove the digital signature. I did try using the signtool remove option on both the x86 and x64 sfxca.dll but still got the same issue signing the resulting custom action dll. I suspect this was not the right way to remove the signature as I still see an entry in the digital signatures tab if I view the file properties. Perhaps the others will have better luck.
Thanks @BMurri. I followed your advice and I now have a working installer.
Is there a way to do this without modifying sfxca.dll in place? I assume that my changes will be squashed the next time Wix is updated.
I’ll post a couple of pull requests.
If sfxca.dll is signed before makesfxca runs, the resulting *.ca.dll cannot be signed, nor can the previous signature be removed (I forget what the error was, but it may have been the one your reporting).
I suspect that the fact that sfxca.dll was signed in the most recent v3 publicly released build may be the cause of this.
@andrey-ivanov, @jozefizso, @WesleyFudala please try to remove the digital signature from the sfxca.dll file in your WiX toolset files, try your build again, and report back to this issue if that resolved your issue or not.
That solved my problem. Thank you very much.
wixtoolset
locked as resolved and limited conversation to collaborators
Dec 3, 2020
signtool.exe returned error 0x800700C1
To sign our binaries with Authenticode I am using Microsoft’s signtool. Unfortunatelly, it is not really descriptive in some error codes it returns.
In my case, I have been replacing resources in some native binaries, which were already signed. Of course, this will break existing Authenticode signature, but the signature is still there.
Signature is just one of sections in the EXE/DLL file and this section stays there, even if the file signature is invalid.
Signtool unfortunatelly cannot resign an file which is already signed and is always returning same error 0x800700C1.
SignTool Error: SignedCode::Sign returned error: 0x800700C1
This error is in fact ERROR_BAD_EXE_FORMAT.
So, I needed to remove existing signature from an binary file.
One interesting tool called delcert is already writen and works pretty nice to solve this and has source code included:
http://forum.xda-developers.com/showthread.php?p=2508061
After quick look into the C++ source, it is in fact does nothing magic. It is using Win32 API from ImageHlp library (which takes case of loading of binaries).
Interesting functions there are: ImageRemoveCertificate, which needs to be followed by MapAndLoad/UnMapAndLoad pair to clear section from PE headers.
After removing signature, signtool has no complains and signs the file nicely.
One step back to the ERROR_BAD_EXE_FORMAT error code
In your Microsoft SDK Program Files, you will probably have X86 and x64 versions of signtool (one in Program Files (x86), another in Program Files).
So depending on your binary bitness (32bit vx 64bit) you have to call proper signtool, otherwise you will get the original error.
Источник
Signtool error signedcode sign returned error 0x800700c1
I was just looking into signing our installer/uninstaller and read this wiki article: http://nsis.sourceforge.net/Signing_an_Uninstaller
Everything seemed to go well until it comes to signing the actual uninstaller:
!system: «»C:Program FilesMicrosoft SDKsWindowsv7.1Binsigntool.exe» sign /f «X:sslcodey.pfx» /p abcdef /t «http://timestamp» «C:UsersyAppDataLocalTempuninstaller.exe»»
Done Adding Additional Store
Number of errors: 1
SignTool Error: SignedCode::Sign returned error: 0x800700C1
Either the file being signed or one of the DLL specified by /j switch is not a valid Win32 application.
SignTool Error: An error occurred while attempting to sign: C:UsersyAppDataLocalTempuninstaller.exe
!system: returned 1
But there is nothing wrong with that uninstaller. I can execute it just fine (so I’m quite certain it’s a valid Win32 application).
Is the approach outlined in that article still correct?
That means «The parameter is incorrect». Try writing the uninstaller elsewhere.
I think it just resolved itself.
I won’t claim that I understand it, but I think the issue was related to switching compression on and off during the build process.
Most likely, the way I use the code from the article isn’t optimal (to say the least) and this caused problems.
I now enable whole LZMA compression at the beginning of the build process and just keep it. Even though the build takes forever 😛
It appears that if you try to sign the uninstaller belonging to a signed installer you will get the same exception..
Isn’t that strange?
I am getting the same error when I attempt to sign uninst.exe. The error persists even if I turn off compression completely.
My guess is when nullsoft installer dynamically patches the uninst.exe file, it somehow violates some non-critical rule of win32 exe format which doesn’t affect correction executation of the file. But it is not able to pass the exe format validation performed by the signtool.exe file from Microsoft Platform SDK.
Does anybody have a better idea what might go wrong?
I’ve not had any issues signing uninstall executables. How are you going about it? You need to:
1. Write a standalone script which generates the uninstaller.
2. Build it and run the built executable to generate the uninstaller.
3. Sign the generated uninstaller.
4. Bundle it in the main installer.
I wasn’t aware there was any other way so you are probably already doing this?
I didn’t attempt to create the fully automatic flow yet. I just use the original script to generate the installer, install it manually to get the file uninst.exe. Then I tried to sign the uninst.exe file manually and got this error. I do use the unicode version of the installer instead of the ansi version.
I noticed in your earlier reply saying «Try writing the uninstaller elsewhere». How does the location of the uninstaller matter in this case?
I’ve not had any issues signing uninstall executables. How are you going about it? You need to:
1. Write a standalone script which generates the uninstaller.
2. Build it and run the built executable to generate the uninstaller.
3. Sign the generated uninstaller.
4. Bundle it in the main installer.
I wasn’t aware there was any other way so you are probably already doing this?
I ran across this post from a Google search because I was having the same problem signing an uninstaller from Bitrock Install Builder. This was my solution:
1.) Build an unsigned installer
2.) Install that unsigned installer on your machine
3.) Sign the resultant uninstall.exe
4.) Package it with your distribution
5.) Build the signed installer
BitRock instructions for packaging and deploying are here if anybody is interested:
http://answers.bitrock.com/questions. ler-on-windows
This may sound like the strangest solution, but for me it worked if I did not sign the installer that wrote the uninstaller.
So this would be the procedure:
1) Make an installer that writes the uninstaller. DO NOT SIGN THIS INSTALLER.
2) Run the installer. This creates the uninstaller.
3) Sign the uninstaller.
4) Make the installer again, this time including the signed uninstaller as a «File» operation instead of writing the uninstaller with «WriteUninstaller».
5) Sign this installer.
This is totally weird. but it worked for me. With a signed installer writing the uninstaller, I cannot sign the uninstaller. I get the 0x800700C1 error.
But if I have used an unsigned installer to write the uninstaller, then I can sign the uninstaller.
Hope this helps you guys.
BR
/Michael
Источник
Signtool error signedcode sign returned error 0x800700c1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am facing an issue where antivirus of my machine is showing alert while uninstalling my application. Antivirus is saying that uninstall.exe is not signed. My installer is signed but uninstall.exe created after installation is not signed.
Please suggest that what would be the right approach to avoid this issue.
InstallBuilder
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unfortunately InstallBuilder does not currently allow signing uninstallers.
However, this can be easily resolved. The uninstaller binary does not contain any metadata and is simply a generic binary that can be overwritten by a signed one.
First thing is to create and install any project using your version of InstallBuilder (preferably with also the uninstall.exe windows resources such as application name being set properly), then use the created uninstaller.exe and sign it.
Next the signed uninstaller should be part of files copied by the installer, but with a different name — such as uninstall-signed.exe .
Finally the installer should replace the uninstaller in
3000 $/uninstall.exe $/uninstall-signed.exe $/uninstall-signed.exe
The code above will also delete the uninstall-signed.exe and remove it from list of files to uninstall.
The action prevents overwriting issues for cases such as antivirus or OS still keeping the uninstall.exe opened.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have installed installer on system and copy uninstaller file at other location. When i am signing the uninstall.exe file with certificate, it throw an error:
SignTool Error: SignedCode::Sign returned error: 0x80070057 The parameter is incorrect. SignTool Error: An error occurred while attempting to sign: C: or or Documents or or uninstall-signed.exe
Can you please help me to signing the unsintaller.exe with digiat certificate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could you provide us which command are you using to signed the uninstaller file? Also, could you check that the uninstaller is not already signed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have used the command : signtool sign /v /ac or ‘ DigiCert.cer or ‘ /f or ‘ certificate.pfx or ‘ /p password or ‘ uninstall.exe or ‘ . Yes, i have verified that uninstaller.exe is not signed in.
Please let me know in case of any other details required.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could you add the option or ‘ /d or ‘ to enable the debug? Please find below the link to the official documentation of this tool: https://msdn.microsoft.com/en-us/library/windows/desktop/aa387764(v=vs.85).aspx
You could also try to use the or ‘ osslsigncode or ‘ tool: http://sourceforge.net/projects/osslsigncode/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
same signing problem — the uninstaller doesn’t appear to work with the microsoft signtool. has anyone from installerbuidler actually tried to run this command?
signtool sign /d /v /tr http://timestamp.digicert.com /td sha256 /fd sha256 /f or ‘ cert.pfx or ‘ /p password or ‘ uninstall-signed.exe or ‘ Done Adding Additional Store SignTool Error: SignedCode::Sign returned error: 0x800700C1 Either the file being signed or one of the DLL specified by /j switch is not a valid Win32 application. SignTool Error: An error occurred while attempting to sign: uninstall-signed.exe
Number of errors: 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
figured it out by following this post — @MichaelKarnerfor — THANKS FOR THIS SOLUTION!
THE TRICK IS THE INSTALLER THAT INSTALLS THE UNINSTALLER, MUST NOT-BE-SIGNED SO YOU ARE SIGNING AN UNINSTALLER THAT CAME FROM AN INSTALLER THAT WAS NOT SIGNED.
once you get that uninstaller signed, then you can follow the plan and include it into the project as a signed uninstaller and overwrite the generated installer.
== from another forum ==
This may sound like the strangest solution, but for me it worked if I did not sign the installer that wrote the uninstaller.
So this would be the procedure:
1) Make an installer that writes the uninstaller. DO NOT SIGN THIS INSTALLER. 2) Run the installer. This creates the uninstaller. 3) Sign the uninstaller. 4) Make the installer again, this time including the signed uninstaller as a or ‘ File or ‘ operation instead of writing the uninstaller with or ‘ WriteUninstaller or ‘ . 5) Sign this installer.
This is totally weird. but it worked for me. With a signed installer writing the uninstaller, I cannot sign the uninstaller. I get the 0x800700C1 error.
But if I have used an unsigned installer to write the uninstaller, then I can sign the uninstaller.
Источник
Discus and support 0x800700C1 in SignTool in Microsoft Windows 10 Store to solve the problem; hi
i hvae made a 32 bit game but im having trouble signing the sertificate off the .appx file
this is the error that i get
C:Program Files…
Discussion in ‘Microsoft Windows 10 Store’ started by toniantonia, Oct 31, 2018.
-
0x800700C1 in SignTool
hi
i hvae made a 32 bit game but im having trouble signing the sertificate off the .appx file
this is the error that i get
C:Program Files (x86)Windows Kits10bin10.0.17134.0×86>SignTool sign /fd SHA256 /a /f signingCertx.pfx C:projectxsnakePackageFilessnake.appx
Done Adding Additional Store
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: C:projectxsnakePackageFilessnake.appxi have used desktop app converter to make the EXE into an APPX
i have done all the steps that has brought me to this code:
SignTool sign /fd SHA256 /a /f signingCertx.pfx C:projectxsnakePackageFilessnake.appx
but im stuck coz all i get is the error mentioned above after i type the code below :
SignTool sign /fd SHA256 /a /f signingCertx.pfx C:projectxsnakePackageFilessnake.appx
my certificate has no password so i didnt include the /p
can you help me please
it would be much apritiated
i run windows pro
i have the windows SDK installed
also i have visual studio 7 that makes it easier
thank you
-
Error 0x800700c1 in windows 10I have got the error 0x800700C1 and could not update KB3115259, KB3167685, KB3163018 & KB3149135 since a week ago. I tried both you two methods but the result was the same. I don’t wish to follow hbja to go back to «Factory Setting». Can you help me sort
it out with other solutions? -
Error 0x800700c1 in windows 10
Hi,
Thank you for posting your query on Microsoft Community.
Share this information to assist you better.
- Which build is currently installed in your computer?
- Do you have any anti-virus program installed?
The error code 0x800700C1 occurs because the Windows Authenticode Signature Verification function now verifies portable executable (PE) files.
I suggest you to follow the methods below and check if you can install the updates:
Method 1: Run Windows Update Troubleshooter
I suggest you to run the Windows Update Troubleshooter. Follow these steps to run Windows Update
troubleshooter:- Press Windows key + W and type
troubleshooting. - Select Troubleshooting.
- Select View all on the top left corner.
- Click Windows Update troubleshooter.
- Follow the on-screen instructions to run the troubleshooter.
- Check if issue persists.
If the issue persists, follow next method.
Method 2:
I suggest you to check if the services responsible for Windows update is running. Refer to these steps:
- Press Windows key +R, type “services.msc”
- Locate the BITS, Cryptographic, MSI Installer
and the Windows Update Services and check if it is running. - If not, right click on the service and click start to start the service.
Hope this helps, let us know the status of the issue. We will assist you further.
-
0x800700C1 in SignTool
Anniversary Update fails with error 0x800700c1
Using Windows 10 Upgrade Assistant Anniversary update fails with 0x800700c1. Checking update history shows other updates are installing but Anniversary failing for the past several weeks. Troubleshooting Windows Update (both program and manual steps) has
no effect.Update proceeds to 85% (very slow after 71%) at which point error 0x800700c1 is received. If «Try Again» is selected update proceeds to 71% whereupon white update window closes and blue update window opens and eventually closes with pop-up advising failure.
Clicking OK returns to white update window with error 0x800700c1 notification.HP Probook 450 G3
Win 10 Pro 1511
0x800700C1 in SignTool
-
0x800700C1 in SignTool — Similar Threads — 0x800700C1 SignTool
-
0x800700c1 error, tried multiple solutions from answers community and none have worked
in Windows 10 Gaming
0x800700c1 error, tried multiple solutions from answers community and none have worked: Hello, so I have been stuck unable to update windows for a very long time now, well over 1.5 years. Whenever I do, I get the error code 0x800700c1I have tried the dism solution, but get the error when attempting it Image Version: 10.0.19042.804 [== 3.8% ] Error: 87 An error… -
0x800700c1 error, tried multiple solutions from answers community and none have worked
in Windows 10 Software and Apps
0x800700c1 error, tried multiple solutions from answers community and none have worked: Hello, so I have been stuck unable to update windows for a very long time now, well over 1.5 years. Whenever I do, I get the error code 0x800700c1I have tried the dism solution, but get the error when attempting it Image Version: 10.0.19042.804 [== 3.8% ] Error: 87 An error… -
0x800700c1 error, tried multiple solutions from answers community and none have worked
in Windows 10 Installation and Upgrade
0x800700c1 error, tried multiple solutions from answers community and none have worked: Hello, so I have been stuck unable to update windows for a very long time now, well over 1.5 years. Whenever I do, I get the error code 0x800700c1I have tried the dism solution, but get the error when attempting it Image Version: 10.0.19042.804 [== 3.8% ] Error: 87 An error… -
windows update failure 0x800700c1
in Windows 10 Gaming
windows update failure 0x800700c1: i have tried almost everything i can think of i have consulted YouTube tutorials, forums and nothing I’ve tried has worked I’m pretty sure its due to some corrupt files but I’ve tried the sfc scan and it doesn’t work I’ve tried resetting my pc that hasn’t worked either so I’m… -
windows update failure 0x800700c1
in Windows 10 Software and Apps
windows update failure 0x800700c1: i have tried almost everything i can think of i have consulted YouTube tutorials, forums and nothing I’ve tried has worked I’m pretty sure its due to some corrupt files but I’ve tried the sfc scan and it doesn’t work I’ve tried resetting my pc that hasn’t worked either so I’m… -
windows update failure 0x800700c1
in Windows 10 Installation and Upgrade
windows update failure 0x800700c1: i have tried almost everything i can think of i have consulted YouTube tutorials, forums and nothing I’ve tried has worked I’m pretty sure its due to some corrupt files but I’ve tried the sfc scan and it doesn’t work I’ve tried resetting my pc that hasn’t worked either so I’m… -
Some BSODS and an issue with windows updater. 0x800700c1
in Windows 10 Gaming
Some BSODS and an issue with windows updater. 0x800700c1: Hi everyone, I have been struggling with quite consistent BSOD’s and have done the best I can reading online to solve the issue but I am now stuck.I recently looked at my pc’s reliability and problem history and noticed the most persistent issue is with Windows Update… -
Some BSODS and an issue with windows updater. 0x800700c1
in Windows 10 Software and Apps
Some BSODS and an issue with windows updater. 0x800700c1: Hi everyone, I have been struggling with quite consistent BSOD’s and have done the best I can reading online to solve the issue but I am now stuck.I recently looked at my pc’s reliability and problem history and noticed the most persistent issue is with Windows Update… -
Some BSODS and an issue with windows updater. 0x800700c1
in Windows 10 BSOD Crashes and Debugging
Some BSODS and an issue with windows updater. 0x800700c1: Hi everyone, I have been struggling with quite consistent BSOD’s and have done the best I can reading online to solve the issue but I am now stuck.I recently looked at my pc’s reliability and problem history and noticed the most persistent issue is with Windows Update…
Users found this page by searching for:
-
signtool error: signedcode::sign returned error: 0x800700c1
,
-
0x800700c1 signtool
,
-
SignedCode::Sign returned error: 0x800700C1
,
- signe tool error 0x800700C1,
- windows 10 error 0x800700c1,
- error 0x800700c1 windows 10 mobile
