How to Reset CPU Uptime (2026 Complete Guide)

You check Task Manager and see CPU uptime stuck at 14 days even though you "shut down" every night. That’s because Windows 10 and 11 enable Fast Startup by default, which saves the kernel state to disk instead of doing a true cold boot. The only way to zero the counter is a full restart—or disabling Fast Startup entirely. In this guide you’ll learn four proven methods to reset CPU uptime, verify the reset, and automate the process so you never wonder again.

What You’ll Need

Item	Details	Cost	Time
Windows 10/11 PC	Admin rights required for registry & scheduler	$0	—
Keyboard / mouse	For shortcuts and menu navigation	$0	—
Terminal (Admin)	Command Prompt, PowerShell, or Windows Terminal	$0	1 min
Registry backup	Export before editing (File → Export in regedit)	$0	30 sec

Step 1: Restart Your PC (The Guaranteed Reset)

Why Shutdown Doesn’t Work

Fast Startup (enabled by default) performs a hybrid shutdown: it hibernates the kernel session and restores it on next boot. The CPU uptime counter survives because the kernel never fully reinitializes. A Restart forces a complete kernel reload, resetting the counter to zero. This behavior dates back to Windows 8 and persists in Windows 11 24H2 because it dramatically reduces boot times on rotational drives and even on NVMe SSDs. However, it also means that any kernel-mode memory leaks, stuck handles, or pending driver updates remain until a true restart occurs.

Fastest Ways to Restart

1. Start Menu: Click Start → Power → Restart.
2. Power User Menu: Press Win+X, then U, then R.
3. Alt+F4 on Desktop: Opens the Shut Down Windows dialog; choose Restart.
4. Command Line: Run shutdown /r /t 0 /f in an admin terminal (see Step 2 for flags).
5. Ctrl+Alt+Del screen: Click the power icon in the bottom-right corner and select Restart.
6. PowerShell one-liner: Restart-Computer -Force (requires admin).

Verify the Reset

Open Task Manager (Ctrl+Shift+Esc), go to Performance → CPU. The "Up time" field should read a few seconds or minutes. If it shows hours/days, Fast Startup is still active—proceed to Step 3. You can also hover over the network icon in the system tray; the tooltip shows "Up time" for the network adapter, which often mirrors the kernel uptime.

Step 2: Command Prompt / Terminal Method (Scriptable & Precise)

Basic Immediate Restart

Open Windows Terminal (Admin) or Command Prompt (Admin). Run:

shutdown /r /t 0 /f

Flags explained:

• /r – full restart (not shutdown)
• /t 0 – zero-second delay
• /f – force-close apps without warning (save work first)

Scheduled Restart with Message

To warn users 60 seconds before reboot:

shutdown /r /t 60 /c "Scheduled uptime reset for system health"

Check Current Uptime via CLI

Two quick commands:

systeminfo | find "System Boot Time"

wmic os get lastbootuptime

The first shows a human-readable timestamp; the second returns a UTC string like 20260515083000.000000+000 (YYYYMMDDHHMMSS). For PowerShell users, (Get-CimInstance Win32_OperatingSystem).LastBootUpTime returns a DateTime object you can format with .ToString('yyyy-MM-dd HH:mm:ss').

Abort a Pending Restart

If you triggered a timed restart and change your mind:

shutdown /a

Step 3: Automate & Make It Permanent (Task Scheduler + Fast Startup Disable)

A. Schedule Automatic Restarts

1. Open Task Scheduler (Win+R → taskschd.msc).
2. Right-click "Task Scheduler Library" → Create Basic Task.
   • Name: Weekly Uptime Reset
   • Trigger: Weekly, e.g., Sunday 3:00 AM
   • Action: Start a Program → shutdown with arguments /r /f /t 0
3. Finish, then double-click the task → Conditions tab: uncheck "Start only if on AC power" for laptops. Settings tab: check "Run as soon as possible after a scheduled start is missed."
4. Optional: On the Actions tab, add a second action to run a script that logs the restart event to a text file for auditing.

B. Disable Fast Startup via Registry (Permanent Fix)

1. Press Win+R, type regedit, press Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power.
3. Find HiberbootEnabled (DWORD). Double-click, change Value data from 1 to 0.
4. Click OK, close Registry Editor, then restart.

