Issue: "Defer until machine is locked" makes the package install start after the timeout has been reached

Version 4

    Issue

     

    In Distribution and Patch settings > General settings > Notification it's possible to customize the behavior of the distribution process when a user interaction is required but there a no response timeout occurs.
    In the section No response timeout options, it's possible to set up the distribution to automatically defer install until machine locked.

     

    Defer_until_machine_locked_core.png

     

    However, this option is actually delaying the package installation for the time set in the timeout setting below, rather than deferring it until the machine is locked.

    Using that option, when the timeout is reached, the package installation will start, even though the machine is not locked.

     

    Defer_until_machine_locked_client.png