Follow this step-by-step guide to get started.

Step 1: Launch the Application

When you start VBA Compiler for Excel for the first time, you will be greeted by the Trial Mode Activation dialog box.

1.  Locate the Email Address field.

2. Enter the email address where you would like to receive your trial activation code.

3. Confirm your email address by re-typing it in the confirmation field directly below.

Once both fields match, the grayed-out Continue button will become active. Click Continue to proceed to the next step.

Step 2: Retrieve Your Activation Code

After clicking Continue, a new dialog window will appear asking for your activation code.

1. Open your email client and look for a message with the subject line:

Subject: Your VbaCompiler for Excel Trial Activation Code

From: support@doneex.com

2. Open the email and locate your unique activation code (usually found on the last line).

Tip to Copy: In most email clients, you can double-click the code line to select it entirely, then right-click and choose Copy (or press Ctrl + C).

Step 3: Enter the Code and Activate the Free Trial Mode

Return to the VBA Compiler dialog window.

1. Paste your copied code into the Trial Activation Code input field (right-click and choose Paste, or press Ctrl + V).

2. Click the Apply button.

Success! You have completed the activate free trial mode procedure!

Once the system validates your code, a confirmation message will appear: “Trial Mode is activated.”

Note on Evaluation: Your 14-day evaluation period begins immediately. You now have access to compilation functionality to test and evaluate the product’s capabilities.

If you encounter any issues receiving your activation code, please check your Spam/Junk folder or reach out to our support team at support@doneex.com.

The post How To Activate Free Trial Mode appeared first on VbaCompiler for Excel.

Whether you are upgrading, troubleshooting a backend environment issue, or clearing space on your system, removing VbaCompiler for Excel is a straightforward process. Because the VBA compiler relies on external backend C-compilers and local registry entries to manage compilation tasks, following an appropriate uninstall method is necessary to ensure no residual data fragments conflict with future Excel installations.

Step by Step Guide

This guide covers the several automated removal methods that you can use to uninstall the VBA compiler.

Method 1: The Recommended Windows Start Menu Route

The quickest and most reliable way to remove VbaCompiler for Excel is by utilizing the dedicated uninstaller package provided directly by DoneEx.

1. Close all active instances of Microsoft Excel and save your work.
2. Click on the Windows Start button or press the Windows Key on your keyboard.
3. Scroll through your applications list or search for the DoneEx folder.
4. Expand the DoneEx folder and locate VbaCompiler for Excel.
5. Click on Uninstall.
6. A Windows User Account Control (UAC) prompt may appear. Click Yes to allow the uninstaller to run.
7. Follow the on-screen wizard prompts to safely remove the software components.

Method 2: Uninstalling VBA Compiler via the Windows Control Panel / Settings

If you cannot locate the shortcut link in your Start Menu, you can remove the application through the centralized Windows software manager.

For Windows 10 & 11:

1. Press Windows Key + I to open the Windows Settings menu.
2. Navigate to Apps > Installed apps (or Apps & features).
3. In the search bar, type VbaCompiler or DoneEx.

1. Click the three dots (…) next to the software name and select Uninstall.
2. Confirm your choice and let the wizard complete the uninstall process for the VBA compiler.

For Legacy Systems (Control Panel):

1. Open the Windows Run dialog by pressing Windows Key + R, type control, and press Enter.
2. Click on Programs and Features (or Add/Remove Programs).
3. Scroll through the alphabetically organized list until you find DoneEx VbaCompiler for Excel.
4. Highlight the entry and click the Uninstall/Change button at the top of the interface.

Need to reinstall or upgrade? Visit the official VbaCompiler for Excel download page to pull down the newest version.

The post How To Uninstall VBA Compiler for Excel appeared first on VbaCompiler for Excel.

If you have ever built an automated Excel workbook only to have a user call you saying, “Your file isn’t working,” you already know the culprit: Microsoft Excel’s dreaded “Security Warning: Macros have been disabled” banner. To protect users from malicious software, Excel blocks unsigned macros by default. While this protects workstations from security threats, it creates friction for legitimate tools built by financial analysts, developers, and automation engineers. The solution is VBA code signing. A VBA digital signature acts as an official seal of authenticity for your macros, removing security warnings, establishing trust, and verifying that your code hasn’t been tampered with.

