Measure the time Windows 11 (and Windows 10) has been on: methods, tricks, and limitations

Knowing how long your PC has been running isn't just a matter of curiosity: it can give you clues about its performance, power consumption, and overall health . It also helps you decide whether it's best to shut down or restart to improve performance, or if something seems off and warrants further investigation.

In Windows 11 and Windows 10, there are several reliable ways to obtain uptime data , from Task Manager to Terminal , and also more advanced methods like Event Viewer. Below is a complete guide that covers the steps, version differences, actual limitations (sleep, hibernation, Modern Standby, restarts due to updates), and alternative tools for viewing the history.

Quick methods in Windows 11 and Windows 10

If you're looking for an immediate check, Task Manager is the quickest way to see the Uptime since the last full system boot . It's a clear indicator of how long your computer has been running continuously.

• Open Task Manager with Ctrl + Shift + Esc or right click on Start and enter its shortcut.
• In Windows 11, go to the left side menu and click on Unlimited; in Windows 10, the same section appears at the top of the window.
• Choose CPU and, under the real-time graph, locate the field Active timeThis value shows how long the PC has been running since the last boot.

This method is quick and visual , but keep in mind that it only shows the current session since the last shutdown/restart. If you need historical data (days, weeks, or months), you'll find the Event Viewer and a portable utility below that provide this information.

Terminal, CMD, and PowerShell: Precise query by command

Windows command prompts offer very handy commands for obtaining system uptime without opening graphical interfaces. They are useful if you prefer a precise, text-based output format or if you automate checks.

In PowerShell you can calculate the time since the last boot with this command, which subtracts the start time from the current time to return the duration in days, hours, minutes and seconds:

(get-date) - (gcim Win32_OperatingSystem).LastBootUpTime

The output includes various time formats and clearly shows how long it has been since the computer was shut down or restarted . If you prefer a classic approach, you can extract the timestamp of the last boot in the Command Prompt ( CMD ) with:

systeminfo | find "Tiempo de arranque del sistema"

Both approaches are reliable and fast , and complement the Task Manager. PowerShell, in particular, is perfect for scripts or scheduled diagnostic tasks.

Event Viewer: History of power-ups, power-downs, and suspensions

The Event Viewer is the "official" Windows log. It records every system event grouped by category, allowing you to investigate in detail when the computer started, shut down, or went to sleep , as well as errors and warnings.

To open it, use Windows search by typing Event Viewer , or press Windows + R and run eventvwr (or eventvwr.msc ). Then, navigate to Windows Logs > System.

From there you can filter by different event IDs related to power and startup. There are two useful groups depending on the type of log you want to analyze:

• ID 12 (system startup), ID 13 (off), ID 1 (suspension output) and ID 42 (standby). They give you a clear timeline of power-on and low-power states.
• ID 6005 (the event log service was started) and ID 6006 (the service stopped). They are another way of inferring starts and shuts down of the operating system.

To narrow your view, use “ Filter current record… ” in the right-hand column and enter the IDs separated by commas (for example, 12,13,1,42 or 6005,6006 ). You can further refine the time period under “Registered” and even filter by user or keywords if you're looking for something specific.

A practical example: if you see a 6006 followed shortly after by a 6005 , a reboot (or a very rapid power cycle) has likely occurred. If a 6008 appears , the system indicates that it "started after an improper shutdown," which is useful for detecting a hang or power outage. And 6013 shows the accumulated uptime reported by the system.

This history is ideal for administrators, but also for any user who wants to check if the computer was on while they were away , or if someone else used it. If you explore it carefully, you'll see thousands of entries, each with a date and time stamp, allowing you to reconstruct your usage timeline.

Factors that affect the count: sleep, hibernation, Modern Standby, and updates

Not every startup or shutdown "counts" equally. Functions like sleep and hibernation aren't registered as a complete shutdown. Therefore, if you frequently use sleep mode, you might see very long uptimes that don't reflect actual hours of continuous use.

On modern computers, especially laptops with Windows 11, the system often implements Modern Standby (OS Low Power Idle). This mode differs from classic sleep and may not generate such obvious startup/shutdown events. Check if your PC supports it by running:

powercfg /a

If “Standby (S0 Low Power Idle)” appears, your device is compatible. In these cases, in addition to IDs 12/13/42, it's advisable to monitor ID 1 to detect when the device “wakes up” from low power mode.

Windows updates are another key factor: sometimes the system restarts itself during the installation of large patches. In the Event Viewer, you'll see a shutdown (ID 13) followed by a startup (ID 12), and possibly events from "WindowsUpdateClient" (such as ID 19 or 20). To avoid surprises in the middle of the day, configure your Active Hours in Settings > Update & Security > Windows Update , or temporarily pause updates if necessary.

Other useful methods of the system itself

