How to Reboot a Remote Desktop Session or Remote PC

AvatarByEric Dawson Computers & Software

To reboot a remote desktop session, press Windows key plus D to bring the desktop into focus inside the RDP window, then press Alt+F4 and choose Restart, or open Command Prompt and run shutdown /r /t 0 for an immediate restart. Both methods work from inside an active Remote Desktop Protocol session on Windows 10, Windows 11, and Windows Server. Administrators managing a frozen session that will not respond to normal input can instead force it closed with the reset session command. Every one of these methods reboots the entire PC, not just the remote desktop application, so save open work first because unsaved changes are lost.

How Do You Reboot a Remote Desktop Session with Keyboard Shortcuts

Press Windows key plus D, then Alt+F4, to open the Shut Down Windows dialog from inside the RDP window, and pick Restart from the drop-down list. TinkerTry describes this combination as a neat and clean solution because it needs no mouse and no trip through the Start menu. Ctrl+Alt+End opens the Windows security screen inside the same session, but it does not always show Shut Down and Restart options on Windows 10 over RDP, so Ctrl+Alt+Del may be the option that works in some configurations instead. Either shortcut gets you to the same restart control the Start menu offers, just faster.

A mouse-only path works too, and it mirrors what you would do on a local PC:

  1. Step 1: Select the Start button in the bottom left corner of the remote desktop.
  2. Step 2: Select the Power icon in the Start menu.
  3. Step 3: Select Restart from the options that appear.

How Do You Reboot Remote Desktop Using the Shutdown Command

Open Command Prompt inside the remote session, type shutdown /r /t 0, and press Enter to restart the PC immediately with zero seconds of delay. Command Prompt reaches the same restart function as the GUI, and it keeps working even when the Start menu freezes or a shell extension misbehaves. Zero delay means the restart begins the instant you press Enter, so close and save any open files before you run it. TinkerTry warns that because of the zero second delay, you want to be very sure you intend to restart immediately before you press that Enter key.

Command line access matters most when the graphical interface stops responding entirely, since a frozen Start menu often still lets a Command Prompt window accept input. Administrators scripting mass restarts across many machines also rely on this syntax, since it drops directly into batch files, scheduled tasks, and remote management tools without any manual clicking. Typing the same three words every time beats hunting through menus on a machine you rarely touch.

How Do You Restart the Local Session Immediately

Typing shutdown /r /t 0 restarts the machine you are logged into right now, with the /r flag telling Windows to restart rather than shut down and /t 0 setting the countdown to zero seconds. Scripts and remote management tools often call this same command, so learning the syntax once covers both manual and automated restarts. Nothing prompts you to save work first, which is why many administrators prefer a short delay instead.

How Do You Delay the Restart to Save Your Work

Running shutdown /r /t 60 restarts the PC 60 seconds after you press Enter, giving you and anyone else on the session time to close programs and save files. A visible countdown or notification typically appears during that window, depending on the Windows version. Thirty, 60, or even 120 seconds are all reasonable choices for a routine restart where nobody needs to react instantly.

How Do You Cancel a Pending Restart

Typing shutdown /a in a new Command Prompt window, before the countdown reaches zero, cancels a pending restart or shutdown. You have to run this as a separate command while the timer is still counting down, since the original window is usually busy waiting. Once the timer hits zero, the restart proceeds and there is nothing left to cancel.

My default would be to use a 60 second restart delay rather than `shutdown /r /t 0` when other people might still be working on the remote PC. The extra minute is a small cost compared with losing an open document or interrupting a task that was still running. I would reserve the zero delay command for a machine that is clearly stuck or for maintenance where the timing has already been communicated. If the Start menu still works, I would also favor the normal Restart option because it makes the choice easier to see before committing.

How Do You Restart a Remote PC from Another Computer

Run shutdown /r /m \\SERVER01 /t 30 /c “Scheduled maintenance restart” from an elevated Command Prompt on your own machine to restart a remote PC named SERVER01 in 30 seconds, with the /m flag pointing at the target computer and /c attaching a reason visible to anyone still logged in. Network administrators use this pattern constantly for patch nights, since it avoids walking to every desk or opening a separate RDP session for each machine. Replace SERVER01 with the actual computer name or IP address on your network, and replace the quoted text with whatever explanation you want logged.

What Do the Shutdown Command Parameters Mean

Eight parameters cover almost every situation the shutdown command handles, from a simple local restart to a scheduled remote shutdown with a logged reason. The table below lists each one with its effect.

Parameter What It Does
/r Restarts the computer after shutdown
/s Shuts down the computer instead of restarting
/t xxx Sets the delay before shutdown, from 0 to 315,360,000 seconds; default is 30
/m \\computername Targets a specific remote computer
/f Forces open applications to close without warning, which can lose unsaved data
/c “comment” Attaches a custom reason, up to 512 characters
/d [p|u:]xx:yy Records a reason code for the Shutdown Event Tracker (p = planned, u = user-defined)
/e Documents the reason for an unexpected shutdown

What Is the Difference Between Reset, Disconnect, and Logoff

Reset forcibly ends a session and clears its memory, disconnect leaves the session running so you can reconnect later, and logoff closes everything and returns the license to the server. Choosing the wrong one either wastes server resources or throws away work you meant to keep. The table below lines up all three next to a full restart, since restarting is really a fourth option people confuse with the first three.

Action Effect on Session Effect on Applications Effect on Resources Best Use Case
Disconnect Session preserved in memory, can reconnect later Applications remain running Resources still allocated to the session Stepping away temporarily, long tasks, unstable connections
Logoff Session ends completely Applications close, unsaved data lost Memory and license returned Not returning to the session, freeing server resources
Reset Session forcibly terminated Applications close without warning, unsaved data lost Memory cleared Frozen or unresponsive session
Restart (shutdown /r) PC reboots, new session created on reconnect All applications close during reboot System fully restarts, all resources reset Maintenance, updates, or troubleshooting requiring a full reboot