After this change, a normal Shutdown (Start → Power → Shutdown) performs a full cold boot. The kernel session is not hibernated, so the next boot reinitializes everything from scratch. This adds roughly 5–15 seconds to boot time on modern NVMe SSDs, but guarantees accurate uptime every time.

C. Alternative: Group Policy (Pro/Enterprise Only)

Run gpedit.msc → Computer Configuration → Administrative Templates → System → Shutdown → "Require use of fast startup" → Disabled. This achieves the same result without touching the registry directly and is preferred in managed environments because it can be deployed via domain policy.

D. Using powercfg for Fine-Grained Control

Advanced users can also manipulate hibernation and Fast Startup via powercfg. Run powercfg /h off to disable hibernation entirely (which also disables Fast Startup because it relies on the hiberfile). To re-enable hibernation but keep Fast Startup off, use powercfg /h on followed by the registry change above. You can also create custom power plans that define different behaviors for lid close, power button, and sleep button via powercfg /setacvalueindex and /setdcvalueindex.

Verify the Change

After restart, do a normal Shutdown (Start → Power → Shutdown). Boot again and check Task Manager → CPU uptime. It should reflect only the time since that boot. If it still shows days, ensure the registry value is 0 and you didn’t use Hibernate. Also check Event Viewer → Windows Logs → System for Event ID 6005 (service control manager started) and 6006 (clean shutdown). A clean shutdown followed by a 6005 at the next boot confirms a full kernel initialization.

Understanding Fast Startup, Hybrid Sleep, and Hibernate

Windows offers three low-power states that affect uptime differently:

• Fast Startup (Hybrid Shutdown): Saves only the kernel session to hiberfil.sys. User sessions are logged off. Boot resumes kernel, then starts fresh user session. Uptime counter persists.
• Hibernate: Saves entire system state (kernel + user sessions + open apps) to hiberfil.sys. Power is cut. Resume restores everything exactly. Uptime counter continues.
• Hybrid Sleep: Designed for desktops. Writes RAM to hiberfil.sys then enters S3 sleep. If power fails, it resumes from hiberfile. Uptime counter continues during sleep.
• Sleep (S0 Modern Standby / S3): Keeps RAM powered. Kernel uptime counter runs continuously.

Only a full Restart (or Shutdown with Fast Startup disabled) resets the kernel uptime counter to zero. This distinction matters when troubleshooting driver issues, memory leaks, or Windows Update installations that require a true reboot.

Pro Tips

• Use Windows Terminal profiles: Create a "Restart Admin" profile that runs shutdown /r /t 0 /f on launch for one-click resets. Open Settings → Profiles → Add new profile → Command line: cmd /k shutdown /r /t 0 /f.
• Monitor uptime remotely: PowerShell Get-CimInstance Win32_OperatingSystem | Select-Object LastBootUpTime works over WinRM for headless boxes. For bulk queries, use Invoke-Command -ComputerName (Get-Content servers.txt) -ScriptBlock { (Get-CimInstance Win32_OperatingSystem).LastBootUpTime }.
• Pair with driver updates: Schedule the automatic restart right after your GPU driver’s auto-update window (usually early morning) so new drivers load cleanly. NVIDIA and AMD installers often schedule a restart; aligning your Task Scheduler task avoids double restarts.
• Laptop users: If you disable Fast Startup, expect 5–15 s longer boot. Offset by enabling "Turn on fast startup" only for the lid-close action via powercfg /h off and custom power plan. Actually, you can't have both; but you can keep hibernation enabled for lid close while disabling Fast Startup for the power button by editing the power plan's "Power button action" and "Lid close action" separately in Control Panel → Power Options → Choose what the power buttons do.
• Document your baseline: After a clean Windows install, note the boot time (Event ID 100 in Microsoft-Windows-Diagnostics-Performance/Operational log). Future deviations help spot unwanted background services.
• Use a dedicated logging script: Append date /t && time /t && systeminfo | find "System Boot Time" to a log file on each restart via Task Scheduler action. This builds a history without third-party tools.

Common Mistakes + Fixes

Mistake	Solution
Using Shutdown instead of Restart	Fast Startup preserves kernel. Always choose Restart or disable Fast Startup.
Forgetting to save work before forced restart (/f)	Omit /f for interactive restarts, or use a 60-second warning with /t 60.
Editing registry without backup	Export the whole registry (or at least the Power key) before changing HiberbootEnabled.
Scheduling restart during active work	Set trigger for 3–4 AM; enable "Run only if network available" to avoid waking sleeping laptops.
Assuming Hibernate resets uptime	Hibernate saves RAM to disk; uptime continues. Use Restart or full Shutdown (Fast Startup off).
Disabling hibernation entirely on laptops	This removes the ability to hibernate, which some users rely on for battery preservation. Only disable Fast Startup, not hibernation, unless you never use hibernate.
Not testing after registry change	Always perform a Shutdown + cold boot and verify uptime reset before assuming it worked.

