TMS Web Update downloading the CAB file again and again

VCL TMS VCL UI Pack
1

Hello folks,

I have been using TMS WebUpdate for many years without a problem. The recent version I released is downloading the new CAB file but the process that shall kill the original executable and replace it with the new content of the CAB file is not working any more.

I am suspicious that a recent Windows 11 update detects the small executable integrated into the EXE as malicious and does not allow the original executable to be removed from memory and replaced.

Anyone else who has similar problems?

Salut, Mathias

2

Just some additional information:

  • the CAB file is downloaded
  • the Upd.exe is extracted from the executable in the CAB file after I say yes to "Shutdown application to update executable files ?"
  • the Upd.exe is called with the process number of the original executable in memory together with the CAB file name and the EXE file name to be replaced

According to the WUPDATE.LOG file there was no error:
WUPDATE.LOG (3.6 KB)

Salut, Mathias

3

Is nothing preventing the app from being closed? Something that holds the app's EXE in memory?

4

Hello Bruno,

thanks for your reply.

I have now tried it once more in my Hyper-V development machine debugging TWebUpdate.DoRestart. I debugged the code until I hit the ShellExecute call on line 5206 and then executed the rest without the debugger. It worked! :slightly_smiling_face:

I then disabled the Developer mode and made sure that the Windows virus thread detection was on, compiled the executable again with the older version number and executed it outside of the Delphi debugger. It worked! :slightly_smiling_face:

I then used the recompiled "older" executable on the host machine, where it had failed yesterday, and it worked!

So at this stage I think it must be related to my hosting environment. I have SuperCacher on a SiteGround website active, which may have caused the CAB file to not being available immediately. But the INF file was! :thinking:

Let's mark this issue as resolved and I will take it up with the support team at SiteGround.

Salut,
Mathias

1 Like