Installation: Couldn't overwrite ContextMenu64.exe

[Megalith]

I just updated my copy of XYplorer and ran into some error about the installation not being able to overwrite ContextMenu64.exe. Just curious if anyone else ran into something like that. I had XYplorer closed when I began the installation, so I'm not sure what happened. However, the upgrade to 16.90.200 seems to have completed without issue (although the progress bar in the installation never completed all the way); the program opens without any errors.

[bdeshi]

ContextMenu64.exe keeps running in the background. It usually closes with XYplorer.exe, but perhaps this time the installer didn't wait long enough for the menu exe to close.

[RalphM]

Not exactly the same problem but along the same line, every now and then one of XY's beta builds (installer version) doesn't kill the XY.exe process on exit, so the installer complains that XY.exe can't be overwritten. Yes, I tried several times in those (still rather rare) instances to give it more time, but after a few minutes I gave up and killed the process manually, after which the "Try again" button worked.

[admin]

Weird. Did not happen to me for years.

[RalphM]

Want to know next time it happens?

[admin]

If you also see any steps to reproduce it, yes.

[JLoftus]

This happens to me about half the time, using the simpleupdater script. The easy fix is kill contextmenu64.exe using task manager, then click "try again". One hiccup for this, is if you run Windows as a standard user (as you should), you have to run taskmgr.exe elevated to kill the process. A minor inconvenience for the increased security that running as a non-admin provides.

[admin]

I cannot make this happen here. (Keep ContextMenu64.exe in memory after closing XYplorer.exe)

[RalphM]

Not exactly the same problem but along the same line, every now and then one of XY's beta builds (installer version) doesn't kill the XY.exe process on exit, so the installer complains that XY.exe can't be overwritten. Yes, I tried several times in those (still rather rare) instances to give it more time, but after a few minutes I gave up and killed the process manually, after which the "Try again" button worked.

Just happened again with the installer upgrade from .0207 to .0208 so I started process explorer to see that XYplorer.exe was still listed with a subbranch of PDFXchange (I had dbl clicked on a pdf in the last session and I still had that pdf open) so I aborted the install, restarted XY, quit out of PDFXchange and started the installer again via context menu in XY, X closed XY but the XY process stayed in process explorer but this time without a subbranch. So I had to kill XY manually in process explorer, after which the installation could be finished.

It seems that .0207 (and some other builds before) somehow didn't get killed on X close.

[admin]

Tried various combinations with PDF-Xchange but could not create any problem. Process got finished 100% of the times.

[LittleBiG]

It has just happened to me too. I had to kill the process manually.

[RalphM]

I only described the PDFXchange bit because I thought first I had found the reason and a way to reproduce it but then was disappointed when the process still didn't get killed even without PDFXchange open.
Whenever it happens it seems to be persistent to that build of XY only.