OneCommander Update Issues

[Jamil Taylor]

I noticed a new version of OneCommander, so I shutdown OneCommander, downloaded the update then installed it.  I kept running into issues with processes in use.  It was specifically OneCommander processes.  I use the dialog extensions that are resident causing locks on the previous install.  Fortunately the install shared the two Process IDs (PIDs) of the OneCommander processes allowing for taskkill:

C:\Windows\System32>taskkill /F /PID 37064
SUCCESS: The process with PID 37064 has been terminated.

C:\Windows\System32>taskkill /F /PID 31196
SUCCESS: The process with PID 31196 has been terminated.

C:\Windows\System32>

A suggestion is to automatically disable all locking processes during installation to allow users to complete the upgrade.

[OneCommander Support]

You mention "dialog extensions", do you mean OneCommanderConnector.exe didn't close + OneCommander.exe? 

Which version did you install msi, or portable? If you ran msi installer directly then it can't automatically close OC processes because installer doesn't know about those. Only when installing through OC update button (for official releases, OC can close everything properly while starting the installer)

[Jamil Taylor]

I am talking about this that is built into OneCOmmander:

I downloaded and installed this:

OneCommanderSetup3.102.0.0.msi

[Ottopops]

I'm confused by the update process as well.  What triggers users to receive an 'official release' through the update button?  I'm running 3.98.1.0 and have no update button.  Is v3.102.0.0 not an official update?

Thanks for any clarification.

[OneCommander Support]

@Jamil - If you manually downloaded installer and started it, it won't be able to close OC and Connector and Taskmaster it in advance. Official update that is started from OC does close everything before updates. 

@nschl... the 3.102.0.0 is "version ahead". The next one will be official update (after a few days of testing)