Keeping a PC Awake During Long Downloads, Renders and Backups
A render that dies at three in the morning is almost never a crash. It is a power setting. Here is how to work out which one, and how to set a machine up so long jobs actually finish.
Diagnose before you change anything
Start by finding out what happened, rather than guessing. Windows records power transitions in the event log, and there is a much faster way to read them:
Windows: open Command Prompt and run powercfg /sleepstudy. It writes an HTML report of every sleep and wake event with timestamps and causes. powercfg /lastwake tells you what woke it most recently, and powercfg /requests shows what is currently holding it awake.
macOS: run pmset -g log | grep -e "Sleep" -e "Wake" in Terminal for a chronological list of sleep and wake events, each with a reason string.
If the timestamps line up with your job dying, it slept. If they do not, the job failed for its own reasons and no amount of power configuration will help.
The four things that kill long jobs
1. System sleep
The obvious one. The machine suspends to RAM, all processing stops, and your job resumes hours later - or fails outright because a network connection timed out while it was suspended.
Fix: Windows - Settings → System → Power & battery → sleep timeout to Never when plugged in. macOS - Battery → Options → "Prevent automatic sleeping on power adapter when the display is off", or run the job under caffeinate -i.
2. Hibernation
Sneakier, because it can trigger after sleep. A machine that sleeps at midnight may hibernate an hour later, writing memory to disk and powering off completely. Network transfers do not survive this.
Fix: control powercfg.cpl → Change plan settings → Change advanced power settings → Sleep → Hibernate after → 0 (Never) for the plugged-in state.
3. Disks and USB devices powering down
This is the one people never suspect. Windows can spin down an idle hard disk, and USB selective suspend can power down a port. If your render is writing to an external drive that just disappeared, the job fails while the computer itself is wide awake.
Fix: in the same advanced power settings dialog, set "Hard disk → Turn off hard disk after" to 0, and disable "USB settings → USB selective suspend".
4. Network adapter power saving
Windows permits the network card to be powered down to save energy. During a large download this shows as a transfer that stalls at some arbitrary percentage.
Fix: Device Manager → Network adapters → your adapter → Properties → Power Management → untick "Allow the computer to turn off this device to save power".
Setting up for an overnight job
- Plug in. Nothing else matters on battery.
- Set sleep and hibernate to Never for the plugged-in state.
- Leave the display timeout short. Turning the screen off does not affect the job and saves power and panel wear. This is the setting you want active.
- Disable disk spin-down and USB selective suspend if any external storage is involved.
- Keep the lid open if the job is CPU or GPU heavy - see the thermal warning.
- Start a keep-awake tool as a belt-and-braces measure - PowerToys Awake without "keep screen on", or
caffeinate -i ./your-job.
The best pattern on macOS: caffeinate -i ./render.sh. The Mac stays awake for exactly as long as the script runs and sleeps normally the moment it finishes. Nothing to remember to turn off.
When you cannot change the settings
On a managed work machine the power plan is usually locked. Two things still work:
An approved keep-awake utility. Worth asking IT - render and build workstations are a recognised case and there is often a sanctioned answer.
Input-based keep-awake. A hardware jiggler or a browser-based one resets the idle timer, which addresses idle-triggered sleep and idle-triggered lock. It cannot prevent a scheduled shutdown or a policy-driven forced log-off, but idle sleep is the common case.
Application-level settings people forget
Some tools have their own opinions about power:
- Render software (Blender, DaVinci Resolve, Premiere) sometimes has a "prevent system sleep during render" option. Check it is on.
- Download managers often offer "prevent sleep while downloading" - and some offer "sleep when finished", which is genuinely useful.
- Backup tools such as Time Machine hold their own power assertions while running, and generally handle this correctly on their own.
- Virtual machines do not stop the host sleeping. If the host sleeps, so does the guest, mid-write.
Verify before you rely on it
Do not test your configuration with the eight-hour job. Set a short sleep timeout - two minutes - start something trivial, and confirm the machine stays awake past the deadline. On Windows, powercfg /requests should show your tool or application holding a display or system assertion. On macOS, pmset -g assertions shows the same thing.
Two minutes of testing is worth considerably more than a lost overnight render.