sodcalculator

10 Tech How-To

How to Find Your Computer’s Uptime in Windows 11

Guide 10-51917 · Updated · Step by step

Knowing your Windows 11 computer’s uptime — how long it has been running since the last restart or shutdown — helps you track system stability, decide when to reboot for updates, or just satisfy your curiosity. This guide shows you several quick ways to check uptime, from the Task Manager to Command Prompt, with no extra software needed.

What You’ll Need

  • A Windows 11 PC or laptop
  • Administrator access is not required for most methods, but one method (PowerShell) works fine without it too.
  • For the Command Prompt and PowerShell methods, you’ll need to type commands — no prior experience necessary.

Step-by-Step

  1. Method 1: Task Manager (Easiest for most users)
    1. Press Ctrl + Shift + Esc to open Task Manager directly. If it opens in compact mode, click “More details” at the bottom.
    2. Click the “Performance” tab in the left sidebar.
    3. Select “CPU” from the list on the left.
    4. Look at the bottom of the main pane — you’ll see “Uptime” with a value like “3:12:45:30” (days:hours:minutes:seconds). That’s your system’s uptime.
  2. Method 2: Command Prompt (Quick and precise)
    1. Press Win + R to open the Run dialog.
    2. Type cmd and press Enter. (Or search “Command Prompt” in the Start menu and click it.)
    3. In the black window, type the following command and press Enter:
      systeminfo | find "System Boot Time"
    4. The output shows the exact date and time your system booted. To get uptime, subtract that from the current time — or use the next method for a direct value.
  3. Method 3: PowerShell (Gives uptime directly)
    1. Right-click the Start button and select “Terminal” or “Windows PowerShell”.
    2. Type the following command and press Enter:
      (Get-Date) - (Get-CimInstance Win32_OperatingSystem).LastBootUpTime
    3. The output shows a time span like 3.12:45:30.1234567 — that’s days.hours:minutes:seconds. The first number before the dot is days.
  4. Method 4: Network Settings (Hidden but handy)
    1. Open Settings (Win + I) and go to “Network & internet” → “Advanced network settings” → “Network adapters”.
    2. Click the “View additional properties” button next to your active adapter (e.g., Ethernet or Wi-Fi).
    3. Scroll down to “Link speed” — you’ll see “Up time” listed there, showing days, hours, minutes, and seconds.

Common Mistakes

  • Mistaking “Up time” in Network settings for system uptime: That value is the time the network adapter has been active, not the whole system. If you’ve toggled Wi-Fi off and on, it resets.
  • Using Task Manager’s “Processes” tab: Some users look for uptime there and don’t find it. It’s only in the Performance tab, under CPU.
  • Forgetting that sleep/hibernate resets nothing: Uptime counts only time the system is actually running. If you put your PC to sleep for 8 hours, that time is not included in uptime.
  • Misreading the PowerShell output: The format is days.hours:minutes:seconds. For example, 2.05:30:00 means 2 days, 5 hours, 30 minutes, not 2 hours.

Tips

  • If you want a more readable uptime in PowerShell, use this command:
    ((Get-Date) - (Get-CimInstance Win32_OperatingSystem).LastBootUpTime).ToString("d' days 'hh' hours 'mm' minutes'")
  • You can also create a desktop shortcut to quickly check uptime: right-click desktop → New → Shortcut, and paste cmd /c systeminfo | find "System Boot Time", then name it “Uptime”.
  • Uptime is a good indicator of when to restart. If it’s been weeks, a reboot can clear memory leaks and speed things up.
  • To see uptime without any command, just open Task Manager and glance at the CPU tab — it’s right there.

Troubleshooting

  • Task Manager shows no Uptime: Make sure you’re on the “Performance” tab and have selected “CPU” on the left. If you still don’t see it, your Task Manager might be in a different view — click “More details” at the bottom first.
  • Command Prompt says “find” is not recognized: This is rare, but if it happens, type systeminfo alone and look for “System Boot Time” in the output. Or use PowerShell instead.
  • PowerShell returns an error: Ensure you typed the command exactly, with no missing parentheses. If you get an error about CIM, try the older command: (Get-Date) - (Get-WmiObject Win32_OperatingSystem).LastBootUpTime.
  • Uptime seems too short: If you recently installed a Windows update, your PC may have automatically restarted overnight. Check Windows Update history to confirm.
  • Network settings “Up time” is missing: This feature appears only for active adapters. If you’re on a virtual adapter or VPN, it might not show. Use Task Manager instead.

Frequently Asked Questions

Does uptime include time in sleep or hibernate?

No. Uptime counts only the time the system is fully powered on. Sleep and hibernate states are not included, so if you sleep your PC for 10 hours, uptime won’t increase during that period.

Why does my uptime reset after a Windows Update?

Windows Update often requires a restart to apply changes. When the system restarts, the boot time resets, so uptime starts from zero again.

Can I check uptime from the login screen?

Yes, but it’s not straightforward. You can press Win + L to lock, then click the power icon and choose “Restart” — after reboot, you can check uptime in Task Manager. But that doesn’t tell you the previous uptime. To see uptime before logging in, you’d need to use a live USB or remote tool, which is overkill for most users.

Is there a way to see uptime in Settings?

Not directly. The closest is the Network adapter “Up time” under Settings → Network & internet → Advanced network settings → Network adapters, but that’s only for the network connection, not the system.

What’s the longest uptime possible?

There’s no hard limit, but Windows updates, driver installations, or power outages usually force a restart. Some users have reported uptimes of months or even years on stable systems, but it’s uncommon.

Can I use uptime to troubleshoot freezing?

Yes. If your PC freezes or slows down after a few days of uptime, a memory leak or driver issue might be the cause. Restarting clears the memory and often fixes the problem. Checking uptime helps you confirm that the issue is time-related.

Related

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 →