How to Check Server Uptime via CMD

Knowing a server's uptime is useful for more than curiosity. It helps answer practical questions: Did the machine reboot after Windows Update? Has that "slow since yesterday" issue actually been happening for 18 hours? Did the host crash overnight and recover on its own? In Windows, you can answer all of those from Command Prompt without opening any third-party monitoring tool.

Fastest Command to Check Uptime

For most admins, the easiest answer is:

systeminfo | find "System Boot Time"

This returns the last boot timestamp. If the current time is 4:00 PM and the boot time says 9:15 AM, your uptime is just under seven hours.

Why this command is useful:

• It is built into Windows.
• It works on desktops and servers.
• It gives a human-readable time instead of a raw timestamp.

The downside is that systeminfo can feel slow on heavily loaded systems because it gathers a lot of other OS details before printing the line you want.

Best Alternative When systeminfo Feels Slow

If systeminfo takes too long, use the classic service-statistics method.

For workstations:

net statistics workstation

For Windows Server:

net statistics server

Look for the line that begins with Statistics since. That timestamp usually aligns with system uptime closely enough for day-to-day troubleshooting.

This method is handy when:

• you are on an older Windows system
• you only need a quick sanity check
• you are already working in a minimal remote shell

Most Script-Friendly Option

If you need the raw boot value for parsing or reporting, use WMIC:

wmic os get lastbootuptime

The result looks like this:

20260309142055.500000+120

That format includes the full date, time, fractions of a second, and timezone offset. It is not the prettiest output, but it is useful in scripts where you want consistent machine-readable data.

If you are working on newer Windows builds, note that WMIC is deprecated. It often still works, but PowerShell is the long-term replacement. If you want the same information from a modern shell, use:

powershell -Command "(Get-CimInstance Win32_OperatingSystem).LastBootUpTime"

How to Check Uptime on a Remote Windows Computer

If you are troubleshooting another machine on the network, uptime is often the first thing to verify after "Can I reach it?" and "Did anyone reboot it?"

For a remote Windows host with appropriate permissions, PowerShell is usually the cleanest way:

powershell -Command "Get-CimInstance Win32_OperatingSystem -ComputerName SERVER01 | Select-Object CSName,LastBootUpTime"

That gives you the hostname and last boot time in one command. It is especially useful for patch validation, reboot scheduling, and after-hours incident review.

What Uptime Does and Does Not Tell You

Admins sometimes treat uptime as a health score. That is a mistake.

Long uptime can mean:

• the server is stable
• the server has not received reboot-required patches
• no one has maintained it in months

Short uptime can mean:

• a healthy planned reboot after maintenance
• an unexpected crash
• a watchdog or orchestrator restarted the VM

So the correct question is not "Is the uptime high?" but "Does this uptime match what should have happened?"

Common Troubleshooting Scenarios

Server is slow after patching

Check whether the server actually restarted after the update window. If uptime still shows several weeks, the patch cycle may not have completed.

Service keeps failing every morning

If uptime resets daily, the entire machine may be rebooting because of a scheduled task, power issue, hypervisor event, or crash.

Users say they were disconnected from RDP

Compare the reported disconnect time with boot time. If they match, the box rebooted. If they do not, focus on RDP service logs, VPN drops, or network instability instead.

GUI Option

If you have the desktop open, Task Manager shows uptime visually:

1. Open Task Manager.
2. Go to Performance.
3. Select CPU.
4. Read the Up time field.

That is useful for a quick spot check, but for documentation and incident notes, the command-line methods are better.

Which Command Should You Use?

Bottom Line

If you just need the answer fast, use:

systeminfo | find "System Boot Time"

If you are scripting or auditing multiple hosts, switch to PowerShell or CIM. The important part is not the exact tool. It is verifying whether the machine's reboot history matches the problem you are investigating.