Search results

Paquet Builder 2026.3 is now available. This release is all about polish. Instead of piling on new features, 2026.3 sharpens the parts you touch every day: the custom action editor gets a proper modern makeover, on-screen text finally behaves on high-resolution displays, and a nagging crash on...

Good news first: the earlier "EXE not found" is gone, your build now produces the .exe, so we are past that. What is failing now is the Azure signing step itself, and the line in your log is the key: Microsoft.Identity.Client.Extensions.Msal.MsalCachePersistenceException: Persistence check...

For a repeatable test loop, the tool that fits your goal best is not registry deletion at all, it is a disposable environment. Two good options, easiest first: Windows Sandbox (a free feature on Windows Pro and Enterprise). It gives you a clean, throwaway Windows session. Install your Paquet...

Let us separate the pieces, because the "capture and display the key so the user can copy it" step is the part sending you down the wrong path. The 405. The /getactivation/ route only accepts POST. Opening it in a browser is a GET, so the kit correctly answers 405 Method Not Allowed. That is...

You are reading it correctly. If "End users must enter an activation key in order to use the protected workbook" is left unchecked, the compiled app has no licensing at all and runs indefinitely. There is no separate keyless "trial period" switch that later flips the app into requiring...

Before anything else, please check one thing, because it decides the rest: the processor architecture of the machine. XLS Padlock protected applications require 64-bit Windows on an Intel or AMD (x64) processor. They do not currently support Windows on ARM, and on an ARM machine the protection...

XLS Padlock compiles your Excel workbook into a native 64-bit Windows application (a Windows .exe). That format runs on Windows only, so the compiled .exe will not run directly on macOS, even when the project has no external links or DLLs. This is by design: the protection layer and the embedded...

XLS Padlock 2026.1 is now available We have released XLS Padlock 2026.1, a maintenance update for the 2026.0 version shipped last month. It clears up a few issues reported in protected applications built with 2026.0, makes the Web Update feature noticeably more dependable, and irons out several...

"Sign EXE File Now" only signs an .exe that already exists in your project's output folder. It does not build it. The message "The EXE file was not found: please first compile the workbook" means XLS Padlock did not find a compiled .exe there when you clicked Sign. Two checks, in order: Build...

Confirmed: this is a regression introduced in Paquet Builder 2026.2. The "Restart Computer" custom action stops rebooting after a rebuild in 2026.2, while installers built with earlier versions are unaffected. It is now fixed on our side. A hotfix is available. If you have already emailed...

One clarification on the engine first, because it changes which of your ideas are reachable now versus later. ExeOutput for PHP's internal browser is WebView2-based, so you are right that WebView2 is the relevant platform here. The catch is that the specific pieces you cite...

For this, use XLS Padlock's own Deactivation feature rather than trying to delete the activation entries from the registry by hand. Deactivation is the supported way to remove an activation from a machine: it clears the local activation cleanly so you can re-run the trial and activation flow...

Both the key and the token are handled automatically by the Kit, and you do not write a wp-activation.php yourself. Key generation is automatic and on demand. There is no pool of keys to pre-create. When the app activates, the Kit generates the activation key server-side at that moment, from...

The 405 first, because it is the quickest to clear: the /getactivation/... route only accepts POST. A browser address bar sends a GET, so the Kit correctly answers "405 Method Not Allowed". That is not a sign that your id or your config is wrong, it is simply the endpoint refusing a GET...

A build that sits at a fixed percentage (80% here) for tens of minutes almost always means something outside XLS Padlock is stalling that step, not XLS Padlock itself looping. The 80% region is where the compiled EXE is protected and, if you enabled it, code-signed, which is exactly where an...

XLS Padlock 2026 is now available We have released XLS Padlock 2026, the new major version of our Excel workbook protection software. This release modernizes the core of the product and puts you back in control of what new AI features can do with a protected workbook. Three long-standing...

That is exactly right, and thanks for posting the solution. OnPubBeingClosed is the correct event for this, and OpenFile with an https URL opens it in the user's default browser. One note for anyone reusing it: OnPubBeingClosed runs while the app is shutting down, so keep the handler short. A...

You are mixing two different methods, and that is the whole source of the confusion. They are not meant to be used together. The "Generate a Trial Activation Key" chapter you read, where you paste a System ID, is the manual / offline key generator. You would only use that if you generated keys...

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