Signing Error - Code 0x800B010A

I have a valid Code Signing certificate. I've used it for years to sign XLS Padlock .exe compiled programs, and until the past few days had no problems signing using the thumbprint option in XLS Padlock. It's now erroring. I've updated Windows 11, all looks good, and I can use the certificate to sign the VBA code within Excel (it is finding the valid correct certificate). The error seems limited to XLS Padlock. It's an absolutely awesome program, and I'm looking forward to resolving so I can distribute an update to our customers.

[12/02/2026 2:20:35 PM] XLS Padlock 2024.3 Compilation Started
[12/02/2026 2:20:35 PM] - Excel File: C:\Work\Test11-2-26.xlsx
[12/02/2026 2:20:35 PM] - Output Path: C:\Work\Test11-2-26.exe
[12/02/2026 2:20:35 PM] - Application Packaging Option: Standalone EXE
[12/02/2026 2:20:35 PM] - Build EXE for Excel: 32-bit and 64-bit (two separate EXE files)
[12/02/2026 2:20:35 PM] Warning: no formula configured to be protected. XLS Padlock detected that you did not choose any cell in your workbook to protect with XLS Padlock's formula protection. Although this feature is not mandatory, we strongly recommend you to use XLS Padlock's formula protection to secure some of your workbook's cells, especially important formulas
[12/02/2026 2:20:35 PM] Please wait while creating your secure application...

[12/02/2026 2:20:35 PM] Applying formula protection to workbook...
[12/02/2026 2:20:35 PM] 0 formula(s) were protected
[12/02/2026 2:20:35 PM] Generating protection files and final EXE
[12/02/2026 2:20:37 PM] Final cleanup...
[12/02/2026 2:20:37 PM] XLS Padlock 2024.3 Compilation Started
[12/02/2026 2:20:37 PM] - Excel File: C:\Work\Test11-2-26.xlsx
[12/02/2026 2:20:37 PM] - Output Path: C:\Work\Test11-2-26.exe
[12/02/2026 2:20:37 PM] - Application Packaging Option: Standalone EXE
[12/02/2026 2:20:37 PM] - Build EXE for Excel: 32-bit and 64-bit (two separate EXE files)
[12/02/2026 2:20:37 PM] Warning: no formula configured to be protected. XLS Padlock detected that you did not choose any cell in your workbook to protect with XLS Padlock's formula protection. Although this feature is not mandatory, we strongly recommend you to use XLS Padlock's formula protection to secure some of your workbook's cells, especially important formulas
[12/02/2026 2:20:37 PM] Please wait while creating your secure application...
- 64-bit version this time.

[12/02/2026 2:20:37 PM] Applying formula protection to workbook...
[12/02/2026 2:20:37 PM] 0 formula(s) were protected
[12/02/2026 2:20:37 PM] Generating protection files and final EXE
[12/02/2026 2:20:40 PM] Final cleanup...
[12/02/2026 2:20:40 PM] Done
[12/02/2026 2:21:28 PM] GSignCode 3.0 -- simple code signing utility
[12/02/2026 2:21:28 PM] Copyright G.D.G. Software 2011-2024. All rights reserved.
[12/02/2026 2:21:28 PM]
[12/02/2026 2:21:29 PM] Certificate Subject Name: E=[email protected], CN=7D Team Pty Ltd, OU=Engineering, O=7D Team Pty Ltd, STREET="25 Spencer St, Cockburn Central", L=Perth, S=Western Australia, C=AU, OID.1.3.6.1.4.1.311.60.2.1.3=AU, SERIALNUMBER=616 258 336, OID.2.5.4.15=Private Organization
[12/02/2026 2:21:29 PM] Issuer: CN=GlobalSign GCC R45 EV CodeSigning CA 2020, O=GlobalSign nv-sa, C=BE
[12/02/2026 2:21:29 PM] Serial Number: 48D0852C992A35F44532F435
[12/02/2026 2:21:29 PM]
[12/02/2026 2:21:29 PM] Signing C:\Work\Test11-2-2664.exe
[12/02/2026 2:21:29 PM] SIGNING ERROR:
[12/02/2026 2:21:29 PM] Signing Error - Code 0x800B010A
[12/02/2026 2:21:29 PM] ERROR Application was not signed, an error occurred.

Thank you for the detailed log — that's very helpful.

The error code 0x800B010A means "A certificate chain could not be built to a trusted root authority." This is not an issue with XLS Padlock itself, but rather with how Windows is currently validating your certificate chain. The fact that you can sign VBA code inside Excel is expected — Excel uses a different signing mechanism that doesn't perform the same chain validation as Authenticode signing (which is what GSignCode/SignTool uses for .exe files).

This is very likely related to a recent Windows 11 update. Microsoft has been rolling out changes to its root and intermediate certificate stores as part of its Secure Boot certificate refresh (January/February 2026 updates). These updates can sometimes disrupt the certificate trust chain for code signing.

Here are the steps to resolve this:

1. Ensure the GlobalSign intermediate certificate is installed
Your certificate is issued under "GlobalSign GCC R45 EV CodeSigning CA 2020." Open certmgr.msc (Current User) and certlm.msc (Local Machine) and verify that this intermediate CA certificate is present under "Intermediate Certification Authorities > Certificates." If it's missing, download it from GlobalSign's support page:

2. Update your root certificates
Make sure your machine has internet access and run the following in an elevated Command Prompt:
Then import the file into the Trusted Root Certification Authorities store.

3. Clear the SSL state
Open Internet Options (inetcpl.cpl) > Content tab > click "Clear SSL state."

4. Verify the full chain
Open your certificate from certmgr.msc, go to the Certification Path tab, and confirm that every certificate in the chain shows as valid — from your EV cert up through the GlobalSign intermediate to the GlobalSign root.

5. As a workaround
XLS Padlock 2025.2 added support for using Microsoft's standard SignTool instead of GSignCode. If the above steps don't resolve the issue, switching to SignTool in XLS Padlock's settings may work since it can handle chain resolution differently.