Managing Windows systems remotely is a crucial skill for IT professionals who are responsible for maintaining network infrastructure across distributed environments. The ability to restart computers without having physical access saves valuable time and resources, especially when handling critical updates, troubleshooting system issues, or performing routine maintenance tasks.
Remote restart capabilities are of utmost importance when managing large deployments where physical access is impractical or impossible; whether you are addressing a performance issue on a server located miles away, applying critical security patches across an enterprise network, or helping a remote employee recover from a system freeze, knowing how to efficiently restart Windows systems is an inevitable part of effective system administration.
This guide will provide you with detailed step-by-step instructions for implementing remote restart procedures using Windows’ built-in tools, including PowerShell commands for individual and batch computer restarts, the Action1 Platform for browser-based remote management, and Command Line utilities with the necessary firewall and service configurations. Furthermore, we will explore how to properly prepare systems for remote operations by enabling required services, configuring firewall settings, and identifying target computers by name.
By mastering these remote restart techniques, you’ll enhance your ability to maintain system availability, respond quickly to issues, and streamline administrative workflows across your organization’s Windows-based environment.
How to Restart a Remote Computer Using PowerShell?
Windows PowerShell is a powerful command-line interface for remote management that automates tasks and simplifies managing multiple systems efficiently. For remote computer management, PowerShell allows executing restart commands across multiple machines simultaneously, scheduling reboots with user notifications, and forcing restarts when necessary.
These capabilities make it a handy tool when dealing with deploying updates, troubleshooting issues, and maintaining system performance across distributed Windows environments without requiring physical access to each endpoint.
-
To restart a remote computer, follow these steps:
Step 1. Open PowerShell with administrator privileges—right-click on the PowerShell icon and select Run as administrator.
Step 2. Execute the restart command:
Restart-Computer -ComputerName REMOTE-PC-NAME -Force
The -Force option will force the remote system to restart even if a user is logged on. Keep in mind that you must replace “REMOTE-PC-NAME” with the actual hostname or IP address of the target computer you want to restart.
Step 3. If you need to use different credentials for the remote connection:
Restart-Computer -ComputerName “RemotePC” -Credential “DomainUser”
PowerShell will prompt you for the password. This method is useful when your current account lacks sufficient privileges on the target system.
How to Restart Multiple Computers via PowerShell?
Restarting multiple remote computers simultaneously can be executed with the following command; just list all the computers you want to restart.
Restart-Computer -ComputerName “PC1”, “PC2”, “PC3” -Force
Alternatively, you can create a text file with all the computers you want to restart and add them to the PowerShell command below:
Restart-Computer (Get-Content c:\work\computers.txt) -Force
This command reads computer names from the text file (one computer name per line) and passes them to the Restart-Computer cmdlet. It’s better suited for restarting a larger number of computers, where maintaining the list in a file is more convenient.
How to Restart Remote Computers Using Action1?
The easiest way to restart your endpoints remotely that does not require firewall configurations is using the Action1 platform directly via your web browser. The solution is useful for a variety of workflows, including installing updates or rolling out new group policies. When it comes to restarting remote machines, you have the option of forcing a reboot immediately or specifying a schedule that will work both for you as an administrator and for the end-user.
Step 1. Create an account:
Firstly, you would need to create an account at Action1 to get started right away. The registration does not require credit card information.
Step 2. Connect endpoints:
Secondly, add endpoints into your network to be able to manage them remotely. To do this, you need to install agents on the endpoints you wish to manage via Action1. The app allows you to add up to 200 endpoints into your network free of any charges and commitments.
Step 3. Restart remote endpoints:
-
Navigate to the Managed Endpoints page.
-
Locate the endpoint(s) you want to restart and select Reboot.
Note: Alternatively, click the locations in the Actions column and select Reboot. Or click New Action on top of the page and select Reboot from the drop-down list.
Complete the Wizard:
Step 4. On the Reboot step, choose if you want to warn users that a reboot is coming. The notice will appear on their screens before the endpoints restart. You can choose to show a default text or enter any other text. Then, specify the message timeout. Make sure you provide enough time to allow users to save their work and prepare for restart.
Step 5. On the Select Endpoints step, check the endpoints you plan to reboot. You can include more endpoints by clicking Add Endpoints. Action 1 enables you to add endpoints individually, or you can specify criteria such as Windows Server 2019 or Windows Desktop OS.
Step 6. On the Schedule step, review your action and pick the right time to execute it. For example, you can force reboot immediately or schedule obligatory restarts once a week to deliver updates. Once ready, click Finish.
Step 7. After clicking Finish, you’ll find yourself on the Actions/History page. Here, you’ll see the execution details. If you opted not to execute your action yet, you’ll find it waiting for you on the Actions/Scheduled page.
What Are the Prerequisites for Restarting a Remote Computer When Using the Command Line?
A remote computer cannot be restarted using the command line if it is not configured properly to receive remote commands or if it is not connected to the same network. Before executing remote restart commands, ensure these critical requirements are properly configured:
-
Administrative Access: Domain or local administrator credentials on target systems.
-
Service Configuration: Remote Registry service enabled and set to automatic startup.
-
Network Connectivity: Functioning TCP/IP connectivity between systems on the same network.
-
Firewall Configuration: Windows Management Instrumentation (WMI) permitted through Windows Firewall.
-
System Identification: Target computer name or IP address properly documented.
-
Command-Line Tools: Access to Command Prompt with appropriate execution permissions.
So before we start using the command prompt, let’s first check if your system is properly configured to avoid any errors during the process of restarting a remote computer(s).
How to Enable Remote Reboot?
To configure the computer you wish to reboot (hereinafter referred to as the remote computer), follow these steps:
Step 1. In the search bar of the Start menu, type ‘services‘ to find the Services utility. If you don’t see the Services icon, type ‘services.msc‘ into the search bar, and the Services menu will appear.
Step 2. In the R section of the Services menu, scroll down and right-click on Remote Registry. Then select the Properties icon.
Step 3. Open the start-up drop-down menu located in the middle of the window.
Step 4. Select Automatic from the drop-down menu.
Step 5. Click OK.
How to Allow Remote Reboot in Firewall?
Step 1. Open the Start menu on a remote computer (not the computer from which the reboot command will be sent). In the search bar of the Start menu, type ‘Firewall‘ to find the Windows Firewall program and click the appeared icon.
Step 2. Click “Allow an app or feature through Windows Firewall.” You’ll find it in the upper left corner of the window.
Step 3. In the upper right corner above the list of programs, click “Change Settings.” A list of programs will be displayed.
Scroll down to the bottom of the program list and tick the box on the left of Windows Management Instrumentation (WMI).
Step 4. On the right-hand side of Windows Management Instrumentation (WMI), you’ll see the option to tick either “Private” or “Public.” If your computers are connected to a public network, check the box in the Public column and click OK at the bottom of the window.
Now the firewall will not block remote access to the computer.
How to Find the Computer Name?
Step 1. On a remote computer (not on the computer from which the reboot command will be sent), open Windows Explorer and click “This PC.”
Step 2. Click the “Computer” tab in the upper left of the window. The toolbar will open.
Step 3. Click “Properties.” (This is a red checkmark icon on a white background, located on the left side of the toolbar.) The computer settings will open.
Step 4. In the middle of the page, you’ll find the name of the computer in the “computer name” line. Write down the name of the computer exactly as it appears here.
How to Restart a Remote Computer Using the Command Line?
Sit at another computer. It must be connected to the same network as the remote computer. Log in as an administrator.
Open the Windows Command Prompt from the Start menu.
Input the following shutdown command: ‘shutdown /i’ in the Command Prompt and then press ↵ “Enter.” A window will open with the option to restart the remote computer.
On the right side of the window, click “Add.” A new window will open.
Enter the name of the remote computer in the corresponding text box. If you have not yet found the name of the remote computer, do it now (see the previous section above). Click “OK.”
In the Select the desired action for computers section, open the drop-down menu and make sure the Restart (not remote shutdown) option is selected. If necessary, check the box beside “Warn users of the action,” too, and input the time during which the warning will be displayed on the screen. Then click “OK.”
How to Restart a Computer Remotely Using Windows Remote Desktop?
Windows Remote Desktop Connection provides administrators with a direct interface for managing local and remote computers effortlessly.
-
To restart a remote computer via Remote Desktop, follow these steps:
Step 1. Establish Secure Connection
-
Press “Windows key + R” to open the Run dialog.
-
Type “mstsc.exe” and press “Enter” to launch Remote Desktop Connection.
-
Click “Show Options” to expand the connection dialog.
-
Select the Advanced tab.
-
Click “Settings” under the “Security” section.
-
Set the encryption level to “High” from the dropdown menu.
-
Return to the main dialog and enter the remote system’s hostname or IP address in the Computer field.
-
Configure appropriate display settings (recommended: full screen for administrative tasks).
-
Click Connect to initiate the connection.
Step 2: Authenticate and Secure Session
-
When prompted, enter administrative credentials with system restart privileges.
-
Verify the security certificate when presented.
-
Click “View certificate” to examine details.
-
Ensure the certificate matches the expected domain/issuer.
-
-
Check the “Remember my credentials” box only if operating in a secure environment.
-
For enhanced security, enable Network Level Authentication:
-
In RDP settings, select Connect only to computers that use Network Level Authentication.
-
Click OK to apply this security setting.
-
Step 3: Execute Restart Operations
-
After a successful connection to the remote desktop, click the “Start” button.
-
Select “Power” from the menu options.
-
Click “Restart” from the power submenu.
-
Alternatively, for a command-line restart:
-
Press Windows key + R on the remote system.
-
Type shutdown /r and press Enter. (This command will restart the computer, not execute a remote computer shutdown.). The /r parameter specifically initiates restart functionality.
-
Keep in mind that your Remote Desktop session will terminate immediately as the restart initiates.
Troubleshooting Remote Restart Operations
When trying to restart remote computer(s) across your organization’s distributed environment, you can frequently encounter specific operational challenges that may become a reason for failed remote machine restarts. For that reason, we have selected the most common problems you may face during the process and their resolutions.
Authentication and Credential Management Issues
Remote restart operations frequently fail due to credential problems or expired login tokens. These issues always show up as “Access Denied” error messages while trying to run restart commands, especially in networks with multiple domains or several levels of administrator permissions.
Resolution:
-
Check your current user permissions with the command “whoami /all” to make sure you have the right admin access.
-
When entering credentials, use the complete format (domain\username) to avoid authentication errors.
-
For persistent login problems, consider setting up dedicated service accounts with proper access rights.
Network Path and Firewall Configuration Obstacles
Connection problems are the most common reason remote restarts fail, especially in networks with separate segments or multiple security layers.
Resolutions:
-
Check Basic Network Connectivity:
-
Run this PowerShell command to make sure you can reach the remote computer:
Test-NetConnection -ComputerName REMOTE-PC-NAME -Port 135
-
Look for “TcpTestSucceeded: True” in the results; that would indicate your connection is working.
-
Verify firewall settings:
-
Check if Windows Management Instrumentation (WMI) traffic is allowed through the firewall:
Get-NetFirewallRule | Where {$_.DisplayName -like “*WMI*”}
-
Make sure these rules show “Enabled: True” in the output.
-
Keep in mind that for computers behind routers, you may need to set up port forwarding for ports 135 and 445.
Service Dependencies and Configuration Misalignment
To successfully execute remote restart commands, you need several background services to work properly. If they aren’t running or are misconfigured, your restart commands will fail.
Resolution:
Verify all necessary services are running by typing this PowerShell command:
-
Get-Service WinRM, RemoteRegistry, RpcSs | Select Name, Status, StartType
-
Make sure all these services show “Running” under Status and “Automatic.”
-
For persistent service problems, run this command to repair the WMI system.
winmgmt /resetrepository
Command Syntax Problems
Using incorrect command formats or parameters is another common cause of restart failures, especially when using PowerShell commands.
Resolution:
-
Add the -Verbose parameter to see detailed information about what’s happening.
Example: Restart-Computer -ComputerName REMOTE-PC-NAME -Force -Verbose
-
Always use full computer names (like server1.company.local) instead of short names when possible.
Testing Your Remote Restart Setup
Every time before restarting remote computers, follow these steps that will guarantee the successful completion of the process:
-
Test basic connectivity with a simple command like “ping REMOTE-PC-NAME” first.
-
Try your restart commands on test computers before using them on important systems.
-
Keep notes of commands that work successfully for future reference.
Manage your PCs remotely with Action1
Action1 is an autonomous endpoint management platform that is cloud-native, infinitely scalable, highly secure, and configurable in 5 minutes—it just works and is always free for the first 200 endpoints, with no functional limits. By pioneering autonomous OS and third-party patching – AEM’s foundational use case – through peer-to-peer patch distribution and real-time vulnerability assessment without needing a VPN, it eliminates costly, time-consuming routine labor, preempts ransomware and security risks, and protects the digital employee experience. Trusted by thousands of enterprises managing millions of endpoints globally, Action1 is certified for SOC 2 and ISO 27001.
The company is founder-led by industry veterans Alex Vovk and Mike Walters, American entrepreneurs who founded Netwrix, which has grown into a multi-billion-dollar industry-leading cybersecurity company.
