@stuurjans: Image may be NSFW.
Clik here to view.
@pjmur: beats me - as you can see it works for the OP now, and works for me.
If you're still having issues, try embedding the command
SHUTDOWN.EXE /h
in the Programs-After setting of the profile (or if in a Group, the last profile, making sure they run sequentially!). This is not ideal, as it would also happen if you ran such a profile manually, and it actually hibernates the PC with SBFree and the Task still running (the PC will - if it works - be hibernated before SBFree has a chance to close, so neither does the Task that called it), but it should figure itself out once it wakes (though there might be a short 'Huh?! What just happened?' period), and it may be your only option.
Of course if SHUTDOWN.EXE (part of Windows) doesn't work either, you may need to take that up with Mr Windows (though they'll probably say your power config is awry, motherboard/BIOS does not support or is wrongly configured, yada yada...)
Clik here to view.
@pjmur: beats me - as you can see it works for the OP now, and works for me.
If you're still having issues, try embedding the command
SHUTDOWN.EXE /h
in the Programs-After setting of the profile (or if in a Group, the last profile, making sure they run sequentially!). This is not ideal, as it would also happen if you ran such a profile manually, and it actually hibernates the PC with SBFree and the Task still running (the PC will - if it works - be hibernated before SBFree has a chance to close, so neither does the Task that called it), but it should figure itself out once it wakes (though there might be a short 'Huh?! What just happened?' period), and it may be your only option.
Of course if SHUTDOWN.EXE (part of Windows) doesn't work either, you may need to take that up with Mr Windows (though they'll probably say your power config is awry, motherboard/BIOS does not support or is wrongly configured, yada yada...)
