After a new version comes out, when I copy the entire clamwin folder (in standalone mode) to another computer, I first of all delete the old version in that computer.

However, the aforementioned file can't be deleted even if I clear ClamWin's registry settings. It demands a total restart!

Obviously there's a way to do it because the official installer does manage to remove this file somehow (and then replaces it with the new version). So what does it do that I don't?

Thanks!

This happens because expshell.dll (explorer context menu handler) is loaded by Windows Explorer. ClamWin setup cannot replace a locked file without a reboot.

If you do not see a request to reboot at the end of an upgrade then this file did not change and the setup did not need to overwrite it. Do a binary file compare on 2 dlls and you should see that they are identical.

So what you're saying is that the only reason the computer that ran the official installer didn't need a reboot too is because the installer was smart enough to know not to delete this file because it had no newer version? And if there was a newer version, the installer would have asked me to reboot?

I have yet to reboot that one computer so I can tell you its file is identical to the one in the computers that were booted.

yes

I wish there was a way to unload it then...

Kill explorer.exe process in the process explorer