Besides Task Manager, CMD/PowerShell, and Event Viewer, there are other ways to approximate uptime. They aren't perfect, but they can be useful in a pinch for a quick estimate.

One of these is the network connection timeout, or alternatives for turning on your PC without the power button . Open Control Panel > Network and Internet > Network and Sharing Center and click on your connection (Ethernet or Wi-Fi). In the window, you'll see the connection timeout , which usually starts when you turn on your PC. Note: if you restart the adapter or the connection is interrupted, the timer resets, so use it as a guideline.

You can also check the Windows installation date. From CMD with systeminfo You will see the “Original Installation Date”, and in PowerShell you can get it with:

(Get-CimInstance -Class Win32_OperatingSystem).InstallDate

Keep in mind that after some major updates, Windows may change that date. Supplement this review by checking your Windows Update history in Settings, especially if you suspect a recent patch has changed your computer's behavior .

Third-party tools to simplify history

If you find the Event Viewer cumbersome, there are lightweight utilities that extract the same information and display it in a more user-friendly and straightforward way . They are especially useful for seeing at a glance what happened in each session.

TurnedOnTimesView

It's a free, portable application (no installation required) from NirSoft. It displays recent startups and shutdowns, the duration the system was powered on in each session, and other relevant data. The current session is usually highlighted in a different color because there hasn't been a shutdown event yet.

Additionally, it allows you to remotely access another computer on the network, provided you use administrator credentials. In Options > Advanced Options, you can select "Remote Computer" as the data source and enter the IP address or computer name. This is ideal if you manage multiple PCs and want to consolidate the history without having to navigate through the Event Viewer on each one.

CrystalDiskInfo

This tool doesn't read the Event Viewer, but it can help you estimate your PC's power-on hours if you've never replaced the main drive. It reads the "Power-On Hours" counter stored by HDDs/SSDs and displays the cumulative value. It's portable and very lightweight, and it also offers a SMART data set to monitor the drive's health.

Use it as a complement: if you've changed your hard drive, the counter no longer reflects the entire lifespan of your computer; and although it's very useful, it doesn't replace system events when you need to know the exact dates and times of each power-on/power-off.

As a quick trick, if you usually open your browser as soon as you start your computer, checking your browsing history can give you a clue as to the time it was turned on (because of the automatic visit to your homepage). It's not a professional or foolproof method, but it can get you out of a bind when you don't want to get bogged down in menus.

Extra tips: smart plugs for hours and consumption

If you want to monitor usage time and energy consumption, a smart plug can record when your PC is on and how much energy it uses. Its app will show you durations, times, and, depending on the model, cost estimates.

The advantage is that this method is Windows-independent: if you work with Linux or macOS and don't want to deal with logs or terminals, this solution provides a clear history without touching the system. Furthermore, it works for multiple devices connected simultaneously if you opt for a smart power strip.

How often should you shut down or restart?

For years, daily shutdowns were recommended, but nowadays periodic restarts are usually enough to "clean up" processes and free up memory. Windows implements Fast Boot , which speeds up startup by saving part of the kernel state, so shutting down and restarting doesn't always equate to a completely clean boot.

My practical advice: restart your computer occasionally (especially after updates or if you notice it's sluggish) and don't be afraid to leave it on for extended periods if needed. If you prefer to avoid accidental shutdowns, configure the power button . However, remember that running 24/7 consumes power and causes wear and tear , and it's advisable to completely shut down older computers when not in use for several hours, especially during the summer.

If your PC is struggling, one change you'll notice instantly is replacing the HDD with an SSD . Not only will it boot and shut down faster, but you'll also experience overall smoother performance. A 256GB SSD currently costs around €30, and the replacement is straightforward for both desktop and laptop computers.

Security: Use history to detect unwanted access

Checking computer startup and shutdown records helps detect if someone has used the PC without permission. If you see sessions outside of your authorized hours, it's time to strengthen login security and perhaps change passwords or lockout policies.

Extend that vigilance to your accounts: review login histories for email and key services, and enable two-step verification (2FA). Many providers will alert you if they detect access from unusual locations or IPs, allowing you to react quickly.

Limitations and professional scenarios

While the methods described above are very useful, they can lead to omissions or misinterpretations due to suspensions, hibernations, or automatic restarts during updates. Therefore, if you require rigorous long-term auditing, the ideal solution is to integrate the PC into a domain and centralize events with corporate policies and logs.

For most home users, combining Task Manager , PowerShell/CMD, and Event Viewer (or TurnedOnTimesView) will be more than enough to understand uptime, detect anomalous sessions, and make smart maintenance decisions.

With all of the above, you now have a range of options to find out how long your PC has been on, from the quickest query to historical analysis with events, understanding what affects the actual count (sleep, Modern Standby, updates), and with additional tricks like smart plugs or the installation date. Choose the method that best suits your needs and combine several to get a clear, reliable, and useful overview of your computer's usage.