Command line users can trigger any of the three with tsdiscon for disconnect, logoff for logoff, and reset session for reset, each followed by the session ID and the /server switch when working across a Remote Desktop Session Host farm. Query session or quser lists every session ID on a server before you act on one. PowerShell offers rwinsta as a direct equivalent to reset session.

How Do You Reset a Frozen or Unresponsive Remote Desktop Session

Run reset session followed by the session name or ID, such as reset session 3, to forcibly terminate a session that stopped responding to keyboard shortcuts or the shutdown command. This deletes the session from the Remote Desktop Session Host server and clears its memory, which is more drastic than a disconnect or a normal restart. Add /server:servername when you are resetting a session on a different machine than the one you are working from.

Finding the right session first matters, since resetting the wrong one disrupts someone else’s work. Query session or quser, run from an elevated Command Prompt, lists every active session name and ID on the target server so you can confirm which one is actually stuck before you reset it.

What Permissions Do You Need to Reboot a Remote Desktop

You need the Shut Down the System user right to restart or shut down a local or remotely administered computer with the shutdown command. Resetting your own session never requires special permission, but resetting someone else’s session does require Full Control access on that session. Microsoft’s own documentation warns that resetting a user’s session without warning them first can result in the loss of data at the session, so a quick message before you act is worth sending.

Annotating an unexpected shutdown with a reason code additionally requires membership in the Administrators group on the target machine, or in the Domain Admins group when the computer is joined to a domain. Standard user accounts can restart their own session in most default configurations, but they usually cannot reset or restart someone else’s.

What Happens After You Reboot a Remote Desktop Session

Reconnecting after a restart typically takes only a few minutes, the actual time the machine needs to boot, provided the Remote Desktop service is configured to start automatically on every boot. A full shutdown behaves differently: once the machine powers all the way off, you cannot reconnect through Remote Desktop at all unless something else brings it back online, such as Magic Packet, a network technology that wakes a sleeping or powered-down PC. That distinction is why most people choose restart over shutdown when they plan to reconnect later.

Unsaved data in any application still open on the remote desktop disappears the moment the restart or reset happens, and forcing applications closed with the /f flag makes this more likely, not less. Saving work and closing programs before you trigger any of these commands avoids the problem entirely rather than hoping the countdown gives you enough warning.

Checking whether the reboot actually completed is worth doing on any machine you cannot see with your own eyes, and pinging the computer name from another machine on the same network is the simplest test once a few minutes have passed. A successful ping means the operating system finished booting and the network stack came back online, even if the Remote Desktop service itself needs another moment to start accepting connections. Waiting an extra minute after a successful ping before you try to reconnect avoids repeated failed connection attempts.

Frequently Asked Questions

Can You Reboot a Remote Desktop Session Without Losing Your Work?

Saving every open file before you restart is the only reliable way to avoid losing work, since none of the standard reboot methods prompt you automatically. A short delay, such as shutdown /r /t 60, gives you a minute to close programs first. Forcing the restart with /f or resetting a session skips that warning entirely.

Why Does Remote Desktop Not Reconnect After a Reboot?

Reconnection fails right after a reboot when the machine has not finished booting yet, so waiting a few minutes solves most cases. It can also fail when the Remote Desktop service is not set to start automatically, which requires fixing the service configuration on that machine rather than waiting longer. Network changes during the reboot, such as a new IP address, occasionally cause the same symptom.

Can You Wake a Remote PC After a Full Shutdown?

Waking a fully shut down PC over the network generally requires Magic Packet support, a Wake-on-LAN technology that must be enabled in the computer’s firmware and network adapter settings ahead of time. Without that configuration in place before the shutdown, a fully powered-down machine stays off until someone restarts it physically. This is one reason restart is usually the safer choice over shutdown for a machine you need to reach remotely.

Do Third-Party RDP Clients Restart Sessions the Same Way?

Third-party clients such as those used in place of the built-in Remote Desktop Connection app still connect to the same underlying Windows session, so the shutdown command and the reset session command work identically once you are connected. The client software mainly changes how you establish the connection, not what happens once you are inside the remote Windows desktop. Menu layouts for restart options can differ between clients, so check the specific app if the keyboard shortcuts described here do not appear.

Does This Work on Windows 11 and Windows Server?

Yes, the keyboard shortcuts and shutdown command described here work the same way across Windows 10, Windows 11, and the Windows Server versions that support Remote Desktop, since they rely on functionality built into Windows itself rather than a specific edition. The reset session and query session commands are specific to Remote Desktop Session Host environments, most often found on Windows Server. Exact menu wording can shift slightly between versions, but the underlying commands stay the same.

Match the method to the situation: keyboard shortcuts for a session you are actively using, the shutdown command when you need speed or scripting, and reset session when nothing else responds. Whichever one you choose, save your work first, since every reboot path here closes running applications along the way.

What This Page Does Not Publish

  • I cover native Windows Remote Desktop here, not reboot steps for TeamViewer, AnyDesk, or other remote-control apps.
  • I do not walk through server configuration for reconnecting automatically after a reboot.
  • I do not cover Wake-on-LAN or Magic Packet methods for starting an offline PC.

References

Author Profile

Eric Dawson
Eric Dawson
I'm Eric Dawson, the writer behind The Money Watch. I live in the Columbus, Ohio area and I write about the ordinary questions that turn out to be complicated: computers, shopping, food, travel, parking, small businesses, fees, rules and products. Every article starts with the official page, the maker or the agency, then the sources that check it, and I say plainly where they disagree and what I would do. More about how I work is on the About page.