Search results

Short version: that message comes from the activation lookup, not from a broken install, and the reset is done on your side (your WooCommerce server), not from inside the compiled EXE. Why "invalid email - order not found" appears With the WooCommerce Integration Kit, the protected workbook...

Thanks for the report. This is a known issue on our side: it comes from a third-party component on the website, and it is already being addressed. A site update is imminent and ships alongside the upcoming XLS Padlock 2026 release, which clears this up. In the meantime the issue is intermittent...

The Security, Excel Versions tab uses Microsoft's internal Office major version number, not a release year. The full mapping is: 9: Excel 2000 10: Excel 2002 11: Excel 2003 12: Excel 2007 14: Excel 2010 15: Excel 2013 16: Excel 2016, 2019, 2021, 2024, and 365 There is no 17, because Microsoft...

The heserver hostname is hardcoded in the EXE's internal pluggable protocol (https://heserver/, http://heserver/, ghe://heserver/), and it is process-local, two ExeOutput apps running side by side on the same machine each have their own private heserver inside their own process, no collision. So...

Great news! Thanks for the follow-up!

Good to hear that close-and-reopen brings it back. The behaviour you describe (random "Call to OS Function Failed" that disappears on restart of the EXE, with the secondary-process-naming option correctly disabled this time) is consistent with a transient resource conflict rather than a...

Thanks for the detail. The "Just a moment, please..." screen is the launcher's loading state while the bundled PHP-CGI process and the embedded Chromium (or WebView2) browser are being started by the EXE. When 6 PCs out of 40 succeed and the rest hang there, the cause is almost always something...

Glad you sorted it out, and thanks for posting the resolution , this helps the next person who hits the same symptom. For anyone arriving on this thread later: PHP's mbstring extension (which provides mb_convert_encoding, mb_strlen, mb_substr etc.) is disabled by default in ExeOutput for PHP's...

OK. Thanks. If you restart the computer and run your EXE again, does it work?

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...