Thank you for your post.
I doubt whether running the process as a scheduled task will be successful, since the process runs all the time, presumably checking for updates as and when it thinks fit, and although I could start the process as a scheduled task the process would then just sit there until I next closed the computer. Since I have known the process replicate itself while the computer was running as well as on start-up, running the process as a scheduled task would neither protect me from multiple instances nor provide any assurance that an update check had actually taken place. For the time being, running the updates check is apparently futile, given that the program is to be discontinued.
I have tried deselecting automatic updates in the user interface, but having done so still get multiple instances upon occasion on start-up.
When I renamed the process, I was still able apparently to run the manual update function in the user interface.
Renaming the file seems to have no adverse effect upon the functioning of the programme.
Even if I terminate the process when it is running it automatically recommences shortly afterwards, and so I take it that it is automatically restarted by the DLL.
I enclose a couple of screen prints of auto run, but I can see no reference to this process, which further supports your suggestion that the process is started by a DLL. I do note however that OEPL.DLL is referred to as a plug-in for Outlook express. I thought the only plug-in was for Outlook. I also note that apart from the plug-in the only start-up is a DLL, and so I presume that that is what handles the encryption and decryption.