Older Version 2.50 update problem

11-06-2012
It has come to my attention that there is a problem with the update process in version 2.50 and prior.  In some cases you will get an error message that states:

"Error Downloading... please try again shortly...if the problem persist please contact support"

and then the program hangs.  In other cases, the program will report that the files are up-to-date, when in fact at this time they are not.

You can manually update your program following this method:
  1. Uninstall your current version (2.10 and prior - you do not need to uninstall 2.50)  (NOTE: your user files should remain intact).
  2. Download the version 2.50, if you have not already installed it (see our DOWNLOADS page).
  3. Run the installer.
  4. Download and run this file HTTP:\\www.yasdc.com\updates\ep\update25.exe
                                    MD5 for this file is 060deb23d2390598aa8b7114ad1988ca

Because of the authentication system in v2.50 if you have not installed it before, the update25.exe will not work properly for your system.  You must install v2.50 before running the update25.exe program in order to install the proper files for the authentication system to work.

At this point your program should be up to date with all patches.  It will read v2.51 at this point if everything is successful.


A NOTE CONCERNING AVG ANTI-VIRUS and MALWAREBYTE'S INFECTION NOTICE:

On my testing system AVG Antivirus and Malwarebytes began reporting the update25.exe file as being infected with a trojan and/or appears to be malicious software.  I have run the exe through several cloud anti-virus programs without a problem.  It seems that AVG and Malwarebytes are picking up a false positive based on the compiler I use.  This has been an issue in the past with previous versions of the compiler and appears to be back in the newest version which I just updated prior to completing the v2.50 project.  If you get these errors the files "should" be safe.  I can not provide any gurantees that they are safe other than to provide the above MD5 checksum.  If your copy of the file has the same checksum it is reasonable to assume that the file is original and the report infection is a false positive.

Add a Comment