How We Verified This Guide

We tested each method on a clean Windows 11 24H2 installation (build 26100) and a Windows 10 22H2 VM. Uptime was measured via Task Manager, systeminfo, and WMI before and after each operation. Fast Startup behavior was confirmed by checking the HiberbootEnabled registry value and observing boot-event IDs 6005/6008 in Event Viewer. No third-party tools were used; all steps rely on native Windows utilities documented by Microsoft Learn.

FAQ

Does high CPU uptime damage my computer?

No. Modern CPUs are rated for continuous operation. However, extended uptime can accumulate memory leaks, orphaned handles, and pending updates that degrade responsiveness. A weekly restart is a low-effort hygiene habit.

Why does my uptime show 1 day after a morning restart?

You likely used Shutdown (not Restart) the previous night, so Fast Startup restored the old kernel. The "1 day" is the time since that restored kernel booted. Use Restart or disable Fast Startup to zero the counter.

Can I check uptime without opening Task Manager?

Yes. Run systeminfo | find "System Boot Time" in Command Prompt, or wmic os get lastbootuptime for a machine-readable timestamp. PowerShell: (Get-CimInstance Win32_OperatingSystem).LastBootUpTime.

Does restarting affect SSD lifespan?

Negligibly. A restart writes a few megabytes (kernel state, registry). Modern SSDs endure hundreds of terabytes written; daily restarts for decades won’t matter.

Why does uptime reset to 1 day instead of 0 after restarting?

A small time drift between the kernel’s boot timestamp and the moment you check Task Manager can show a few seconds as "1 day" if the display rounds. Ensure you used Restart, not Shutdown, and verify Fast Startup is off.

Is there a way to see uptime history over time?

Windows doesn’t log a continuous uptime graph, but Event Viewer (Windows Logs → System, filter Event ID 6005 for boots, 6006 for clean shutdowns, 6008 for unexpected shutdowns) gives a reboot timeline. Third-party tools like HWiNFO64 can log it continuously.

Should I restart my home server to reset uptime?

Home servers benefit from monthly restarts to apply updates and clear leaks. Enterprise clusters use rolling restarts; for a single box, schedule a monthly maintenance window.

Does sleep mode reset CPU uptime?

No. Sleep keeps RAM powered; the kernel’s uptime counter continues. Only a full Restart or a Shutdown with Fast Startup disabled resets it.

Can I reset uptime without restarting or shutting down?

Not legitimately. The counter is maintained by the kernel; any userspace tool that claims to reset it only changes the displayed value, not the actual hardware counter.

What about Windows Update’s automatic restarts?

Windows Update schedules restarts outside active hours. Those restarts are full kernel reinitializations, so they reset uptime. You can view the update restart history in Settings → Windows Update → Update history.

Does disabling Fast Startup affect BitLocker or Secure Boot?

No. Fast Startup is independent of BitLocker drive encryption and Secure Boot. Disabling it only changes the shutdown/boot path.

Can I use a third-party tool to schedule restarts?

Yes, tools like Shutter, Auto Power-on & Shutdown, or even simple Task Scheduler scripts work. Native Task Scheduler is preferred because it requires no extra software and integrates with Windows power management.

Sources

• Microsoft Learn: Fast Startup overview
• Microsoft Learn: shutdown command reference
• Microsoft Learn: Win32_OperatingSystem WMI class

Conclusion

Resetting CPU uptime is really about forcing a true kernel reinitialization. The simplest path: hit Restart instead of Shutdown. For automation, schedule a weekly shutdown /r /f /t 0 task. For a permanent fix, flip HiberbootEnabled to 0 in the registry (or use Group Policy). Pair these habits with regular driver updates and you’ll avoid the memory leaks and stale updates that make long-uptime systems feel sluggish. If you’re troubleshooting deeper power issues, our guide on how to fix a loose monitor power cable covers related hardware checks, and if you’re shopping for a budget machine that handles restarts snappily, see our picks for best budget laptops under $700.