This complete guide breaks down everything you need to know about Excel macro certificates, setting up digital signatures, and establishing a complete security strategy for your VBA projects.

What Is a VBA Digital Signature & How Does It Work?

A VBA digital signature is a cryptographic seal attached to your Visual Basic for Applications (VBA) project. It converts an unverified macro file into a trusted document.

When you sign a VBA project, your digital certificate creates two key guarantees:

1. Identity (Authenticity): It proves to Excel and your users exactly who authored the code.

2. Integrity (Tamper Prevention): It guarantees that no one has modified, corrupted, or altered a single line of code since you signed it.

 Choosing Your Certificate for VBA: Self-Signed Digital Signature vs. Commercial CA

Before you can digitally sign a macro project in Excel, you need an Excel macro certificate. You have two choices depending on your audience:

Option A: Self-Signed Certificates (SelfCert.exe)

Microsoft Office includes a free utility called SelfCert.exe. It generates a local digital certificate stored in your personal Windows Certificate Store.

• Use case: Personal productivity scripts, testing, or files used exclusively on your own workstation.

• Limitation: If you email a workbook signed with a self-signed certificate to a colleague, their computer will treat it as untrusted because their system does not possess your private certificate key.

Option B: Commercial Code Signing Certificates

For distributing macro-enabled workbooks to clients, external stakeholders, or company-wide networks, you need a certificate issued by a trusted Certificate Authority (CA) such as DigiCert, Sectigo, or SSL.com.

• Use case: Commercial Excel applications, enterprise add-ins (.xlam), and client-facing tools.

• Advantage: Public CAs are automatically trusted by Windows and Microsoft Office, allowing your macros to run smoothly on any workstation worldwide.

Step-by-Step Guide: How to create a Digital Signature for a VBA Project

Applying a VBA code signing certificate to an Excel workbook takes less than two minutes once you have a valid certificate installed.

Step 1: Create or Install Your Certificate

• For Testing (Self-Signed): Press Win + R, type C:\Program Files\Microsoft Office\root\Office16\SELFCERT.EXE (path varies by Office version), enter a certificate name, and click OK.

• For Production: Install your .pfx or hardware token certificate provided by your Certificate Authority into the Windows Personal Certificate Store.

Step 2: Open the VBA Editor

1. Open your macro-enabled workbook (.xlsm, .xlsb, or .xlam).

2. Press Alt + F11 to launch the Visual Basic Editor (VBE).

Step 3: Attach the Certificate

1. In the VBE top menu, select Tools > Digital Signature…

2. In the dialog box that appears, click the Choose… button.

3. Select your desired certificate from the list and click OK.

4. You will see your certificate details displayed in the dialog. Click OK to apply it.

Step 4: Save the Workbook

Return to the main Excel window and save the file (Ctrl + S). The digital signature is now embedded directly into the document structure.

Pro-Tip: Timestamp Your Code Signatures By default, a digital signature becomes invalid the moment your digital certificate expires (usually after 1–3 years). By configuring a Timestamp Server URL in your Windows Registry (RFC 3161 Timestamping), Excel verifies that the code was signed while the certificate was valid, allowing your trusted VBA macros to keep running long after the certificate itself expires.

Excel Trust Center Settings & Enterprise Deployment

To maximize the benefits of code signing, you must configure how Excel handles macro execution.

Configuring Excel Trust Center Settings

In Excel, navigate to File > Options > Trust Center > Trust Center Settings > Macro Settings.

The recommended setting for security-conscious organizations is:

• Disable all macros except digitally signed macros

Under this setting:

• Unsigned macros are completely blocked without prompting the user.

• Macros signed with a valid, trusted Excel macro certificate run automatically without warnings.

• Macros signed by a new or unrecognized publisher display a one-time prompt asking the user to trust the publisher.

Enterprise Deployment via Group Policy (GPO)

System Administrators managing enterprise environments can deploy public certificates silently across all employee machines:

1. Export the public root certificate (.cer) of your organization’s internal or commercial signing authority.

