Updating BC and shell extension

[Guest]

Usually when I install an update I don't check the "Include in Explorer context menu" option because it is already installed so. This way I avoid to restart the system.
This time with the 2.4 I get the message that the system must be restarted. I think that this should not happen.

Bye

[Zoë]

Re: Updating BC and shell extension

Thanks for the bug report. If the installer has a new version of the shell extension dll, which this version does, it will try to replace it even if you don't have that checked, and if you already have the shell extension loaded it has to replace it during the reboot. It's only supposed to prompt to restart if you have that checked, but it looks like that's not working properly. We'll take a look and see what's going wrong.

[mlotauro]

Re: Updating BC and shell extension

Is it really necessary to restart the system?

And about the options checked during the installation, should they reflects the actual situation? Acutally if I don't want anymore for example the shell extension I cannot remove it until I finished the installation.


Bye, Maurizio.

[Zoë]

Re: Updating BC and shell extension

If we're updating the shell extension and it's already been loaded by Explorer then yes, the system has to reboot for it to update that file. As long as Explorer is running it will keep the file locked, so we have to tell Windows to do the copy the next time it's booting.

Changing the behavior is certainly something we can consider, but I'm not really sure that the install program is the best place to disable the shell extension if you already have it enabled.