Hopefully when the IT will put the program in the Win Task Schedule, I can find more on how to do updates.

>Several ways to skin this cat: have another task running that looks from the directory where YOU are barred from into a directory where you can put things to look for new versions
>Or similar, inside the task have a constant "stub loader", which loads the "newest" real task dynamically from secure directoy, but peeks into the directory where you have write access to check for new versions.
>Of course such half assed security opens a slight vulnerability into the system, as anybody knowing the directoy you have access to, the inner workings of your service loader and your login creds can place a malicious service - one way around that is not installing yourself but mailing updates to DBA who is responsible...
>
>>>What I did for updates was to invoke the taskmanager aka bouncer and simply kill the task, then replace the exe with a new version and then restart it from the task scheduler.
>>>Another, easier way, was to have the version number in the filename, and just place the new exe in the same folder, then edit the task in the scheduler to run the new exe instead. That way the old exe would continue until it would regularly exit, and the next run would use the new exe. The trouble with this approach is that I need to know the password of the account under which it runs, which I didn't, for several clients.
>>
>>Most likely I won't know the password either. And I can easily choose the time for the update when the program will not be running, since it will only run one time per week for about 2-3 minutes. What I read in your message is that Windows does not actually move the application file (EXE) to another folder. Therefore, once this project goes into effect, I will simply replace the EXE one time and see what happens.
>>Thank you.