You can reset a Windows PC remotely, but only if the machine is powered on, reachable on the network, and was already set up for remote management. Every remote reset route — Remote Assistance, PowerShell remoting over WinRM, or a recovery restart — depends on software inside Windows that is still online. If the computer is off or disconnected, nothing you send will do anything.
This guide walks through how to reset a Windows PC remotely for Windows 10 and Windows 11, from Home through Enterprise. Most method sections take five minutes of checking before you touch anything destructive. The whole job takes longer than people expect, mostly because of the credential and recovery-key checks, not the reset itself.
Table of Contents
- What You Need
- Step-by-Step
- How to Check Remote Access Before Resetting
- How to Use Windows Remote Assistance
- How to Reset Windows Remotely with PowerShell
- How to Restore a Reachable PC with Windows Recovery
- How to Handle an Offline or Unreachable PC
- Common Mistakes
- Frequently Asked Questions
- Can I reset a Windows PC when it is turned off?
- Which Windows versions support remote reset features?
- Does Windows Reset this PC delete all my files?
- How do I reset a remote Windows PC without knowing the administrator password?
- Why can my PowerShell reset command fail even though the computer is online?
- Can I remotely reset a PC that is not on my local network?
- Conclusion
What You Need
What you need depends entirely on which route you take, and the route depends on how the PC is set up. Work through this list before you send a single command.
Administrative access. Every method below needs local administrator rights or an equivalent domain or Entra ID administrator account. A standard user account cannot trigger Reset this PC or change WinRM configuration, no matter how many commands you queue up.
Network reachability. The target must answer on the network. Across subnets or firewalls you will need routing, firewall rules, or WinRM over HTTPS. On the same LAN, an IP address or hostname is usually enough.
Remote management enabled in advance. PowerShell remoting needs WinRM running, Remote Assistance needs to be available on both machines, and the machine needs to have been reachable when you configured it. There is no remote switch that turns all of this on from outside.
Credentials. Keep both the local administrator password and the domain or Microsoft account credentials handy. A reset that loses remote access before setup finishes leaves you relying on the built-in administrator account, which on some builds is disabled for remote login.
BitLocker recovery key. If the drive is encrypted and the reset fails partway, Windows will ask for the 48-digit recovery key. Find it before you start, on the Microsoft account page or your organization’s key vault.
Two more items matter more than most people expect. First, decide whether the PC is on Windows Home, Pro, or Enterprise, because the edition changes what you can script. Second, have a fallback for physical access: a USB with Windows recovery media, or the ability to send someone to the machine. Both turn a failed remote attempt into a ten-minute fix instead of a dead end.
A quick note on the Windows edition. Home has no native remote management story worth relying on: no WinRM over HTTPS by default, no built-in MDM, and no Intune enrollment of the kind admins use. If you need unattended remote reset on Home machines, third-party RMM or anti-theft agents are the realistic path. Pro and Enterprise give you everything described here.
The quickest way to sort out which situation you are in:
| Method | Needs | Works while nobody is logged in | Data erased | Difficulty |
|---|---|---|---|---|
| PowerShell remoting | WinRM enabled, admin rights | Yes | Depends on the option you pass | Medium |
| Remote Assistance | A cooperating user at the PC | No | Yes, when you run Reset this PC | Easy |
| Recovery restart (WinRE) | Admin rights, physical fallback | Yes, on some builds | Depends on the option you pick | Medium |
| Out-of-band (Intel AMT, vPro) | Hardware with AMT provisioned | Yes, even while powered off | You drive the whole install | Hard |
| Someone on site | A person and the recovery key | Not applicable | Depends on the option you pick | Easy |
Step-by-Step
How to reset a Windows PC remotely safely comes down to four decisions, in order: confirm you have the access, confirm the machine answers, pick the least destructive option, and keep a way back in. Work through the sections in order and you will not need to improvise later.
How to Check Remote Access Before Resetting
Run these checks on the machine you will be working from. Most “the reset did nothing” problems turn out to be a failed check here.
Confirm the machine answers and you know its name:
ping PCNAME
Test-Connection -ComputerName PCNAME -Count 2
Resolve-DnsName PCNAME
Then confirm PowerShell remoting is listening. On the target, run this in an elevated PowerShell window:
Get-Service WinRM
winrm enumerate winrm/config/listener
A listener line with an address of 0.0.0.0 or your machine’s LAN IP means WinRM is listening. No output, or an access denied error, means it is not configured yet.
From your admin machine, test the session and confirm who Windows thinks you are on the far end:
Test-WSMan -ComputerName PCNAME
Enter-PSSession -ComputerName PCNAME
whoami /groups
If Enter-PSSession fails with a trusted-hosts error, the target is in a different workgroup or domain and Kerberos will not resolve it. That is expected, and the fix is covered in the PowerShell section below. If it fails with a network error, check the firewall before anything else: WinRM’s HTTP listener uses TCP 5985, and HTTPS uses 5986.
Finally, read the reset options you are about to use, so there are no surprises at the confirmation screen:
Get-ComputerInfo -ComputerName PCNAME | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber
Windows 11 shows up as Windows 11 Pro or similar in WindowsProductName; Windows 10 shows the same way. Knowing the exact build matters because recovery options and reset behavior shift between major releases.
How to Use Windows Remote Assistance
Remote Assistance is the right choice when a person is sitting at the PC and can click. It is guided support, not unattended automation, and knowing that up front saves disappointment.
On the machine that needs help, search for Remote Assistance in the Start menu and choose Invite someone to help you. Pick Use the default Easy Connect or save an invitation file, which produces a short code. Send that code to the helper.
On the helper machine, start Remote Assistance and enter the code. Once connected, you share the screen and can run commands on the target in an elevated PowerShell window, or open Settings > System > Recovery and start Reset this PC.
Watch for the difference between the two reset choices before confirming. Keep my files removes installed applications and settings but keeps personal files. Remove everything deletes personal files too, and on some builds also attempts to remove the previous owner’s account and sign the device out of Microsoft servers.
Remote Assistance expires after a set period and the connection must be accepted by the person at the PC. If nobody is there to click accept, this method is a dead end.
How to Reset Windows Remotely with PowerShell
This is the method most administrators reach for, because it works while nobody is logged in and it scripts cleanly. Test it on a noncritical machine first — every configuration mistake is easier to debug there.
On the target, in an elevated PowerShell window:
Enable-PSRemoting -Force
Confirm-Configuration -Confirm:$false
That starts WinRM, creates the HTTP listener, and opens the firewall rules. On a domain network, Kerberos handles authentication and you are done. On a workgroup or a cross-domain hop, add the target to TrustedHosts on the admin machine:
Set-Item WSMan:localhostClientTrustedHosts -Value "PCNAME" -Concatenate
Test the connection with Test-WSMan PCNAME. If that returns a listener and version, you have a working remote channel.
Then choose the reset. To launch the built-in reset experience on the target:
Invoke-Command -ComputerName PCNAME -ScriptBlock { Start-Process systemreset.exe }
That opens the same Reset this PC screen you would get from Settings, with the Keep my files and Remove everything choices, and the session drops once the machine restarts into it.
For a plain restart when you only need Windows to come back up clean:
Restart-Computer -ComputerName PCNAME -Force
Two warnings. Never enable anonymous access or add AllowUnencrypted to the listener on a network you do not control — that lets anyone on the segment run code as administrator. And a remote PowerShell session dies the moment the target restarts, so queue the reset as the last thing you send, not the first.
How to Restore a Reachable PC with Windows Recovery
When the PC answers administrative commands but cannot complete a normal reset, boot into the Windows Recovery Environment instead. On Windows 10 and 11 you can do that remotely:
shutdown /r /o /t 0
The /o flag means boot into the recovery options. The machine will drop the session and come back up at the recovery menu, where you choose Continue, then Use a device.
Once in the menu, the three options are different things and mixing them up is the usual reason a repair “didn’t fix it”:
- Reset this PC reinstalls Windows. Choose Keep my files to retain documents and downloads, or Remove everything to erase them.
- Repair your PC tries to keep the existing installation and fix what’s broken. It uses the local reinstall source or a cloud download, and can take a long time on a slow link.
- Advanced startup gives you Startup Settings, Safe Mode, System Restore, and command prompt options. This is where you go if the drive is encrypted and you need the recovery key entry screen.
Expect to prove you are an administrator: a local administrator account password, or a domain or Microsoft account that is an administrator on the device. If the only admin account used a Microsoft account, the password is the full email and password, not the four-digit PIN. If nobody can authenticate, you will need the recovery key and a USB with installation media.
Put that USB in place before you need it. A formatted drive, a copy of Windows, and the BitLocker recovery key stored on a separate drive remove almost every failure mode in this section.
How to Handle an Offline or Unreachable PC
Be blunt about this: software running inside Windows cannot execute anything when Windows is not running. There is no remote command, registry value, or scheduled task that reaches a powered-off machine. Every “remote wipe” feature people describe really means “wipe the next time this device checks in,” and devices that never check in are never wiped.
What you can still do:
- Wake it first. Wake-on-LAN sends a magic packet to the network interface and works with the PC off, as long as the motherboard, NIC, and BIOS support it and the packet stays inside the broadcast domain. Router-based wake or a smart plug on the PSU is the next step up.
- Use out-of-band management. Intel AMT or vPro, IPMI on a server, iLO or iDRAC, or an equivalent BMC console runs firmware independent of Windows. You can power on, power cycle, enter BIOS, and mount a virtual media image to install Windows yourself. This is the only true remote reset of a powered-off machine, and it has to be provisioned in firmware first.
- Check the remote management console. If the machine is enrolled in an RMM or MDM service, the console shows its last check-in time and any queued commands. That tells you whether it is asleep, disconnected, or genuinely gone.
- Send someone. A site visit with the recovery key and a USB is faster and more reliable than any workaround, and it is the honest answer when out-of-band management was never set up.
Out-of-band management is worth configuring on hardware you cannot physically reach, before you need it. It is the difference between a device problem and a travel problem.
Common Mistakes
Not actually an administrator. Remoting succeeds, then the reset command fails with an access denied error. Check whoami /groups inside the session and confirm the account is elevated on the target.
WinRM is disabled or the firewall blocks it. The listener exists in configuration but nothing answers on TCP 5985 or 5986. Test with Test-WSMan from the admin machine, and check the Windows Firewall rules created by Enable-PSRemoting.
Wrong hostname or stale IP address. DHCP leases move. Resolve the name rather than trusting an IP you noted down weeks ago, and confirm the name resolves to the machine you think it does.
Domain credentials used on a workgroup machine. The fix is TrustedHosts plus the local administrator password, not repeated retries with a domain account.
Windows Home edition. WinRM over HTTPS is not configured, there is no built-in MDM, and several of the reset flags behave differently. Treat Home as needing third-party tooling or a hands-on visit.
Confusing reset with format. Reset this PC reinstalls Windows. A clean install from USB media gives you a genuinely fresh system with no leftover accounts, which is what most people actually mean by “factory reset.” Related: Reset this PC can leave the previous owner’s Microsoft account able to reclaim the device during setup, and no remote method fully prevents that on a consumer machine. A clean install from media does.
Losing the BitLocker recovery key. If a reset fails midway on an encrypted drive, Windows will demand the 48-digit key. Without it, the data is unrecoverable no matter how many remote attempts you make.
Closing the only recovery session. Remote Assistance and RDP both drop when the target restarts. Never close your console until the reset is confirmed complete, or you lose the ability to see the out-of-box experience screens.
Before you restart anything, run this checklist: backups exist and you have tested one; the BitLocker recovery key is saved somewhere off the machine; you know which edition and build you are resetting; you have local admin credentials plus the Microsoft account password; you have a USB with Windows media or a person who can reach the PC; and you have tested connectivity from a second device. If all six are true, the reset is routine.
Frequently Asked Questions
Can I reset a Windows PC when it is turned off?
Not through Windows itself. Every built-in remote method depends on software running inside the operating system, so a powered-off PC will accept no commands. You can still reach it with hardware out-of-band management such as Intel AMT, vPro, or a server BMC console, which runs in firmware and can power the machine on and mount installation media. Otherwise, Wake-on-LAN may bring it up if the hardware supports it, or someone has to visit the machine in person.
Which Windows versions support remote reset features?
Windows 10 and Windows 11 both support PowerShell remoting, WinRM, Remote Assistance, and the Reset this PC options. Edition matters more than version: Home lacks a native MDM path and WinRM over HTTPS is not configured by default, while Pro, Enterprise, and Education give you the full set of administrative tools. Recovery Environment options shift slightly between major builds, so check the exact build with Get-ComputerInfo before scripting anything.
Does Windows Reset this PC delete all my files?
It depends on the option you pick. Choose Keep my files and Windows reinstalls the operating system while keeping documents, downloads, and desktop items. Choose Remove everything and personal files are erased too, which is the correct choice when you are wiping a lost or compromised machine. Either way, installed applications and settings are removed. Back up first, because the reset can fail partway and leave you needing the BitLocker recovery key.
How do I reset a remote Windows PC without knowing the administrator password?
You cannot, unless you hold an out-of-band management console or an MDM administrator account, both of which bypass the local password. A forgotten local administrator password cannot be reset remotely by design. If you are an administrator of a domain-joined or Entra ID-joined machine, use the directory account reset instead. For a personal machine whose only admin used a Microsoft account, recovery starts with the Microsoft account itself, not the four-digit PIN.
Why can my PowerShell reset command fail even though the computer is online?
Ping working only proves the network stack answers. The usual causes are that WinRM is not running on the target, the firewall blocks TCP 5985 or 5986, the account lacks administrator rights, or the target is in a workgroup so Kerberos cannot resolve the name. Run Test-WSMan from your admin machine first: if that fails, the problem is transport, not the reset command. If it succeeds, the problem is permissions or the command’s own flags.
Can I remotely reset a PC that is not on my local network?
Yes, as long as a route exists. On a corporate network, route through a VPN or the internet-facing jump host that manages the fleet. Across the open internet, configure WinRM over HTTPS with a certificate, or reach the machine through an out-of-band management console. Plain WinRM over HTTP across the internet is a bad idea because the traffic is not encrypted, so do not port-forward 5985 to the internet. For a home PC, a VPN into the router is the cleaner option.
Conclusion
The safest first move is not a command. Confirm the backup, save the BitLocker recovery key, and write down both the local admin password and the Microsoft account password before you touch the machine. Then identify which remote access route actually exists on that PC: WinRM for an admin machine, Remote Assistance when a person is sitting there, or an out-of-band console if the hardware has one.
Test connectivity with Test-WSMan before you test anything destructive, and start with the least destructive option the machine supports. A repair or a keep-my-files reset fixes more problems than people expect, and you can always go further afterward.
Keep physical or out-of-band access available until the reset is finished and the new installation is confirmed working. On a machine you cannot reach in person, that fallback is the difference between a solved problem and an expensive one. Updated for 2026.
