Server Core has no Start menu, so there is no Restart button to click. So how do you do it from just a command? This guide shows the one-line reboot, explains each switch, and covers the PowerShell equivalent, delayed and remote restarts, and how to confirm the server actually came back.
Prerequisites
- A Windows Server Core install (2008 R2, 2012/2012 R2 and every later release, including 2016, 2019, 2022 and 2025). The same commands work on full Desktop Experience installs and on Windows client.
- An account in the local Administrators group. Shutdown and restart need elevation.
- A quick check that nobody is in the middle of something: a reboot drops every RDP session, open file share and running job on the box.
1. Open a command prompt or PowerShell window
On Server Core you land in a command prompt (2012 R2 and earlier) or a PowerShell window (newer builds) after you sign in. Either one works. If you closed it, press Ctrl+Alt+Del, choose Task Manager, then File > Run new task and type cmd or powershell.

2. Reboot now with shutdown /r /t 0
Use the following command:
shutdown /r /t 0
Basically shutdown /r is for reboot, the /t is for time, and 0 is zero seconds, meaning now. That’s it: Windows closes your session and restarts straight away.
What the common switches do
/r: full shutdown and restart./s: shut down and power off instead of restarting./t xxx: wait xxx seconds first. Any value above 0 also implies/f./f: force running applications to close without warning users./c "text": a comment shown to logged-on users and written to the event log./d p:4:1: a planned reason code (here: application maintenance), so the restart is documented in the System log./a: abort a pending shutdown while the timer is still running./m \\computer: act on a remote computer instead of the local one.
3. Schedule a restart with a warning
For a production box, give users a minute and leave a note in the log:
shutdown /r /t 60 /c "Restarting for patching" /d p:2:17
Changed your mind? Cancel it before the timer runs out:
shutdown /a
4. The PowerShell way: Restart-Computer
In a PowerShell window, Restart-Computer does the same job:
Restart-Computer
Restart-Computer -Force
-Force restarts even if users are logged on or applications have unsaved work. To restart another server from your workstation and wait until PowerShell remoting answers again:
Restart-Computer -ComputerName SRV-CORE01 -Force -Wait -For PowerShell -Timeout 600
The remote form needs admin rights on the target and remote management allowed through its firewall. See Enable Remote PowerShell Access for the WinRM side.
5. Using sconfig instead
If you prefer menus, type sconfig at the prompt. The Server Configuration tool has Restart Server and Shut Down Server entries near the bottom of its menu. It is handy right after you install Windows Updates on Server Core, which usually needs a restart.
Verify the server came back
Once you are signed in again, check the last boot time:
systeminfo | find "System Boot Time"
or in PowerShell:
(Get-CimInstance Win32_OperatingSystem).LastBootUpTime
The time should match your restart. Planned restarts done with shutdown are logged in the System event log as event ID 1074, together with the user and the reason code.
Common errors
- Access is denied.(5): the window is not elevated, or your account isn’t a local administrator. Open an elevated prompt and try again.
- A system shutdown has already been scheduled.(1190): a restart is already pending (Windows Update often schedules one). Run
shutdown /a, then issue your own command. - The server takes a long time to come back: updates are being installed during shutdown or startup. Give it time and watch the console in your hypervisor or iLO/iDRAC before forcing a power cycle.
Related guides: Install Server 2012 Core | Install Windows Updates on Server Core
