Protected applications are typically deployed using an installer created by a third-party tool. If you have any questions about how to implement the necessary deployment steps outlined below in your application's installer, refer to the manual for the installer software you are using, or contact the vendor responsible for it.
When using AutoCrypt SL, there are certain files which must be distributed with your application:
The FMSL.DLL file created when protecting your executable. This file will be created when protecting your application and located in the output folder specified in the Wrapper Options wizard step. Your installer should place this file in the same folder as your protected executable or DLL.
The Microsoft Visual C++ 2005 Redistributable Package. This is a small installer package provided by Microsoft that will need to be included in your installer and run during installation. The 32-bit and 64-bit installers can be found on Microsoft's website:
https://www.microsoft.com/en-us/download/details.aspx?id=26347
When protecting DLL files, AutoCrypt SL automatically creates a small stub application named <your dll filename>_helper.exe. Since most installers require elevated privileges, the easiest way to initialize the required license file permissions is to run a copy of the <your dll filename>_helper.exe application as part of your installation process. The helper.exe application is merely a stub application that does nothing, but it is wrapped with the same licensing settings as your product so that it can handle the /OPENLF call.
This section is only applicable if you have selected "One activation for all users on a machine (installer changes required)" in the License File Options wizard step.
Windows Vista and later includes a "User Access Control" (UAC) security feature which limits privileges users have, even when a user part of the Administrators group. If you have selected "One activation for all users on a machine (installer changes required)" in the License File Options wizard step for your license file locations, protected applications need to be called with the /OPENLF command line switch while running with elevated privileges to change the permissions of all License Files and Aliases to give standard users full read/write access to these files. This is typically done from within your installer since elevated/administrator privileges are usually required for installers.