How to Check System Uptime in Windows

This guide shows you several ways to check how long your Windows PC has been running since its last boot. You’ll learn quick commands, Task Manager tricks, and PowerShell options—no extra software needed.

What You’ll Need

A Windows PC (Windows 10 or Windows 11 recommended, but most steps work on Windows 8/8.1)
Permission to open Command Prompt, PowerShell, or Task Manager (standard user accounts can do all of these)

Step-by-Step

Method 1: Use Task Manager (Quickest)

Press Ctrl + Shift + Esc to open Task Manager directly. If it opens in compact mode, click More details at the bottom.
Click the Performance tab on the left sidebar.
Select CPU in the left panel. The right side shows a graph and stats.
Look for Up time near the bottom of the CPU section. It displays something like 3:45:12:30 (days:hours:minutes:seconds).

Method 2: Use Command Prompt

Press Win + R, type cmd, and press Enter. Or search for “Command Prompt” in the Start menu and open it.
Type the following command and press Enter:
systeminfo | find "System Boot Time"
The output shows the exact date and time your system last booted. For example: System Boot Time: 10/15/2024, 9:42:17 AM.
To see uptime as a duration (days, hours, minutes), use this instead:
net statistics workstation | find "Statistics since"
This shows when the workstation service started—usually your boot time.

Method 3: Use PowerShell

Right-click the Start button and select Windows PowerShell (or Terminal on Windows 11).
Type this command and press Enter:
(Get-Date) - (Get-CimInstance Win32_OperatingSystem).LastBootUpTime
PowerShell returns a time span like Days : 2 Hours : 5 Minutes : 12 Seconds : 33. That’s your uptime.
For a one-line summary, use:
Get-CimInstance Win32_OperatingSystem | Select-Object LastBootUpTime

Method 4: Use the System Information Tool

Press Win + R, type msinfo32, and press Enter.
In the System Summary section, look for System Up Time in the right pane. It shows a duration like 2:05:12:33 (days:hours:minutes:seconds).

Common Mistakes

Confusing boot time with uptime: The system boot time is a date/time stamp; uptime is the elapsed duration since that stamp. Both are useful, but they answer different questions.
Using the wrong command syntax: Typing systeminfo | find "Boot Time" without the exact phrase may return nothing. Use the full string System Boot Time including spaces.
Reading the Task Manager value wrong: The format is days:hours:minutes:seconds. If it says 0:12:34:56, that’s 12 hours, 34 minutes, 56 seconds—not 12 minutes.
Forgetting that sleep/hibernate resets the counter: Uptime counts time since the last full boot, not since you last woke the PC from sleep. If you’ve been using sleep, uptime will be much longer than your actual session.
Running commands without admin rights: Most uptime commands work fine as a standard user, but some older methods might need admin. If you get “access denied,” right-click and run as administrator.

Tips

For a quick visual check without typing, Task Manager is the fastest method—just two clicks after opening it.
If you need uptime for scripting or monitoring, PowerShell’s Get-CimInstance is the most reliable and script-friendly.
To see uptime in a clean format (e.g., “2 days, 5 hours”), you can use PowerShell with formatting:
$uptime = (Get-Date) - (Get-CimInstance Win32_OperatingSystem).LastBootUpTime; "$($uptime.Days) days, $($uptime.Hours) hours, $($uptime.Minutes) minutes"
If you’re troubleshooting a network or performance issue, note the boot time—it can help you correlate when a problem started.
On Windows 11, you can also see uptime in the Task Manager’s Performance tab under CPU, same as Windows 10.

Troubleshooting

Command Prompt says “find” is not recognized: This is rare, but if you’re using a minimal environment, use PowerShell instead. Or type the full path: systeminfo | %{$_ -match "System Boot Time"} in PowerShell.

Task Manager doesn’t show “Up time”: Make sure you’re on the Performance tab and have selected CPU (not Memory or Disk). The uptime is only shown on the CPU page in most versions. If you don’t see it, try widening the window or scrolling down.

PowerShell returns an error like “Get-CimInstance not recognized”: This happens on very old PowerShell versions (2.0). Use the older WMI command instead:
(Get-Date) - (Get-WmiObject Win32_OperatingSystem).LastBootUpTime

The uptime seems too long or too short: Remember that Windows updates, driver installations, or system crashes can reboot your PC without you noticing. Also, if you use Fast Startup (default on many PCs), the “boot time” might be from a hybrid shutdown—check your power settings if this matters.

You get “Access Denied” when running systeminfo: This can happen if your user account has limited rights. Right-click Command Prompt and choose “Run as administrator,” then try again.

Frequently Asked Questions

Q: Does uptime reset when I put my PC to sleep?
A: No. Sleep and hibernate preserve the uptime counter because the system doesn’t fully shut down. Only a restart, shutdown, or crash resets it.

Q: Can I check uptime on a remote Windows computer?
A: Yes. Use PowerShell with Get-CimInstance -ComputerName "REMOTE-PC" Win32_OperatingSystem | Select-Object LastBootUpTime, but you need admin rights on that machine and network access.

Q: Why does Task Manager show uptime but not the boot time?
A: Task Manager shows the elapsed duration, not the date/time of boot. For the exact boot time, use Command Prompt’s systeminfo or PowerShell.

Q: What’s the difference between “System Boot Time” and “System Up Time”?
A: Boot time is a specific date and time (e.g., Oct 15, 2024 9:42 AM). Up time is the duration since that moment (e.g., 2 days 5 hours). Both are derived from the same underlying data.

Q: Is there a way to see uptime without any command line?
A: Yes. Task Manager (Method 1) and System Information (Method 4) are both graphical and require no typing.

Q: Does uptime affect performance?
A: Not directly. However, long uptimes can mean many background processes have accumulated, and some memory leaks in drivers or apps may slow things down. A reboot often clears those issues.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →