If a task has been running longer than expected, it could be that it is waiting on user input. The application or patch that is associated with the task will run with the same account that the task is run as. If that account does not have an interactive logon session, then the application or patch will not have an interactive logon session. If the application or patch is waiting for user input and the account is non-interactive, then the task will appear to still be running. Some applications and patches can detect whether or not the logon session is interactive and will exit with an error if it detects that the session type is incorrect.