Search results

Yes, this strange path is due to the virtualization used by XLS Padlock. The workbook is always at a random virtual location. That's why we use: Public Function PathToCompiledFile(Filename As String) Dim XLSPadlock As Object On Error GoTo Err Set XLSPadlock =...

Thank you for the additional report. According to the debug log on ProtectEbook.net, we haven't received any notifications from your FastSpring account, which suggests there may be an issue on FastSpring's end. I recommend reaching out to FastSpring’s support team. They previously identified our...

We are working on the issue. Are you using the console compiler or the GUI to build your project with the directive?

Yes, we are aware of this issue appeared in the last CEF version. We'are studying for a way to disable this automated "restore" behavior from Chromium. Thanks for the reports!

The idea is to add the second workbook as a companion file or to use our VBA helper to tell Excel where the second workbook lies (for instance in the same folder as the EXE, using our VBA helper PathToFile...

📢 XLS Padlock 2025.0 is here! Discover the next major evolution at www.xlspadlock.com We’re excited to announce the release of XLS Padlock 2025.0, a major update that brings significant new features and improvements to help you protect and distribute your Excel workbooks even more efficiently...

In the video you sent to us, it looks like the agreement opens fine and then nothing. Could you try to upgrade to XLS Padlock 2025.0?

Yes, both Paquet Builder and XLS Padlock (2025 versions) now offer cloud code signing, thanks to the new SignTool integration. Choose SignTool Commands as the Code Signing Method: Then enter the necessary parameters for signtool, generally sent to you by your Code Signing provider. For...

Well, in the incoming XLS Padlock 2025, the old version is correctly closed, the custom message shows up and the new version is shown. Even if the “Only allow one instance of the protected workbook” option is on. So hopefully it will also work in your case. XLS Padlock 2025 is rather a big...

Strange, because it works for us once the port 9000 was added to the "Discover Network Targets" Chrome dialog box.

Unfortunately, CEF in ExeOutput has a very limited extension support, but with the recent CEF releases, we'll check whether this has been improved. Note that we are focused on WebView2 now, and probably we'll depreciate CEF as WebView2 offers the opportunity to get smaller EXE files.

RTF is being deprecated. PB converts old RTF files in GUI when loading all projects or importing manually RTF files, but not in the automated/directive area. Can you try to switch to a markdown or HTML format file?

There is another switch to try: --disable-session-restore If it still does not work, we'll have to debug this ourselves.

Thanks for the follow-up and this discovery! Maybe you can try to add this command line switch: --disable-restore-session-state

Really strange issue. Because once again, admin rights are not necessary to access files.

Does it occur with your other projects? Are the project files still accessible?

This is a known issue in CEF, but the developer said he won't fix it: https://github.com/chromiumembedded/cef/issues/3740 Instead, there are new instructions for remote debugging. You should use chrome://inspect/ for connecting to remote debugging in Edge or Chrome, click Configure and enter...

Strange that administrator is required. It may be a file access problem because this dialog box is displayed when ExeOutput scans for files in your project. If the dialog is stuck (even if multithreading is used), then this means something blocked access to the scanned files. Any antivirus or...