UPDATE: Launcher PRO V2.6.2

TokenMaster's Launcher 2.6.2 PRO is now Out.

Launcher PRO 2.6.2 Build 135

- Added ability to load Developer-signed CAFD files. Signature must be properly calculated for this to work. Tampered files are still blocked.

Launcher was designed with security in mind, not an after-thought. That being the case, we do have some brilliant minds out there, and allowing a modified, properly vetted, CAFD file can be beneficial. Starting with version 2.6.2, CAFD files properly signed with developer certificate and correct digital hash will be allowed, but ONLY IF the user chooses to do so. So, how does this work? Let's start with the following image:

Default is Not Allowed. This setting is not saved, so every time the Launcher starts, this is the default. You get the PSdZ error above, whenever a modified, or in this case -developer-signed, CAFD is requested.

Now, when you click on it, you'll get the following message:

You need to acknowledge the message, and understand that from that point forward, everything you do can have a catastrophic result. The button will turn Red while this setting is active. You can turn this on or off at will, and you will get the same message every time it is turned on.

Be careful when loading developer-signed CAFD and do not share it if you encounter one. And I hope nobody abuses this feature. 

NOTE: Please do not request via the comment section. I do not monitor the comments actively nor will answer any requests from this blog. Email me at fxxtokenmaster_at_gmail for any question.