Share via


Force close apps upon Logout / Restart / Shutdown *after* specified delay.

Question

Wednesday, February 20, 2019 7:57 PM

We've observed with Windows 10 the default behavior upon logout is that if an application (ie: unsaved word document) is holding up the process that after 60 seconds the logout attempt is aborted and it returns to desktop.

What we'd like is to be able to specify a time (15-30 seconds or so) for the user to acknowledge their are applications holding it up giving them the ability to press cancel, and if they don't then the logout / shutdown process will resume and the applications will be force shut down. 

We've experimented with all combinations of WaitToKillAppTimeout, HungAppTimeOut, and AutoEndTasks but none of these seem to achieve these results. 

WaitToKillAppTimeout I'm not sure is still supported in Windows 10. HungAppTimeOut appears to just change how long the delay is before Windows let's you know an application is holding up shutdown and enabling AutoEndTasks simply forces the logout process with no ability for the user to review the applications that are holding up the logoff. 

Am I missing something or is what we're trying to accomplish not possible? We are running Windows 10 1803 (17134.590).

Jason

All replies (3)

Thursday, February 21, 2019 9:39 AM âś…Answered

Hello JCPWX,

Thank you for posting in this forum.

I did experiments on Windows 7, Windows 8, and Windows 10. When you have a program that needs to perform a "save" operation (such as Notepad and Word document), the system will pop up a screen with two options (Shut down anyway and Cancel). If you do nothing, the computer does not force the program to close and continue to shut down unless you click "Shut down anyway".

If applications, for example, the web browser, is not closed, the system will shut down directly without popping up that screen.

The system is designed to prevent you from losing important data.

Maybe you can do this with a script. I hope these sites can help you: Script Gallery and Forum for Script requests.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Monday, February 25, 2019 11:00 PM

Thanks Leon,

I understand the design is to protect losing data, what we were looking for was a balance between that and a user unsuccessfully logging off and leaving a workstation logged in.

After you stated Windows 7 was the same I was confused as this is definitely an issue that only started to be reported on our new Windows 10 users. I went back and tested Windows 7 and see what the difference is. The difference is in Windows 7 it will sit at the 'Waiting for programs to close' indefinitely until a user chooses the force log off, or to abort the log out. 

In Windows 10 after 60 seconds has passed it decides on behalf of the user and aborts the logoff process, returning to the desktop. This is what has led to some of our users being confused when they came back to their desks why it hadn't logged off, whereas in Windows 7 it was quite apparent as they would return to a desk with the logoff process clearly being held up. 

What I wish was available with Windows 10 is a setting / registry key that allows you to choose the behavior that occurs after 60 seconds. Default to what it does today (abort log off), Windows 7 behavior (log off screen remains until selection made), or force logoff.

It isn't what I was hoping for but the issue is understood better now, thanks for the reply.


Tuesday, February 26, 2019 9:59 AM

You are welcome, JCPWX.

Good to hear that the information is useful. And sorry for not providing a really effective solution.

Maybe a script or a third-party program can fulfill this requirement.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].