How to wake your home PC from university (and put it back to sleep after)
The powerful desktop is at home; you are in halls with a laptop that cannot run the coursework software, does not hold the files, and will not play anything recent. The desktop does not have to be switched on all term to be useful to you: it can sleep at a few watts, hold itself awake while you are actually working on it, and drop back to sleep when you stop. Neither of the usual answers is necessary — leaving it on all term at forty to a hundred watts on your parents’ electricity, or messaging somebody at home to press the button — because a machine can be woken from anywhere in seconds by a packet sent inside the house.
This guide is the arrangement for a student away in term time: the settings to change before you leave, what at home sends the wake — the family's Echo or a machine that is on anyway, so nobody at home presses anything and you never touch the router — how to wake the desktop from halls and know it is up, how to stream a game from it, and how it goes back to sleep. It ends with the Mac and laptop cases and the seven reasons a wake does nothing.
Why halls Wi-Fi does not matter
What wakes a sleeping PC is a magic packet: a broadcast on the machine's own network, carrying the network card's address, that the card listens for while the rest of the machine is off. A broadcast does not cross the internet, so the wake is never sent from halls. Something in the house sends it, and what you do from halls is ask that thing to.
That is why the university's network is irrelevant. Nothing halls Wi-Fi does — blocking inbound traffic, sharing one address between a thousand rooms — is in the path. Your laptop or phone talks to a service over an ordinary outbound connection, the sender at home holds its own outbound connection to the same service, and the packet goes out from inside the house. Nothing is forwarded at the home router, your parents' public address can change every week, and halls Wi-Fi, eduroam, the campus VPN and a phone on 4G all work identically. Wake-on-LAN without port forwarding covers the mechanics; how to wake a PC remotely is the any-machine version of this page.
Before you leave: make the PC wakeable
Do this at the desk before you leave; nothing on this page can fix a setting here from a hundred miles away. Four places, in this order, because each can hide the next. With the free agent on the PC, the Wake readiness section in the machine's settings on the dashboard reads the second and third for you and offers to fix both — on a Linux PC, the second alone, there being no fast startup to turn off; the compatibility check gives the exact click-path for doing it by hand.
- BIOS or UEFI: turn on Wake on LAN. Boards call it Wake on LAN, Power On By PCI-E, Resume by LAN or Wake on PCI-E, usually under Power. If the board has ErP Ready, EuP 2013 or a deep-sleep option, turn it off: it cuts standby power to the network card and undoes everything else here.
- Device Manager: let the adapter wake the machine. On the Ethernet adapter's Power Management tab, tick Allow this device to wake the computer and Only allow a magic packet to wake the computer. On the Advanced tab set Wake on Magic Packet to Enabled.
- Power Options: turn fast startup off. Control Panel, Power Options, Choose what the power buttons do, Change settings that are currently unavailable, then untick Turn on fast startup. With it on, Shut down is a partial hibernation that parks the network card un-armed — and Shut down is what a parent tidying the room will choose.
- Use the cable, and leave it asleep rather than off. Ethernet wakes reliably; Wi-Fi wakes rarely, from sleep only, and never on a laptop. Asleep, the PC draws two to five watts and comes back in seconds, so Sleep is the state to leave it in and to ask the household for; set Hibernate after to Never under Change advanced power settings, or it hibernates a few hours into term.
Choose what at home sends the wake
The packet leaves from inside the house, so the choice is which thing at home sends it — for a student, whichever is already there. Four things can, and any one is enough; none is the desktop itself, and none needs anybody at home to do anything after setup day. How to wake a PC remotely walks each one.
Scroll the table sideways to see every column.
| Choose what at home sends the wake | What it costs | What can trigger it | The one limit |
|---|---|---|---|
| An Amazon Echo you already ownOur free, certified Alexa skill has the Echo broadcast the packet on the home network; a tap in the Alexa app from halls reaches it. | Nothing | "Alexa, turn on the study PC", and a tap in the Alexa app from anywhere in the world. | Voice and the Alexa app only. The dashboard, the phone app, schedules, wake links on Pro, the API and the Claude connector all need one of the rows below. |
| The free agent on a machine that already stays onA parent's desktop that never sleeps, the family NAS, a Raspberry Pi — or a container on any of them. Never the desktop you want to wake. | Nothing | Everything: the dashboard, the phone app, voice and the Claude connector — plus schedules and the API on the paid plans, and wake links on Pro. | Needs a machine that stays on. An agent cannot wake the machine it runs on. |
| A certified smart plugFor a machine that starts when power is applied — most desktop PCs can be set to, and Apple-silicon desktop Macs do. The certified models. | About £10 | Power on and power cycle from the dashboard, through an agent or dongle that reaches the plug — on the paid plans. | The machine must start when power returns: a cold boot, not a resume. |
| A dongle you buildA Raspberry Pi Pico W and a few parts, for the house where nothing else stays on. The parts list names them. | About £17 in parts | Everything the agent carries. | A small build: flash it from your browser, print or buy a case. |
- The family's Echo. Enable the skill, link your Rooster Wake account, and give it the desktop's name and address; the Echo at home then puts the packet on the home network when you ask from the Alexa app in halls — free on every plan.
- The free agent on a machine at home that stays on. Install it on a parent's always-on desktop, the family NAS or a Raspberry Pi — or as a container on the NAS — and that box sends for every other machine in the house. It cannot wake the machine it is installed on.
- A certified smart plug. For the desktop somebody shut down, or one that has frozen: it cuts and restores the mains, and a PC set to start when power returns boots from cold, on the paid plans.
- A dongle you build. A Raspberry Pi Pico W in a printed case, for the house where nothing stays on: half a watt behind the router, and everything the agent carries.
From halls: wake it, see it come up, connect
With a sender in place the desktop is a row on your dashboard, and the row carries a green Wake button. Press it from halls and the packet goes out on the home network a second or two later. With the free agent on the desktop itself, the row turns green the moment the machine is up — up now — agent connected — on every plan, usually within twenty seconds. On Plus and Pro, wake confirmation watches the home network for the machine answering and tells you it came up, or that it did not and why, pushed to your phone.
The button is one of several ways to ask. By voice, the free skill has the Echo at home do the same from a tap in the Alexa app anywhere; a schedule on the paid plans does it at seven on the evenings you always work; "wake my desktop" in any Claude chat does it in words, on every plan.
Then connect with whatever the job needs: Remote Desktop for the coursework software, Moonlight or Parsec for a game. Store the client's own link against the machine and the row carries a Remote Desktop button that opens it, whatever the link's scheme; pressed while the desktop is asleep it wakes, waits for the free agent to say the machine is up, and opens the link as one press, and on Plus and Pro holds the machine for ten minutes while you sign in. If you unlock the desktop with a PIN or a fingerprint, read the sign-in trap before term starts: a remote session wants the account password.
Streaming a game from the rig at home to a laptop in halls
The most common reason a student wants any of this is a game the laptop cannot run. Steam's own streaming, Moonlight with Sunshine on the host, and Parsec all do the same job: the desktop at home runs the game and streams the picture to the laptop. All of them share one limit — the client can only find a host that is already awake, because the host software is asleep with the machine — and none can send the wake from outside the house.
So the order is always the same. Wake: press Wake on the row, or ask through the free skill. Confirm: wait for up now — agent connected, the free agent on the desktop saying the machine is genuinely up rather than that a packet was sent. Connect: open the client, and the host is there. With the client's own link stored — moonlight://, parsec://, or your remote-desktop address — the row's Remote Desktop button does all three as one press.
Before you leave, sign in to Steam and the launchers on the desktop, so a session from halls is not stuck at a two-factor prompt on a screen you cannot see, and pair the streaming client once over the home network. Waking a gaming PC remotely covers the rig's own settings; waking your PC for Steam Link, Moonlight or Parsec is the streaming page.
Putting it back to sleep from halls
Waking needs nothing on the desktop; sleeping does, because something has to ask Windows to suspend. That is the free agent on the desktop, and with it there the row carries Sleep: press it from halls when you finish and the machine suspends in seconds. The free plan includes ten sleeps a calendar month; Plus and Pro are unmetered and add Restart… and Shut down… beside it.
Keep awake…, on Plus and Pro, is the other half: hold the desktop up for a window you choose — a render, a download, a long session — and the row shows the deadline. When the timer ends the machine goes back to sleep by itself unless somebody is using it, on Windows, macOS and Linux. A machine on a certified plug shuts down cleanly instead, because it comes back by cold boot rather than resume, and the switch stays on for the next Wake to cycle it.
The agent on the desktop cannot wake the machine it runs on — asleep, it is asleep along with it — so it does not replace the sender at home.
If the machine at home is a Mac, or a laptop
A Mac wakes by packet over Ethernet only, from sleep only, and never from full power-off. Turn on Wake for network access, keep it on mains and on a cable, and every sender above brings it back from sleep as it would a PC; the free agent runs on it too, from its installer package, so the row reads the sleep when it happens, offers Wake, and offers to turn that setting on for you — Prepare for wake, in the row's Wake readiness section. An Apple-silicon Mac mini or Mac Studio starts when power is applied, so a certified plug on the paid plans is its route from off.
A MacBook on Wi-Fi cannot be woken by packet at all, and the same is true of a Windows laptop. A laptop left at home is reachable only if it lives on a dock with a cable and on mains, asleep — off the dock, nothing on this page reaches it.
When the wake does nothing
Nearly every "it does not wake" is one of these seven, each with a check — six to run at the desk before you leave, one about the house rather than the machine. The top ones are the most common, and each can mask the next.
- The adapter setting is off. Check Device Manager, the Ethernet adapter: Allow this device to wake the computer ticked under Power Management, Wake on Magic Packet Enabled under Advanced. A driver update can silently reset both; with the free agent on the machine, the dashboard's Wake readiness section catches it and offers the fix.
- Fast startup is on, and you shut down. The machine is hibernated, not off, and the card is parked un-armed. Check Choose what the power buttons do: Turn on fast startup unticked. Or sleep the machine instead — sleep is the state the packet is best at.
- The machine was off, not asleep. From full power-off a PC listens only if the BIOS keeps the card fed and the driver's after-shutdown wake is on; a Mac never listens. Check: sleep it, send the wake, and if that works the missing setting is the BIOS one.
- It is on Wi-Fi. Check whether the cable is in. Waking over Wi-Fi works from sleep only when it works at all, and never on a laptop.
- Wrong network. A broadcast does not cross a VLAN, a guest Wi-Fi, a client-isolated network or, on some mesh systems, a different node. Check that the sender and the machine share a segment — same switch, off the guest network.
- A BIOS power setting. ErP Ready, EuP 2013, deep sleep, or a mode that cuts the standby rail. Check the BIOS's power page with all of those off and Wake on LAN on — and take the right address:
getmac /v, the Ethernet row, never a virtual adapter's. - Somebody at home switched the router off, or unplugged the sender. A router off at night, a NAS shut down to save electricity, or a plug pulled out to charge a phone all look the same from halls: the wake fails, and the history says the sender was offline. Check the emitters page, which says when each sender was last seen; on the paid plans an alert reaches your phone when one stops reporting. Then ask the household for one thing — leave the router and the sender on — and put the desktop on a schedule on the paid plans, so trouble shows as a morning message rather than a missed deadline.
What it costs to leave it on all term
A desktop idling with the monitor off is commonly 40 to 100 watts, a gaming machine more, and a ten-week term is 1,680 hours. At 60 watts that is about 100 kWh a term left on, against roughly five asleep — multiply by the household's tariff, the only figure that matters. Across a year it is a few hundred kilowatt-hours on somebody else's electricity, which wins the argument about leaving it plugged in.
The other half is not money: a sleeping machine is quiet, cool, and exposes nothing — which matters if you forwarded a Remote Desktop port at the home router before leaving. The exposed Remote Desktop check says whether that port is answering the internet; the free agent reports it on every plan. Other shapes of the problem — a rig you stream from anywhere, a work desktop, a NAS in a cupboard — are mapped in who uses Wake-on-LAN, with a guide for each.