Search results

A few questions to help narrow this down: - Does this error happen every time you run the EXE, or is it random/intermittent? - Have you tried restarting your PC and running the EXE again? - Do you have any antivirus software that might be interfering (Windows Defender, or a third-party one)? -...

What is the Windows version are you running the EXE on?

You should replace the full path in the command line by "{$OUTPUTFILE$}".

We're unable to reproduce the issue. Would it be possible for you to provide us with your EXE file for internal review? Or to create a lite sample that would let us reproduce your problem? Please contact us with PM/DM if you don't want to publicly publish your file(s).

Can you show the entire line you entered in ?

Which Excel version are you using? And XLS Padlock version?

If Windows SDK is now set up, click Global Preferences in XLS Padlock (on code signing page) and let XLS Padlock auto-detect the path to SignTool.exe (click the appropriate button near the path field).

The behavior you describe is consistent with XLS Padlock disabling the Solver add-in when the protected workbook starts. By default, XLS Padlock disables most Excel add-ins in the secured environment for security reasons. Solver is one of the built-in “common Excel add-ins,” so if your workbook...

Are you running some antivirus software or maybe you're running on a virtual PC?

XLS Padlock’s built-in trial mode is based on activation keys. In practice, this means the standard trial workflow requires the user to activate the compiled EXE with a trial key first. The nag screen and the trial state are both linked to that trial-key configuration. You could generate a trial...

Sorry for the delay in replying. We were closed on Sunday, which is why you did not receive an answer yesterday. Regarding your question, the option to create hardware-locked registration keys is disabled in the Pro version you are currently using. This feature is only available in the...

Sure, here is an article that should help you: https://www.vbapadlock.com/blog/vba-padlock-vs-xls-padlock-which-one-do-i-need

Thanks for the clarification. The IsTrial() function is intended to work only when the workbook is running inside the compiled XLS Padlock application, not while testing the original workbook directly in Excel. So in your original workbook, this line: Set XLSPadlock =...

The XLS Padlock free trial is fully functional, allowing you to test it for as long as you need.

Yes — this is absolutely possible and it’s a very common licensing pattern for XLS Padlock applications. The concept is simple: the application starts normally, then VBA checks whether the app is running in trial mode. If it is, a dialog prompts the user to either continue the trial or activate...

The error shown in your screenshot indicates that SignTool.exe cannot be found on your system: This happens because the Microsoft SignTool utility, which is required to digitally sign the EXE file when using the SignTool Commands method, is not installed or its path has not been configured in...

VBA Padlock 2026.1 is here! We're excited to announce the release of VBA Padlock 2026.1 — an update focused on making it easier to compile real-world VBA projects with minimal or no modifications. This release brings Enum support, full error handling, array operations, pattern matching, Unicode...

Answered to your ticket.

The "Invalid code page" error is related to your client's Windows regional/locale settings, not to the Office version itself. This explains why it works on your machines but fails on theirs. The internal spreadsheet engine of XLS Padlock expects certain regional settings (particularly the code...

We'll launch next week our new product and we also got news from the third-party provider for your problem in ExeOutput, so we'll have news next week. Sorry for the delay!