1. Home
  2. PowerArchiver 2021
  3. Tech Support
  4. Compress from shell got killed by update after closing another GUI instance


Compress from shell got killed by update after closing another GUI instance

  • C

    :mad:

    I just had a 80% complete job that had been running for >24 hours killed by the stupid patchbeam updater, after closing another instance of the PowerArchiver GUI.

    Needless to say, I am 100% seeing red!

    The updater should NOT kill ANY running jobs!!

    0
  • M
    conexware

    Hello,

    Sorry you had an unwanted experience.
    There are a few prompts asking you to use patchbeam before upgrade starts.
    Can you provide some more detail as to what exactly happened? Patchbeam closed PowerArchiver while it was working?

    Thanks!

    0 C 1 Reply
  • C

    Sorry, I see now in my hasted anger I forgot to post the details.

    In explorer, I selected a folder and from the shell menu chose “Compress to folder.7z”. This then opened a window with the compression progress.
    Completely unrelated to that, about a day later, I opened a PA GUI window, NO archives, I just wanted to check some settings (specifically, if there are any ‘multi-thread’ options). After I closed this GUI, my other dialog stated ‘cancelling’, closed after a while and then PatchBeam opened and updated my PA.

    0
  • spwolf
    conexware

    In the case of PA 2015, full Patchbeam has not yet activated. So it just downloads the installer right now. Installer when it starts actually doing the update, will want to replace powerarc.exe, in order to update it.

    Are you sure that you did not have to manually advanced through installer though? I think first step should be manual.

    0 C 1 Reply
  • C

    Maybe I am so used to PatchBeam doing the updates that I mistyped what happened. I remember that the installer was run, yes, but AFTER my ‘shell compress job’ got killed. That is the important bit.

    So, the steps as I recall:

    • shell compress was running
    • GUI opened and closed
    • shell compress got nuked
    • update was downloaded/installed
    0 spwolf 1 Reply
  • spwolf
    conexware

    @crohan:

    Maybe I am so used to PatchBeam doing the updates that I mistyped what happened. I remember that the installer was run, yes, but AFTER my ‘shell compress job’ got killed. That is the important bit.

    So, the steps as I recall:

    • shell compress was running
    • GUI opened and closed
    • shell compress got nuked
    • update was downloaded/installed

    It is installer that kills instance of anything that it has to replace, so it has to be done during install process - Patchbeam or PA do not have ability to do this.

    Now, we run installer in reduced mode when you are updating from Patchbeam. So I will check if we show enough dialogues during update. If I remember correctly, we do, but I will check to make sure. Most people usually just click through it super fast though.

    But in general, for the future, it would be safe to assume that update will close all instances of anything that it is updating. This is always pa.exe at least. There is no really a way around it except for not updating when PA is running of course.

    thanks!

    0 S 1 Reply
  • S

    I’m assuming POWERARC.EXE will only ever be loaded/running if either the GUI is open or it’s actively doing an archive operation. Are there any other cases where the EXE would be loaded?

    In the first case, probably not many people would care if the EXE got killed to update the app…

    In the second case (the OP’s case) could you not have some sort of callback to some module in the PA stack that the installer could use to see if there are active operations running - and if so, abort the update?

    0
Log in to reply