11 out of 19 rated this helpful - Rate this topic

ExitWindowsEx function

Applies to: desktop apps only

Logs off the interactive user, shuts down the system, or shuts down and restarts the system. It sends the WM_QUERYENDSESSION message to all applications to determine if they can be terminated.

Syntax

BOOL WINAPI ExitWindowsEx(
  __in  UINT uFlags,
  __in  DWORD dwReason
);

Parameters

uFlags [in]

The shutdown type. This parameter must include one of the following values.

ValueMeaning
EWX_HYBRID_SHUTDOWN
0x00400000
Beginning with Windows 8:  You can prepare the system for a faster startup by combining the EWX_HYBRID_SHUTDOWN flag with the EWX_SHUTDOWN flag.
EWX_LOGOFF
0

Shuts down all processes running in the logon session of the process that called the ExitWindowsEx function. Then it logs the user off.

This flag can be used only by processes running in an interactive user's logon session.

EWX_POWEROFF
0x00000008

Shuts down the system and turns off the power. The system must support the power-off feature.

The calling process must have the SE_SHUTDOWN_NAME privilege. For more information, see the following Remarks section.

EWX_REBOOT
0x00000002

Shuts down the system and then restarts the system.

The calling process must have the SE_SHUTDOWN_NAME privilege. For more information, see the following Remarks section.

EWX_RESTARTAPPS
0x00000040

Shuts down the system and then restarts it, as well as any applications that have been registered for restart using the RegisterApplicationRestart function. These application receive the WM_QUERYENDSESSION message with lParam set to the ENDSESSION_CLOSEAPP value. For more information, see Guidelines for Applications.

EWX_SHUTDOWN
0x00000001

Shuts down the system to a point at which it is safe to turn off the power. All file buffers have been flushed to disk, and all running processes have stopped.

The calling process must have the SE_SHUTDOWN_NAME privilege. For more information, see the following Remarks section.

Specifying this flag will not turn off the power even if the system supports the power-off feature. You must specify EWX_POWEROFF to do this.

Windows XP with SP1:  If the system supports the power-off feature, specifying this flag turns off the power.

 

This parameter can optionally include one of the following values.

ValueMeaning
EWX_FORCE
0x00000004

This flag has no effect if terminal services is enabled. Otherwise, the system does not send the WM_QUERYENDSESSION message. This can cause applications to lose data. Therefore, you should only use this flag in an emergency.

EWX_FORCEIFHUNG
0x00000010

Forces processes to terminate if they do not respond to the WM_QUERYENDSESSION or WM_ENDSESSION message within the timeout interval. For more information, see the Remarks.

 

dwReason [in]

The reason for initiating the shutdown. This parameter must be one of the system shutdown reason codes.

If this parameter is zero, the SHTDN_REASON_FLAG_PLANNED reason code will not be set and therefore the default action is an undefined shutdown that is logged as "No title for this reason could be found". By default, it is also an unplanned shutdown. Depending on how the system is configured, an unplanned shutdown triggers the creation of a file that contains the system state information, which can delay shutdown. Therefore, do not use zero for this parameter.

Windows 2000:  This parameter is ignored.

Return value

If the function succeeds, the return value is nonzero. Because the function executes asynchronously, a nonzero return value indicates that the shutdown has been initiated. It does not indicate whether the shutdown will succeed. It is possible that the system, the user, or another application will abort the shutdown.

If the function fails, the return value is zero. To get extended error information, call GetLastError.

Remarks

The ExitWindowsEx function returns as soon as it has initiated the shutdown process. The shutdown or logoff then proceeds asynchronously. The function is designed to stop all processes in the caller's logon session. Therefore, if you are not the interactive user, the function can succeed without actually shutting down the computer. If you are not the interactive user, use the InitiateSystemShutdown or InitiateSystemShutdownEx function.

A non-zero return value does not mean the logoff was or will be successful. The shutdown is an asynchronous process, and it can occur long after the API call has returned, or not at all. Even if the timeout value is zero, the shutdown can still be aborted by applications, services, or even the system. The non-zero return value indicates that the validation of the rights and parameters was successful and that the system accepted the shutdown request.

