Home
>
WinDev Forum
>
Topic
Error with Certificate during creation of executable and setup Windev Suite 2026
Posted by @Master
|
Error with Certificate during creation of executable and setup Windev Suite 2026 January 06, 2026 05:09AM |
Registered: 2 years ago Posts: 8 |
Hi Everyone,
Hope you all had a great festive season.
Has or is anyone else having the same issue during the creation of executable and setup in Windev Suite 2026??
See pics attached.
I somehow managed to fluke a creation of one, my resarting the PC.
But I cannot get this going again, no changes have been made, only the upgrade to 2026??
If anyone could help it would be greatly appreciated.
Hope you all had a great festive season.
Has or is anyone else having the same issue during the creation of executable and setup in Windev Suite 2026??
See pics attached.
I somehow managed to fluke a creation of one, my resarting the PC.
But I cannot get this going again, no changes have been made, only the upgrade to 2026??
If anyone could help it would be greatly appreciated.
|
Re: Error with Certificate during creation of executable and setup Windev Suite 2026 January 06, 2026 09:54AM |
Admin Registered: 8 years ago Posts: 648 |
Hi, "the certificate is not valid"
Certificates are valid with from - to date. Inspect your certificate store for validity dates.
Either you have to buy a new certificate for code signing or to ask / pay for the extension of your code signing certificate.
Kind regards,
Guenter Predl
gpredl@syspredl.at
Certificates are valid with from - to date. Inspect your certificate store for validity dates.
Either you have to buy a new certificate for code signing or to ask / pay for the extension of your code signing certificate.
Kind regards,
Guenter Predl
gpredl@syspredl.at
|
Re: Error with Certificate during creation of executable and setup Windev Suite 2026 March 10, 2026 07:00AM |
Registered: 2 years ago Posts: 8 |
|
Re: Error with Certificate during creation of executable and setup Windev Suite 2026 March 16, 2026 05:56AM |
Registered: 2 years ago Posts: 8 |
just an FYI, this was the fix
Steps to modify the Registry
⚠️ < Important : Incorrectly modifying the Registry can cause system problems. Always back up the Registry before making any changes.
1. Open the Registry Editor.
Press Win + R, type regedit, then press Enter.
If prompted by User Account Control, click Yes.
2. Access the subkey.
Access: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais
3. Modify the key and set the value.
Within Calais, the option is enabled if the DisableCapiOverrideForRSA key exists.
Double-click on DisableCapiOverrideForRSA.
In the Value Date field, enter: 0
Note : The DisableCapiOverrideForRSA registry setting is NOT added by the default operating system installation or Windows Update installation and must be added manually on each device.
4. Close and restart.
Close the Registry Editor.
Restart your computer for the changes to take effect.
Affected platforms:
Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
Server: Windows Server 2025; Windows Server 23H2; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2
Steps to modify the Registry
⚠️ < Important : Incorrectly modifying the Registry can cause system problems. Always back up the Registry before making any changes.
1. Open the Registry Editor.
Press Win + R, type regedit, then press Enter.
If prompted by User Account Control, click Yes.
2. Access the subkey.
Access: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais
3. Modify the key and set the value.
Within Calais, the option is enabled if the DisableCapiOverrideForRSA key exists.
Double-click on DisableCapiOverrideForRSA.
In the Value Date field, enter: 0
Note : The DisableCapiOverrideForRSA registry setting is NOT added by the default operating system installation or Windows Update installation and must be added manually on each device.
4. Close and restart.
Close the Registry Editor.
Restart your computer for the changes to take effect.
Affected platforms:
Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
Server: Windows Server 2025; Windows Server 23H2; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2