Search results

Make also sure that you have the latest Microsoft Visual C++ Redistributable version. https://aka.ms/vs/17/release/vc_redist.x86.exe

Which version of CEF have you selected in your project? And make sure to run the Web Update utility to replace old remaining versions that were not deleted by the installer.

Could you please check the Windows Event Viewer in case of a crash? If you have a DUMP file as well, that would be even better. Thank you.

Before the final release, here is a pre-release of ExeOutput for PHP 2025 with WebView2 support, for those who are interested. Before releasing the final installer, we still need to fix a few minor bugs and finalize our documentation. However, due to demand, we are publishing this version as...

Regarding the issue you described, we have not received any additional reports of similar behavior since your last message, and our internal tests with XLS Padlock under the latest Windows updates have not reproduced the problem. We regularly monitor Windows updates, and no recent changes have...

We don't provide support for old versions though. You could create a stand-alone console app with ExeOutput that executes your artisan queue:work command. Then, with HEScript within your main app, you execute the console app in the background. Thus, it does not freeze your main app UI. To...

As XLS Padlock does not manage deployment environments or automatic switching of validation URLs, the responsibility for distinguishing between staging and production environments typically falls under your own deployment setup. Some hosting providers offer staging tools that allow you to...

To prevent this, you can use the two VBA protection features of XLS Padlock: Lock VBA project and Prevent access to the VBE. Or even better, use our integrated VBA compiler to secure portions of your VBA code.

Thanks Susan. Note that there is still a lot of work. We want to polish the release before it goes live.

Yes, we still want to keep Windows 7 CEF files in that release. But it may be the last one to handle Windows 7, we'll see. Especially with additional 64-bit support, it becomes time-consuming to keep compatibility with CEF, WebView2 32-bit and 64-bit down to Windows 7.

Each product should have its own INF file. Have you checked that the URL is correct?

The solution is to create a stand-alone artisan.exe for your project, as explained in our tutorial here: https://www.exeoutput.com/blog/new-tutorial-convert-laravel-web-apps-to-windows-desktop-apps It's near the end: 10. Manage Artisan Commands.

If you use the WooCommerce Integration Kit for online activation, verify that you have not enabled the trial nag screen into the workbooks.json file. That would explain why you are getting the initial trial message.

Get ready for our incoming upgrade! We are thrilled to announce that ExeOutput for PHP 2025 is in the final stages of development and is expected to be released by the end of this month. This is one of our biggest updates yet, packed with features you've been asking for and significant...

I see now, this error message is not due to XLS Padlock itself, but rather the activation options you configured for your project. You certainly made a key for testing with that option enabled: That's the option which shows the nag screen on the screenshot you sent. To remove this, try this...

Please start the XLS Padlock Manager (shortcut on your desktop) and choose Activate. Then follow instructions.

It's in "inc\app\controllers\MainController.php" Even if you don't know PHP, with an AI, you should be able to make modifications you want.

We'll try to reproduce the issue, thanks for the report!

Any screenshot for the problem please?

Deactivation API works in the last 2025.1 release, with the bundle format too. IF not, please report it again.