When this function is called, the caller must specify whether or not applications with unsaved changes should be forcibly closed. If the caller chooses not to force these applications to close and an application with unsaved changes is running on the console session, the shutdown will remain in progress until the user logged into the console session aborts the shutdown, saves changes, closes the application, or forces the application to close. During this period, the shutdown may not be aborted except by the console user, and another shutdown may not be initiated.

Calling this function with the value of the uFlags parameter set to EWX_FORCE avoids this situation. Remember that doing this may result in loss of data.

To set a shutdown priority for an application relative to other applications in the system, use the SetProcessShutdownParameters function.

During a shutdown or log-off operation, running applications are allowed a specific amount of time to respond to the shutdown request. If this time expires before all applications have stopped, the system displays a user interface that allows the user to forcibly shut down the system or to cancel the shutdown request. If the EWX_FORCE value is specified, the system forces running applications to stop when the time expires.

If the EWX_FORCEIFHUNG value is specified, the system forces hung applications to close and does not display the dialog box.

Console processes receive a separate notification message, CTRL_SHUTDOWN_EVENT or CTRL_LOGOFF_EVENT, as the situation warrants. A console process routes these messages to its HandlerRoutine function. ExitWindowsEx sends these notification messages asynchronously; thus, an application cannot assume that the console notification messages have been handled when a call to ExitWindowsEx returns.

To shut down or restart the system, the calling process must use the AdjustTokenPrivileges function to enable the SE_SHUTDOWN_NAME privilege. For more information, see Running with Special Privileges.

Examples

For an example, see How to Shut Down the System.

Requirements

Minimum supported client

Windows 2000 Professional

Minimum supported server

Windows 2000 Server

Header

Winuser.h (include Windows.h)

Library

User32.lib

DLL

User32.dll

See also

Logging Off
Shutting Down
System Shutdown Functions
AdjustTokenPrivileges
HandlerRoutine
SetProcessShutdownParameters

 

 

Send comments about this topic to Microsoft

Build date: 2/3/2012

Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
Does ExitWindowsEx for WP 8?
I'm trying to reboot a WP 8 device using ExitWindowsEx but getting the below error.

error LNK2019: unresolved external symbol __imp_ExitWindows
Ex referenced in function

I've added the User32.lib in my linker input but still getting the error.

Does anyone know how to resolve this or any other alternative function I can use?

Thanks.
EWX_RESTARTAPPS does not work with EWX_POWEROFF
When you want to power off the computer with EWX_POWEROFF, you need to exclude the EWX_RESTARTAPPS flag otherwise it will perform log off only.
ExitWindowsEX doesn't do forced restart on XP
I have not had the chance to test with other OS's yet, but I have some drivers that I think are preventing my XP Pro from shutting down (a common problem with XP). as a result, I have been forced to try alternative means to restart my computer.

my next try is with InitiateShutdown(), because ExitWindowsEx failed to shutdown the machine using the example code. it would shutdown to the point of saying "shutting down system..." with the blue logo screen, and hang with no disk activity. I think it actually works. more testing.

personally, I think this is a bug in XP. I really need a forced restart so I can do a chkdsk /f! and so do a lot of other people!

...
success = ExitWindowsEx(EWX_REBOOT | EWX_FORCE, 0);
...

I will be adding some REASON flags with my production code, but this is basically what it is.

EWX_SHUTDOWN does not seem to be necessary if you are doing EWX_REBOOT.

I have tried just about everything to get EWX_REBOOT|EWX_FORCE to work. GetLastError returns error code 5 and FormatMessage gives me an empty string on XP Media Center Edition. I can't get these 2 to work together. only when I have EWX_REBOOT alone will this work. InitiateShutdown() is more what I want I think, since it gives the option to force, but more testing is needed.

Logoff doesn't work inside Windows Service using WTSLogoffSession instead

[DllImport("wtsapi32.dll", SetLastError = true)]
static extern bool WTSLogoffSession(IntPtr hServer, int SessionId, bool bWait);


[DllImport("kernel32.dll")]
static extern int WTSGetActiveConsoleSessionId();


[DllImport("wtsapi32.dll", CharSet = CharSet.Auto, SetLastError = true)]
static extern IntPtr WTSOpenServer(string pServerName);





public static void Logoff()
{
int id = WTSGetActiveConsoleSessionId();
IntPtr ptr = WTSOpenServer(System.Environment.MachineName);
WTSLogoffSession(ptr, id, false);
}