2. Push the certificate to employee workstations using Group Policy Management (GPO) under: Computer Configuration > Policies > Windows Settings > Security Settings > Public Key Policies > Trusted Publishers

3. Once deployed, any workbook signed with that certificate executes seamlessly across the entire corporate network.

Code Signing vs. Code Protection: Building a Complete Security Strategy

A common myth among developers is that applying a VBA digital signature protects your intellectual property from being viewed or stolen. It does not.

Understanding the difference between Code Signing and Code Protection is critical for protecting your work:

• Code Signing (Trust): Proves author identity and integrity. It verifies code integrity by confirming who wrote the code and that the code hasn’t been modified or tampered with. While it eliminates Excel macro security warnings, the underlying VBA source code remains completely visible and editable if someone opens the VBE.

• Code Protection (Security): Obfuscates, encrypts, or compiles the source code into native binary dynamic link libraries (.dll). This prevents competitors, clients, or end-users from inspecting, copying, or reverse-engineering your intellectual property.

To achieve complete commercial security, combine both techniques: protect your underlying algorithms using compilation tools like VBA Compiler to convert your macros into secure binaries, and then apply a VBA digital signature to ensure smooth distribution and trusted execution.

Frequently Asked Questions (FAQ) about VBA Digital Signature

Why does my VBA digital signature disappear when I edit my code?

A digital signature relies on a cryptographic hash of your exact VBA code. Editing even a single line, comment, or space changes the code hash. To prevent unauthorized tampering, Excel automatically invalidates and removes the signature whenever modifications are saved. You must re-apply the signature after making edits.

How do I fix the “Signature Removed” warning in Excel?

If Excel reports that a signature was removed or is invalid, check three things:

1. The code was modified after it was signed.

2. The signing certificate has expired and was not timestamped during signing.

3. The certificate authority that issued the signature is not installed in your computer’s Trusted Root Certification Authorities store.

Does code signing bypass Windows “Mark of the Web” (MOTW)?

Files downloaded directly from the internet or received as email attachments carry a Windows “Mark of the Web” flag that may cause Excel to open them in Protected View. While a digital signature establishes publisher trust, users may still need to click “Unblock” in the file’s properties window once before opening, or save the file to an Excel Trusted Location.

The post Create a Digital Signature for Excel VBA Projects appeared first on VbaCompiler for Excel.

Digitally signing your Visual Basic for Applications (VBA) macro project builds trust, prevents security pop-up warnings, and ensures your code hasn’t been tampered with. Adding a timestamping service when you apply your digital signature ensures your macros remain valid even after your code signing certificate expires.

What Is a Timestamping Service and Why Is Applying a Digital Signature with it Necessary?

When you sign a macro without a timestamp, the digital signature is tied directly to the current certificate’s validity period (usually 1 to 3 years). Once the certificate expires, Microsoft Office marks the signature as invalid and alerts users.

A Timestamp Authority (TSA) acts as an independent cryptographic notary. It verifies that the macro was signed while the certificate was active and valid. This guarantees long-term validity—your macro will stay trusted indefinitely as long as the underlying code remains unchanged.

Step 1: Configure Windows Registry for Timestamping

Unlike standard executable signers, the Office Visual Basic Editor (VBE) does not have a timestamping option in its user interface. Instead, it checks specific Windows Registry keys during the signing process.

Option A: Automatic Registry Setup (Recommended)

1. Press Win + R, type cmd, and press Enter to open the Command Prompt.

2. Copy and paste the following commands to add your preferred Timestamping Server URL (replace the URL with your CA’s timestamp server if using a different authority):

 
reg add "HKCU\Software\Microsoft\VBA\Security" /v "TimeStampURL" /t REG_SZ /d "http://timestamp.digicert.com" /f reg add "HKCU\Software\Microsoft\VBA\Security" /v "TimeStampRetryCount" /t REG_DWORD /d 3 /f reg add "HKCU\Software\Microsoft\VBA\Security" /v "TimeStampRetryDelay" /t REG_DWORD /d 3 /f
 

Option B: Manual Registry Setup

1. Press Win + R, type regedit, and press Enter.

2. Navigate to:

   HKEY_CURRENT_USER\Software\Microsoft\VBA\Security

