To ensure a computer automatically restarts after a power loss, you must configure the BIOS/UEFI "AC Power Recovery" setting to "Power On" and enable Wake-on-LAN if remote management is required. While operating system-level scripts can monitor uptime, they cannot trigger a reboot from a completely powered-off state; hardware firmware settings are the only reliable method for this specific failure mode.
Understanding Hardware vs. Software Control
A common misconception in IT support is that software tools like systemd or Windows Task Scheduler can force a machine to boot up after it has lost all electrical power. This is technically impossible because an operating system requires power to execute instructions. When the power cord is unplugged or the grid fails, the CPU halts immediately. Therefore, any solution relying solely on OS-level configuration will fail to address the core requirement of restarting after a complete power outage.
The responsibility for handling AC power events lies with the motherboard firmware, specifically the Basic Input/Output System (BIOS) or Unified Extensible Firmware Interface (UEFI). These low-level programs run before the operating system loads and have direct access to the power management circuits. By configuring these settings, you instruct the hardware to send a signal to the power supply unit (PSU) to begin the startup sequence as soon as electricity is restored.
Configuring BIOS/UEFI Settings
The primary step involves accessing the server or workstation's firmware interface. Restart the computer and press the designated key during the POST (Power-On Self-Test) phase, typically Delete, F2, or F10, depending on the manufacturer. Once inside the BIOS menu, navigate to the Power Management section. The exact location varies by vendor, but look for options labeled Restore on AC/Power Loss, AC Back, or After Power Failure.
- Power On: Select this option to ensure the machine boots immediately when power returns. This is the standard setting for servers and critical workstations.
- Last State: This setting restores the machine to the state it was in before the power cut. If the machine was off, it stays off. If it was on, it resumes. This is less desirable for automated recovery scenarios.
- Power Off: The machine remains off until manually started. Avoid this for auto-restart requirements.
After selecting Power On, save the changes and exit. Most systems use F10 to save and reboot. It is crucial to test this setting by unplugging the power cable while the machine is running and plugging it back in to verify the behavior. Note that some consumer-grade motherboards may not offer granular control over this feature, limiting your options to just "On" or "Off."
Enabling Remote Management Capabilities
While BIOS settings handle the physical boot process, remote configuration often implies the ability to manage the device over a network. For this, you need out-of-band management solutions that operate independently of the host operating system. Technologies like Intel vPro (AMT), AMD Pro, or IPMI (Intelligent Platform Management Interface) allow administrators to power cycle machines remotely even if the OS is crashed or the machine is off.
If your infrastructure supports these standards, you can configure the management controller to set the default power state upon AC restoration. Additionally, enabling Wake-on-LAN (WoL) in both the BIOS and the network card driver allows you to send a magic packet to wake the machine from a low-power sleep state, though WoL generally does not work from a fully powered-off state unless supported by specific modern standby features.
For environments without dedicated management hardware, consider using a smart UPS (Uninterruptible Power Supply) with network management cards. These devices communicate with the server via SNMP or web interfaces. You can configure the UPS to send a graceful shutdown command during a prolonged outage and then initiate a remote power-on command once utility power is stable again. This adds a layer of safety against data corruption during sudden power cuts.
Operating System Level Monitoring
Although the OS cannot start the machine from zero power, it can prepare for recovery. Configure your monitoring agents to detect unexpected reboots and log them. This helps distinguish between planned maintenance and accidental power losses. In Linux, checking /var/log/syslog or dmesg for timestamps related to ACPI events can provide evidence of when power was restored. In Windows, check the Event Viewer under System logs for Event ID 6008 (unexpected shutdown) or 41 (kernel power error).
By combining firmware-level auto-boot settings with robust remote management protocols, you create a resilient system that recovers autonomously from power failures. Always prioritize hardware settings for the initial boot, as they are the most reliable mechanism for ensuring availability after a blackout.
Frequently Asked Questions
Can I use a script to restart my PC after a power outage?
No, a script cannot execute if the computer is completely powered off. Scripts require the operating system and CPU to be active. You must rely on BIOS/UEFI settings to initiate the hardware boot process when power returns.
What happens if I select "Last State" in BIOS?
If the computer was shut down before the outage, it will remain off when power returns. If it was running, it will resume operation. This setting is risky for automated services that need to be online immediately after a blackout.
Does Wake-on-LAN work after a total power loss?
Generally, no. Wake-on-LAN requires the motherboard to have standby power to listen for the magic packet. After a total power loss, the NIC is usually unpowered unless the BIOS explicitly enables "Wake on LAN from Soft Off" or similar S5 states, which is rare on older hardware.
How do I find the correct BIOS key for my machine?
Check the manufacturer's website or look at the splash screen during startup. Common keys include Delete, F2, F10, and Esc. Server hardware often uses F11 or F9 for boot menus or F1 for setup.
Is it safe to leave a computer set to "Power On" after AC loss?
Yes, it is safe and recommended for servers. However, ensure your surge protection is adequate, as frequent power cycling can stress components. Using a UPS is highly advised to smooth out power transitions.