Resolve Windows App Code Signing Issue
Budget: $30 – $250 USD
Project Title:
Fix Code Signing / Certificate Issue for Windows Application
Project Description:
I have developed a Windows desktop application (EXE file), and I have already added a code signing certificate. However, when I run the installer or EXE on a system, Windows still flags it as "untrusted" or "not signed", showing warnings like "Windows protected your PC" or "Publisher: Unknown".
I need an experienced Windows developer (or someone familiar with code signing and digital certificates) to:
- Review the current code signing implementation
- Verify if the certificate is correctly applied to the EXE and/or installer
- Ensure the application shows a trusted publisher and removes SmartScreen warnings
- Guide me on best practices for code signing (timestamping, using EV certs if needed, etc.)
- Help with resigning or reconfiguring the application if necessary
---
Requirements:
- Experience with Windows app development and digital code signing
- Familiarity with tools like `signtool`, `certutil`, or similar
- Knowledge of Windows SmartScreen and reputation-based protection
- Ability to troubleshoot certificate chain, timestamping issues, and trust level problems
---
Deliverables:
- A properly signed application that does not show untrusted publisher warnings
- Step-by-step guide or assistance for future builds
- Explanation of what was wrong and how it was fixed
---
Please only apply if you have previously worked with code signing and resolving trust issues in Windows applications. I can provide the EXE, the installer, and details about the certificate I used.
Fix Code Signing / Certificate Issue for Windows Application
Project Description:
I have developed a Windows desktop application (EXE file), and I have already added a code signing certificate. However, when I run the installer or EXE on a system, Windows still flags it as "untrusted" or "not signed", showing warnings like "Windows protected your PC" or "Publisher: Unknown".
I need an experienced Windows developer (or someone familiar with code signing and digital certificates) to:
- Review the current code signing implementation
- Verify if the certificate is correctly applied to the EXE and/or installer
- Ensure the application shows a trusted publisher and removes SmartScreen warnings
- Guide me on best practices for code signing (timestamping, using EV certs if needed, etc.)
- Help with resigning or reconfiguring the application if necessary
---
Requirements:
- Experience with Windows app development and digital code signing
- Familiarity with tools like `signtool`, `certutil`, or similar
- Knowledge of Windows SmartScreen and reputation-based protection
- Ability to troubleshoot certificate chain, timestamping issues, and trust level problems
---
Deliverables:
- A properly signed application that does not show untrusted publisher warnings
- Step-by-step guide or assistance for future builds
- Explanation of what was wrong and how it was fixed
---
Please only apply if you have previously worked with code signing and resolving trust issues in Windows applications. I can provide the EXE, the installer, and details about the certificate I used.