During Autoupdate processing, the Autoupdater is unable to replace a Certify Client file

Problem: During Autoupdate processing, the Autoupdater is unable to replace a Certify Client file.

Symptom: A new patch is placed in the Autoupdater source location and the database has been updated to the new patch level.  When the user starts Certify, the splash screen briefly flashes the “Autodating …”  message and returns with an error message that the Client is the incorrect version (a previous version before the auto update).

Diagnosis: Autoupdate may have failed during the copying of files. If you look in the autoupdater.log file, there should be a message that says that the auto updater failed during copying a certain file (for instance, the “Worksoft.Application.dll” file).

Corrective actions: 
1.    Verify that there are no instances of the Certify Client running on the local machine.
2.    If the set up is a multiple login box (Citrix, Terminal Services, etc...), look at all processes using Task Manager. 
-    Verify that there are no other instances of Certify running for another user
-    Shutdown all instances of Certify running on the multiple login box, before restarting the Certify Client.
3.    Restart the Certify Client again. Autoupdater should be successful this time.