I have encountered numerous cases where a plug-in update fails because the exe is not accessible with a recommendation to disable the plug-in and try again. Since I routinely disable plug-ins before updating them, that is not a helpful suggestion.
Bob Maslin has been recommending that his plug-ins be disabled, then HS restarted before attempting an update.
One thing I've noticed is that in many cases disabling the plug-in leaves its exe running in Task Manager. Today I tried killing the exe of the troublesome plug-in. After that the update proceeded without issue and re-enabling the plug-in was uneventful.
Can anyone explain what should happen when a plug-in is disabled? Is the exe supposed to be terminated when the plug-in is disabled? Is there a downside to killing the process with Task Manager if disabling the plug-in doesn't do it?
Bob Maslin has been recommending that his plug-ins be disabled, then HS restarted before attempting an update.
One thing I've noticed is that in many cases disabling the plug-in leaves its exe running in Task Manager. Today I tried killing the exe of the troublesome plug-in. After that the update proceeded without issue and re-enabling the plug-in was uneventful.
Can anyone explain what should happen when a plug-in is disabled? Is the exe supposed to be terminated when the plug-in is disabled? Is there a downside to killing the process with Task Manager if disabling the plug-in doesn't do it?
Comment