Running the current v3.00 release, noticed that on Windows 2008 R2, logged in as administrator, I found that the update executable is not being replaced by the new .ts3 file that has downloaded from the server. I did run one of the updaters (same script) from a compile that was done with an earlier version of True Update and it worked as expected on the same server. Cannot not honestly tell you which version but it was complied about 18 months ago.
Now if I run the updater on a stand alone computer everything works as expected. Bit Defender tries to get in the way but with it turned off you see the script working exactly as is has for the past 5 years.
So I am wondering if there was something that changed in True Update that might possibly be causing the issue. I event went so far as setting the Share to Everyone with Full control and no change.
So you are aware, the update script does work and the software does update properly. In the end it just leaves the .ts3 file and the update executable at an old date.
Any suggestions?
Jack
Now if I run the updater on a stand alone computer everything works as expected. Bit Defender tries to get in the way but with it turned off you see the script working exactly as is has for the past 5 years.
So I am wondering if there was something that changed in True Update that might possibly be causing the issue. I event went so far as setting the Share to Everyone with Full control and no change.
So you are aware, the update script does work and the software does update properly. In the end it just leaves the .ts3 file and the update executable at an old date.
Any suggestions?
Jack
Comment