3. Create three entries inside the Security key:

Common Timestamp Server URLs:

• DigiCert: http://timestamp.digicert.com

• Sectigo / Comodo: http://timestamp.comodoca.com/authenticode

• GlobalSign:  http://timestamp.globalsign.com/tsa/r45standard

Step 2: Apply the Digital Signature in Office (VBE) With Timestamping

Once the registry keys are configured, apply the signature in your macro-enabled workbook or document (.xlsm, .docm, .pptm).

1.Open the Visual Basic Editor:

Open your macro-enabled document (Excel, Word, etc.). Press Alt + F11 (or go to Developer > Visual Basic) to launch the editor.

2.Select Your VBA Project:

In the Project Explorer pane on the left, click on the project name corresponding to your file.

3.Open the Digital Signature Window:

On the top menu bar, click Tools > Digital Signature

4.Choose Your Code Signing Certificate:

Click Choose… to bring up your installed personal or hardware token certificates. Select your active Code Signing Certificate and click OK.

5.Apply Signature with Active Internet Connection:Internet connection is strictly required for this step.

Ensure your machine is connected to the internet. Click OK in the Digital Signature dialog. The editor will communicate with the timestamping server automatically via the configured registry URL.

6.Save the Document:

Press Ctrl + S or save the file directly within Office. This writes both the digital signature and the timestamp counter-signature into the file structure.

Step 3: Verify the Timestamp and Digital Signature

1. Go back to Tools > Digital Signature… in the Visual Basic Editor.

2. Click Detail… on the attached certificate.

3. Select the Advanced or Countersignatures tab (depending on your Windows version). You should see a timestamp entry listing the exact date and time the server countersigned your macro project.

Best Practices and Troubleshooting

• Active Internet Connection Required: If the Visual Basic Editor cannot reach the TimeStampURL, the signing process may time out or revert to a simple signature without a timestamp.

• Avoid Self-Signed Certificates for Distribution: Tools like SelfCert.exe create self-signed certificates that work locally but are untrusted on external workstations. For commercial or enterprise distribution, use a publicly trusted Certificate Authority (DigiCert, Sectigo, GlobalSign).

• RFC 3161 Protocol Note: Note that Microsoft Office VBA uses legacy Authenticode timestamping mechanisms rather than RFC 3161 protocols.Ensure you use the standard Authenticode endpoint URL provided by your Certificate Authority.

Explore Also:

Create a Digital Signature for Excel VBA Projects

The post Apply Digital Signature with a Timestamping Service appeared first on VbaCompiler for Excel.

Converting a standard VBA macro into an Excel add-in (.xlam file) allows you to run your custom tools across any workbook without copying code, cluttering spreadsheets, or relying on personal macro workbooks. If you want to create an Excel add-in from a VBA macro, this guide will walk you through the entire process step by step—from preparing your code to installing your custom .xlam file in Excel.

Why Create an .xlam File in Excel?

Standard .xlsm workbooks tie your VBA code to a single file. In contrast, an Excel Add-In (.xlam) operates quietly in the background every time Excel opens.

• Global Accessibility: Use your custom macros on any open spreadsheet without switching files.

• Cleaner Workbooks: Distribute functionality without embedding code into client or team files.

• Easy Updates: Updating one .xlam file automatically updates the macro for every linked user.

Step-by-Step Walkthrough to Turn a VBA Macro into an Add-In

1.Prepare and Test Your VBA Macro:Ensure your code runs independently of specific sheet names.

Before you make an Excel add-in, verify that your VBA code works without relying on a specific active worksheet name unless intended.

1. Open Excel and press Alt + F11 to open the VBA Editor.

2. Insert a standard module (Insert > Module).

3. Paste or write your macro code.

4. Replace references like Sheets("Sheet1") with ActiveSheet or dynamic workbook references so your code works across any active file.

5. Test your macro inside a standard sheet (Alt + F8) to ensure it executes cleanly without runtime errors.

2.Configure Workbook Properties:Provide a name and description for the Excel Add-in manager.

Setting metadata helps Excel identify your tool when users view their installed add-ins list.

1. In the VBA Editor (Alt + F11), locate the Properties pane (press F4 if hidden).

