Like many things in the Microsoft Windows universe, there are several ways to check Up Time of your systems.
Fortunately, they are all easy and quick!
How to Check Windows Uptime via Command Line
There are several really simple ways to check uptime in Windows Server 2016 and Windows 10 using Command Prompt or PowerShell.
Rather than bore you with the details lets jump into each of them starting with the easiest.
Check Windows Uptime with Net Statistics
This one is super simple. You just need to open command prompt or PowerShell and type either:
net statistics server
net statistics workstation
If you’re on a server OS such as Server 2012 or Server 2016 then use the command ending in Server. If you’re using a workstation OS such as Windows 8.1 or Windows 10 use the command ending in workstation.
The output will look like this:
C:\WINDOWS\system32>net statistics workstation Workstation Statistics for \\DOMCON1 Statistics since 9/17/2018 4:40:11 PM Bytes received 6094 Server Message Blocks (SMBs) received 12 Bytes transmitted 5164 Server Message Blocks (SMBs) transmitted 0 Read operations 0 Write operations 0 Raw reads denied 0 Raw writes denied 0 Network errors 0 Connections made 0 Reconnections made 0 Server disconnects 0 Sessions started 0 Hung sessions 0 Failed sessions 0 Failed operations 0 Use count 8 Failed use count 0
The line starting with “Statistics since …” displays the last time your computer was booted up.
How to Check Uptime in Windows with SystemInfo
Another way to see the the last boot time of your machine using a simple command prompt command is to use:
You can cut down the output to just the system boot time line by using a pipe and the find operator like so:
systeminfo | find “System Boot Time”
C:\WINDOWS\system32>systeminfo | find "System Boot Time" System Boot Time: 9/17/2018, 4:40:10 PM
If you want to check the boot time on a remote server you can either use the this command:
systeminfo /s remoteservername | find “System Boot Time”
or use a utility like PSExec from Microsoft PSTools to enter a remote command line.
Use the Windows Uptime Command (Uptime.exe)
The original Windows Server Uptime command was part of a program released by Microsoft called Uptime.exe. You used to be able to download it via KB232243. Now you have resort to downloading it from the Internet Archive URL or our website here.
Simply download the .exe and place inside your C:\Windows\System32 folder.
You can then run the following command to find the system uptime:
Or you can use this command to see the uptime on a remote server or workstation:
Which results in:
C:\WINDOWS\system32>uptime \\DOMCON1 has been up for: 1 day(s), 12 hour(s), 6 minutes(s), 58 seconds(s)
Now I did say original Uptime command earlier. That is because a new uptime.exe was developed under the open source project uptimeEXE which you can download here at Codeplex.
The command syntax is nearly identical to the original Uptime.exe as you can see here:
C:\WINDOWS\system32>uptime 08:20:14 uptime 08:48:27
The only drawback to this updated version is that it doesn’t contain the extra options such as checking windows uptime on a remote computer.
Use Task Manager to Check Server Uptime
If you’re more of a GUI type person then you’ll be happy to know that you can use Task Manager to view system uptime.
All you have to do is open Task Manager (can search start menu for Task Manager, right click the task bar and click on Task Manager, or search for taskmgr.exe) and open the Performance tab.
Inside the CPU window, in the bottom left hand corner, you’ll find the Up time.
Recommended for You: Solarwinds Server & Application Monitor (SAM)Know which applications are having issues in your environment before users complain? Know which systems are causing those problems? How about which servers are about to have problems like running out of space or memory?
Automate collection of data and alerting on your applications and servers with Solarwinds Server & Application Monitor so you have these answers.
Get insight into Active Directory, DNS, DHCP, and your Virtual environment without needing to mess with complex templates or knowing a single line of code.