See All FAQs and Terms (Quick Links) for links to all FAQs including purchase terms, free software agreements, and software licensing terms.
A note about Anti-Virus detections
Sometimes our software can be falsely flagged as a ‘threat’ by some Anti-Virus, Anti-Malware, etc. security software vendors.
Email (Troubleshooting Issues)
For CryptoPrevent, please see the CryptoPrevent Email FAQ here.
For d7x, please see the Email Configuration section of the d7x manual here.
All other applications, if you are having issues with GMail try the steps below:
GMail’s SMTP server is “smtp.gmail.com” and it can be accessed on port 465/SSL or port 587/TLS or StartTLS; select “Auto” for authentication if available.
Be certain to include the domain name (e.g. @gmail.com or @yourcustomdomain.com) in the SMTP username field.
For accounts without two factor authentication, enabling the “less secure application” feature may help: https://www.google.com/settings/security/lesssecureapps
Two factor authentication can complicate things as well, and when using this you will need an “application specific password” in order to connect properly to the server through this app. Learn more and obtain application specific passwords here: https://support.google.com/accounts/answer/185833?hl=en and you can manage them at this link: https://security.google.com/settings/security/apppasswords
Finally, we have also had reports that Gmail will sometimes block what it considers a ‘suspicious login‘ and that it should alert you of this the next time you login to the webmail interface. You should be notified that you can ‘unlock‘ your account by going to this link: https://accounts.google.com/DisplayUnlockCaptcha after which the account should be unlocked and email sending will no longer be blocked.
Digital Signatures and User Account Control
Most if not all of our applications are digitally signed! A digital signature is what is displayed in User Account Control pop-ups requesting admin rights prior to running the apps. There are two issues that one may discover that is caused by this setup.
1. On some systems the signature was not correctly recognized as a trusted publisher, invoking the yellow warning “User Account Control” box and displaying “unknown” as the publisher. This should no longer be an issue; several years ago we moved to Digicert from StartSSL for our code signing certificates, which should be supported on all modern platforms “out of the box” and without update.
To resolve the issue, be sure and install the Trusted Root Certificates update from Microsoft/Windows Update. If this does not appear in the updates list, you may manually download and install the package directly from Microsoft HERE for Windows XP. Alternately, visit which will prompt you to download the appropriate cert, open the file and select Install.
- As a PC Repair business customer, one might expect the ability to fully brand a “White-Label” application with your business logo and details. Unfortunately this is only partially true, without a lot of effort on your part. The issue does not affect only our software, as the trusted publisher information appearing on the UAC prompt of ANY application cannot be altered, except by “signing” the executable with a new digital signature. Otherwise UAC would be a pretty pointless feature, as all manner of malware could disguise itself as legitimate applications!
So how do you re-sign the executable with your own digital signature, specifying your own company name? Well the process is fairly complicated, and involves obtaining an identity verification from a trusted certificate authority, such as Comodo, Verisign, or
StartSSL (which I personally used the latter as it was far less expensive.) Digicert, which we currently use. The process of obtaining identity verification, a digital code signing certificate, and applying that to the executable is outlined in my blog post Digital Code Signing – What a Chore!