2. Select ThisWorkbook in the Project Explorer (Ctrl + R).

3. Change the IsAddin value to true.

4. Save your changes

3.Save as an Excel Add-In (.xlam):Export your workbook into the .xlam format.

To create a .xlam file in Excel, you need to save the file under the proper add-in format.

1. Return to the main Excel sheet and click File > Save As.

2. Click Browse and open the Save as type dropdown menu.

3. Select Excel Add-In (*.xlam).

4. Excel will automatically redirect the file path to your local AddIns directory (e.g., C:\Users\<User>\AppData\Roaming\Microsoft\AddIns). Note: You can save it here or choose a shared network folder for team access.

5. Enter a clear file name and click Save.

4.Install and Activate the Add-In in Excel:Enable your newly created add-in.

Once saved, you must activate the add-in within Excel to make your macros available globally.

1. In Excel, go to File > Options > Add-ins.

2. At the bottom of the window, ensure Manage: Excel Add-ins is selected and click Go…

3. Check the box next to your new add-in in the list.

4. If your file isn’t listed, click Browse…, navigate to your saved .xlam file, and select it.

5. Click OK. Your add-in is now active across all open and future Excel workbooks.

Best Practices for Managing Excel Add-Ins

When you create an Excel VBA add-in for wider distribution or personal efficiency, keep these three practices in mind:

1. Adding Ribbon or Menu Controls

Because .xlam files hide their sheet interface when loaded, users won’t see a standard sheet to click buttons. Use custom Ribbon XML or add macro shortcuts to the Quick Access Toolbar (QAT) so users can trigger your code with a single click.

2. Handling File Path Permissions

If you share your .xlam file with colleagues, ensure they save it to their local AddIns folder or a shared network drive where they have read/write permissions.

3. Protecting Your Source Code

VBA project password protection prevents unauthorized edits, but standard VBA passwords can be easily bypassed. If you are distributing proprietary business logic or commercial tools, consider compiling your VBA code into a native dynamic link library (.dll) or executable using dedicated tools to secure your intellectual property.

Explore Also:

How to Protect and License Excel Add-In from Being Pirated or Shared

The post How to Create an Excel VBA Add-In: A Step-by-Step Guide appeared first on VbaCompiler for Excel.

In this guide, we will break down what self-signed certificates are and walk through three simple ways to generate them on Windows.

What Is a Self-Signed Digital Certificate?

A digital certificate links an identity (you or your business) to a pair of cryptographic keys. When you attach this certificate to an Excel workbook (.xlsm or .xlsb) or a local web server, it guarantees two things:

1. Authenticity: The code or project came from you.

2. Integrity: The code has not been altered or corrupted since it was signed.

Standard certificates are issued by a trusted Third-Party Certificate Authority (CA) like DigiCert or Sectigo. A self-signed certificate, on the other hand, is created and signed by you.

Differences between Comercial and Self-Signed Certificates

Commercial CA Certificate

• Issued by a trusted third party
• Costs $100–$500+ per year
• Works globally on any computer
• Best for public software / websites

Self-Signed Certificate

• 100% Free
• Ideal for local dev & internal
• Best for VBA macros & testing

While self-signed certificates are not meant for public software distribution, they are the single best way to generate a self-signed SSL certificate for free when building local projects or running personal Excel tools.

Method 1: Create a Certificate for Excel VBA Using SELFCERT.EXE

If your goal is to stop Microsoft Excel from blocking your VBA macros, Microsoft provides a built-in utility called SELFCERT.EXE. This is the easiest method for Excel users.

Step 1: Locate SELFCERT.EXE

1. Open Windows File Explorer.

2. Navigate to your Microsoft Office installation folder. The standard location for modern 64-bit Office installations is: c:\Program Files (x86)\Microsoft Office\root\Office16\

3. Scroll down and double-click SELFCERT.EXE.

Step 2: Create Your Certificate

1. When the tool opens, a dialog box will ask for a Your Certificate Name.

2. Type a clear name, such as My Local VBA Cert or Developer Cert - John Doe.

3. Click OK. You will see a success message stating that your certificate was created.

