VBA & Macro Problems

How to Fix Access VBA Project Cannot Be Signed with a Code-Signing Certificate

Huma Ashraf Ch Oct 7, 2026 869 views

Question details

The user is unable to sign a Microsoft Access VBA project using a commercial code-signing certificate, even though the same certificate works perfectly in Microsoft Word.

How to Fix Access VBA Project Cannot Be Signed with a Code-Signing Certificate

Product: Microsoft Access
Device & OS: not provided
Scenario: Attempting to apply a renewed or new commercial OV/EV code-signing certificate (such as Sectigo or Comodo) to a VBA project in Microsoft Access utilizing a secure physical token.
Observed behavior: Microsoft Access rejects the commercial VBA code-signing certificate or fails to recognize it, stopping the user from properly securing and distributing the Access database.

Before you start

Ensure that your physical USB security token is securely plugged into your computer and that you have administrator privileges to install or update middleware drivers.

Solution 1Recommended

Update Token Middleware and SafeNet Drivers

Microsoft Access is highly sensitive to hardware token driver versions. Updating your HSM or USB token middleware (like SafeNet) often resolves signing rejections.

Modern secure-token requirements mean that your private key resides on a physical device. If the middleware bridging this device to Microsoft Office is outdated, Access may fail to read the certificate even if Word succeeds.

Disconnect the token

Safely remove the physical USB code-signing token from your computer.

Uninstall outdated software

Open the Windows Control Panel, navigate to Programs and Features, and uninstall your current SafeNet Authentication Client or equivalent token middleware.

Download the latest middleware

Visit your certificate authority's (e.g., Sectigo, Comodo) or token vendor's official website to download the latest version of the client software.

Install and restart

Install the new middleware and restart your computer to ensure all background services are properly initialized.

Reconnect and test

Plug your USB token back in, open your Access database, navigate to the VBA Editor (Alt + F11), and attempt to apply the digital signature via Tools > Digital Signature.

Update Token Middleware and SafeNet Drivers

Driver Compatibility: Always ensure the middleware version you install explicitly supports the build of Windows and Microsoft Office you are running.

Solution 2

Verify Office Architecture Compatibility (32-bit vs 64-bit)

Mismatched architectures between Microsoft Access and the token drivers can prevent the certificate from loading correctly.

Solution 3

Use SelfCert for Diagnostic Testing

Create a local self-signed certificate to isolate whether the issue lies with Microsoft Access's VBA signing feature itself or with the commercial hardware token.

Free Microsoft Office alternative

Experience a Lighter, Hassle-Free Office Suite with WPS Office

If complex hardware token drivers and VBA macro signing issues in Microsoft Office are interrupting your daily workflow, consider WPS Office for your standard document needs. WPS Office offers a streamlined, lightweight alternative for word processing, spreadsheets, and presentations without the heavy legacy configurations.

Seamless compatibility with Microsoft Office formats including .docx, .xlsx, and .pptxSignificantly lighter and faster to launch than traditional Office suitesFree to download and use with a highly familiar, tabbed user interfaceAvoids complicated hardware token driver conflicts for standard document tasks

microsoft office alternative - wps office

Frequently Asked Questions

Why does my code-signing certificate work in Word but not in Access?

Microsoft Access handles VBA project compilation and signing differently than Word. It is historically more sensitive to HSM (Hardware Security Module) token drivers and middleware versions (like SafeNet), which can cause the signing process to fail in Access while succeeding in Word.

What is a secure-token requirement for code-signing certificates?

Modern industry standards require that the private keys for commercial code-signing certificates (OV and EV) be stored on a secure physical USB token or Hardware Security Module. This prevents unauthorized duplication but requires specialized middleware drivers to function with Office.

Can I use a self-signed certificate for commercial Access databases?

No. While you can use the built-in SelfCert tool to sign a database for local testing, self-signed certificates are not trusted by other computers. Users opening your database on different machines will still receive severe security warnings or have the macros blocked.

Excel & Data Problems