Panda

ah yes thanks for the hint! From last upgrade process i had a dynamic group with task to reboot the client! I'm going to try it again without the autoassigned reboot task ^.^ oopsie EDIT: I tried it again to upgrade to the newest version and everything went as expected.

I did it with 3 clients from 7.3.2032 to 7.3.2036 and all 3 did an unexpected reboot though the option for reboot were unchecked.

I just tested the new version and updated my version through eset task. Selected no reboot but eset reboots my client anyway... that is not acceptable for our enterprise - user should be given the option to reboot their client when they want to (or at least forced reboot in the middle of the night).