-remote-exit--exit-debugging-client-.md

title	description	keywords	ms.date	topic_type	ms.topic	api_name	api_type
.remote_exit (Exit Debugging Client)	The .remote_exit command exits the debugging client but does not end the debugging session.	Exit Debugging Client (.remote_exit) command remote debugging through the debugger, Exit Debugging Client (.remote_exit) command .remote_exit (Exit Debugging Client) Windows Debugging	05/23/2017	apiref	reference	.remote_exit (Exit Debugging Client)	NA

.remote_exit (Exit Debugging Client)

The .remote_exit command exits the debugging client but does not end the debugging session.

.remote_exit [FinalCommands]

Parameters

FinalCommands
Specifies a command string to pass to the debugging server. You should separate multiple commands by using semicolons. These commands are passed to the debugging server and the connection is then broken.

Environment

You can use the .remote_exit command only in a script file. You can use it in KD and CDB, but you cannot use it in WinDbg.

Item	Description
Modes	User mode, kernel mode
Targets	Live, crash dump
Platforms	All

Additional Information

For more information about script files, see Using Script Files. For more information about debugging clients and debugging servers, see Remote Debugging Through the Debugger.

Remarks

If you are using KD or CDB directly, instead of using a script, you can exit from the debugging client by using the CTRL+B key.

You cannot exit from a debugging client through a script that is executed in WinDbg.