Recent content by gdgsupport

Update (October 2026): how XLS Padlock protects your workbook today The answer above dates from 2020. Here is the current picture, as of XLS Padlock 2026.3. Blowfish is no longer used. Encryption is now based on AES: save files are encrypted with AES 256, with HKDF-SHA256 key derivation and...

This question never got a direct answer from us, so here it is, with the facts as of XLS Padlock 2026.3. XLS Padlock does not obfuscate your VBA code: it compiles it. When you build the application, the VBA Compiler turns the pasted macros into bytecode and removes their original source. There...

Thanks for the extra detail. The antivirus and virtual machine questions were a guess, and they do not hold: this particular failure does not come from a security product. The message Hash must be initialized is raised by the third party compression component that the current release uses for...

Unfortunately, it's a bug inside WebView2. Could you run the upload again under WebView2 with this in the receiving script: var_dump($_FILES['file']); var_dump($_SERVER['CONTENT_LENGTH'] ?? null, strlen(file_get_contents('php://input'))); What matters is: whether tmp_name is an empty string...

This is fixed, and the fix is out today in XLS Padlock 2026.2. https://www.xlspadlock.com/download @StevegHI, your two Event Viewer entries are what pointed at this! Thank you again! What to do now: Install XLS Padlock 2026.2. Re-pack your workbook with it. The second step is not optional...

It's also fixed in version 2026.2 released today. Thanks!

XLS Padlock 2026.2 is now available We have released XLS Padlock 2026.2, the second maintenance update of the 2026 line after 2026.1 in July. The headline item is a correctness fix: in applications built with 2026.0 or 2026.1, protected formulas that reference other cells could return a wrong...

Sure, please check your direct messages on the forum (mailing icon at the top). Thank you!

Thank you for the issue report! This will be fixed in the incoming XLS Padlock 2026.2 to be released in the incoming days. If you are OK, we can send you a preview build.

Thank you for the reports! Though they are different applications. We'll investigate.

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