Search results

Please, can you check whether the option is not enabled again after switching the engine?

Thanks for the great feedback! On the diagnosis itself You are right, and the misleading error message is what makes this nasty. The FILTER_SANITIZE_STRING is deprecated message is emitted by some other component in the same PHP request lifecycle (typically WordPress itself in 6.7+, or one of...

Thanks for the final feedback and yes, we'll add a refresh too without having to change the method. Great that it works for you now!

Paquet Builder 2026.1 — What's Updated Paquet Builder 2026.1 is out. This is a maintenance release for the 2026 line that resolves two regressions from 2026.0 and adds a couple of small runtime improvements. Fixes from 2026.0 Multi-volume extraction returning error -5 (can't open archive) —...

Note that it's already available in HTMLEXE see https://www.htmlexe.com/help/topics/codesigning.html ;) And it's scheduled for ExeOutput 2026. Both new major releases with lots of new features to come ☺️

When you click the Auto button next to the Azure Trust Signing dlib field (or when XLS Padlock probes the DLL automatically before signing), it looks in the old per-user location used by the legacy Microsoft.Trusted.Signing.Client package...

Could you please try: https://download.exeoutput.com/tmp/EXORun1D.7z Once downloaded, follow these steps: 1) Extract the EXORun.dat file from the archive. 2) Move it into the CEFRuntime subfolder inside your ExeOutput for PHP installation directory, replacing the existing file. 3) Restart...

Do you mean the activation key for end users or the activation token? BTW here is a working demo to show you how this works: https://demo.xlspadlock.com

Now that Paquet Builder 2026 is out, an intermediate fix for your issue is coming soon ;)

The function you're calling, XLSPL_GetActivationKey, does not exist in XLS Padlock — that's why Application.Run returns nothing. The same applies to names like XLSPL_GetLicenseExpirationDate. Copilot has likely invented them. The real VBA API is exposed through the GXLSForm.GXLSFormula...

Antes de nada, hay una confusión sobre las opciones que Copilot te ha indicado. Las casillas "Enable XLS Padlock VBA API" y "Expose VBA API via PLEval" no existen como tales en XLS Padlock 2025.2, y tampoco hay ningún fichero XLSPadlock.exe independiente que haya que activar...

Short answer: "Trial Days" in the XLS Padlock desktop UI and keymaxdays in the Woo Integration Kit's workbooks.json are the same field. They both set the maximum number of days the key remains valid from the date of first activation. "Display the nag screen" in the...

Thanks for sharing this data point! We've seen similar file-dialog crashes pinned on Norton's behavioral/exploit protection intercepting the Excel process when the Windows common dialog is spawned from inside a protected EXE. For anyone hitting this in the future, the usual fixes on the...

Paquet Builder 2026 — What's New We’re pleased to announce that our Windows installer and Self-Extracting archive creator Paquet Builder 2026 is out. Here's a rundown of the additions available in this major release: AI Assistant & MCP Server The IDE now includes an AI assistant that accepts...

OK, thanks for the extended testing. We'll focus on CEF then.

The syntax heexternal:// followed by a full URL should work correctly for opening external links in the user's default browser. Your code looks correct in principle: <a href="heexternal://https://411center.com/r/exeoutput-magicai">...</a> A few things to check: 1. Test with a simple text...

Glad to hear the issue is resolved! That setting is related to how secondary processes are named. It is mainly intended for companies with strict security rules regarding allowed processes. Since everything works correctly without it, we recommend keeping it disabled for your project.

Did disabling that option fix the issue? Please let us know if the error still occurs after unchecking it and rebuilding your EXE.

Could you check if the following option is enabled or not in your ExeOutput project?

When you use the SignTool Commands method in XLS Padlock, you should not type the actual path to your EXE file in the command line. Instead, use the placeholder {$OUTPUTFILE$} — XLS Padlock will automatically replace it with the real path to your compiled EXE at build time. For example, if your...