Step 3: Sign Your Excel VBA Project

1. Open your macro-enabled Excel workbook (.xlsm).

2. Press ALT + F11 to open the VBA Editor.

3. Click Tools in the top menu, then select Digital Signature…

4. Click Choose…, select the certificate you just created, and click OK.

5. Save your workbook. Your VBA project is now digitally signed!

Method 2: Generate a Self-Signed Certificate via PowerShell

Windows PowerShell includes a native command that lets you generate robust digital certificates in seconds. This method is great if SELFCERT.EXE is missing from your Office installation.

Step 1: Open PowerShell as Administrator

1. Press the Windows Key, type PowerShell.

2. Right-click Windows PowerShell and select Run as administrator.

Step 2: Run the Creation Command

Copy and paste the following command into PowerShell and press Enter:

New-SelfSignedCertificate -Type CodeSigningCert -Subject "CN=MyLocalCodeCert" -CertStoreLocation "Cert:\CurrentUser\My"

This creates a new Code Signing Certificate named MyLocalCodeCert and stores it safely in your Windows Certificate Store. It will immediately appear in Excel’s Tools > Digital Signature menu.

Method 3: Create a Self-Signed SSL Certificate for Local Development

If you are developing local web applications or testing local web servers alongside your tools, you may need an SSL/TLS certificate. You can easily create a self-signed SSL certificate for local development using OpenSSL.

If you have OpenSSL installed (via Git Bash, WSL, or Windows binaries), run this single-line command in your terminal:

openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout local.key -out local.crt -subj "/CN=localhost"

What this command does:

• -x509: Specifies that you want a self-signed certificate instead of a certificate signing request (CSR).

• -nodes: Skips password-protecting the private key (ideal for automated local test servers).

• -days 365: Sets the certificate validity to 1 year.

• -newkey rsa:2048: Generates a secure 2048-bit RSA key pair.

• -keyout & -out: Saves your private key (local.key) and public certificate (local.crt).

How to Make Windows Trust Your Self-Signed Certificate

Because Windows did not issue this certificate through a recognized public root authority, it will mark it as “Untrusted” by default. To fix this on your local machine, you need to import it into your Trusted Root Store.

1. Press Windows Key + R, type certmgr.msc, and hit Enter.

2. Expand the Personal > Certificates folder on the left side.

3. Locate the certificate you created (e.g., My Local VBA Cert or MyLocalCodeCert).

4. Right-click the certificate and select Copy.

5. On the left side, expand Trusted Root Certification Authorities.

6. Right-click the Certificates sub-folder and select Paste.

Once pasted, Windows will fully trust your custom certificate, and Excel will load your signed macro workbooks without displaying any security warnings.

Self-Signed Certificates vs. VBA Compiler: Complete Code Protection

Creating a free self-signed certificate solves the identity problem: it tells Excel that you wrote the code and that no one altered it. However, it is important to understand what a digital certificate does not do:

• It does not encrypt your VBA code.

• It does not hide your intellectual property.

• It does not prevent someone from viewing or copying your source code.

Anyone who opens your .xlsm file can still access the Visual Basic Editor (ALT + F11) and read your proprietary formulas, macros, and business logic.

Taking Security to the Next Level

If you want to protect your hard work, proprietary algorithms, or commercial Excel tools from reverse engineering, signing your project is only the first step.

For full protection, consider compiling your VBA macros into native C code and binary DLL files using VBA Compiler. By converting your VBA code into a compiled DLL, you eliminate the source code entirely from the workbook—making it impossible for users to steal, modify, or crack your IP while keeping your Excel files running smoothly and securely.

Summary

Setting up a free self-signed certificate is a simple, effective way to streamline your workflow in Excel and local development environments:

1. Use SELFCERT.EXE for quick Office macro signing.

2. Use PowerShell for flexible Windows-native code signing.

3. Use OpenSSL to generate SSL certificates for local server testing.

4. Always import your certificate into the Trusted Root Certification Authorities store so Windows accepts it without warnings.

Combine digital signatures with native compilation to keep your Excel applications both seamless to run and completely secure!

The post How to Create Free Self-Signed Digital Certificate appeared first on VbaCompiler for Excel.