Search results

The Digital Signatures tab in your screenshot indicates that there is no signature on the file at all. The signing step did not produce anything, which is why there is no timestamp to see. That is good news in a way, because it means you are looking for one failure rather than two. Your...

STOCKHISTORY is a Microsoft "connected experience": the function does not compute anything locally, it fetches the price history from Microsoft's online service. That is the key to what you are seeing, and it explains why the workbook behaves differently once compiled while the .xlsm works...

Yes, your machine is perfectly suitable. An i7-13650HX with 32 GB of RAM on 64-bit Windows with an x64 processor is well above what XLS Padlock needs, and the "System type" line settles the important question: this is not the ARM limitation. So we can set that aside entirely and look at the...

@fsarre: you're right, but as of today there is no setting, on the Norton side or on ours, that removes this while keeping the browse dialog. Every configuration that does not crash is one where the dialog is never shown. Offering you a fourth workaround after you have soundly rejected three...

Thank you for coming back with real test results rather than impressions! Your two tests together are conclusive. You uninstalled Norton, rebooted, and the crash disappeared on both. That is the test that actually proves something, and it means Norton is the trigger. Your instinct was right...

Glad that was it, and well found! :) One thing to check before your beta, because it is the same trap one level down. That library reference resolves on your machines because they have XLS Padlock installed. Your beta users will not have it. So if your project still carries a design-time...

On reuse: on the same computer, no. The trial's expiry date is stored on the machine when the key is first entered, and XLS Padlock also detects the clock being turned back, so a user cannot get a fresh 14 days by simply re-downloading and re-entering the same key on the same PC. It stays...

The pattern in your own results points straight at the cause: it runs on your Office 2021 laptop and fails on every Office 2013 machine, in both bitnesses. That rules out 32 versus 64-bit, and it rules out the individual machine. The common factor is Excel 2013, and the "Compile error in hidden...

fsarre, the Event Viewer entry you posted is the decisive piece, thank you for it. It changes where this needs to be looked at. The faulting module is AppVIsvSubsystems64.dll, with exception code 0xc0000005, an access violation. That DLL is not part of XLS Padlock, and it is not a Norton...

Good, a signed EXE ready for the shop is the milestone. The trial is a separate mechanism from the kit, and that is the part worth getting straight, because it decides where the 14 days actually go. Two different keys live in two different places: The trial (before anyone buys) does not come...

Thanks, that is useful, because it clears the whole environment side. First, the detail you noticed about the two black windows, because it tells us something concrete. XLS Padlock signs by calling SignTool with the Azure dlib. When SignTool comes back with a failure code, XLS Padlock waits two...

Thank you for spelling out the workflow, because it changes the answer, and it also shows that two of our earlier statements sent you in the wrong direction. Your design is built on them, so let us correct both first. First, in a previous reply we wrote that an open trial with no order at all...

fsarre, your report is different from the one this thread started with, and the difference matters, so it is worth separating the two. The original issue here was a crash on any Windows file dialog, Save As and Insert Image alike, and it was traced to Norton's behavioural protection. Yours is...

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