Launcher PRO 3.4.0 Build 191 is now available.
3.4.0 Build 191
- Added: Support for 3.33.4 64bit Only
- Updated: CAFD Mapping compatibility level: 18-04 i-Step
- Removed: Required root certificate
- Minor bug fixes
NOTE: Authenticode RSA certificate is no longer required, but installing RSA Certificate with "EB06BA22 6FB31CD3 787A2ABB 84E71D61 F1CEA5B9" thumbprint to the Trusted Root Certification Authorities store on current user is still recommended. This certificate can only be used for Authenticode purposes and cannot be used to create intermediate or subordinate, or end entities certificates.
To Install Certificate:
via Command prompt: LauncherPro3.exe installcert
via Windows: Right-click LauncherPro3.exe > Properties > Digital Signatures > Details > View Certificate > Install Certificate and install it under Trusted Root Certification Authorities store
To Delete Certificate:
via Command prompt: LauncherPro3.exe removecert
or use mmc.exe and Certificate Snap-in. See https://tokenmaster.blogspot.com/2019/05/code-signing-certificate.html
*Requires Google Authenticator mobile app. Download from Apple App Store or Google Play Store
Note: Please see https://www.fxxtokenmaster.com and blog before upgrading to 3.1+. Launcher PRO now uses Time-based One-time Password for authentication.
Google Authenticator is required when using dynamic activation and when updating the Launcher.
NOTE: For WIndows 7 users, if you're having problems with validation/activation, Windows is probably not using TLS 1.2 to communicate to my site. Check the following registry key, as shown in the image:
First thing to do is ensure all updates are installed. If you don't see TLS 1.2 key, create it, then create the Client key under it. The two DWORD values must exist and should contain data as shown in the image. Restart WIndows and try again