SYSTEM DIAGNOSTICS

System Uptime Verification.

Enforce the "trust but verify" rule of IT support. Instantly calculate the precise timespan a machine has been running continuously to verify user reboot claims and identify potential stability issues.

SEE HOW IT WORKS

WMI / CIM Dispatcher ● CONNECTED

[UHDC] UPTIME CHECK: LAPTOP-US-4829

[i] Querying LAPTOP-US-4829...

> Last Boot: 02/11/2026 08:14

> Uptime: 14 Days, 6 Hours, 22 Minutes

[!] ATTENTION: Machine has not been rebooted in over a week.

Trust, But Verify

Users frequently confuse "closing the laptop lid" or "logging off" with a full system restart. Instead of arguing with the user over whether they actually rebooted, this tool provides absolute, mathematical proof of the system's state in seconds.

CIM Telemetry Extraction

Establishes a remote session over Port 5985 (HTTP) using the modern Get-CimInstance cmdlet to query the Win32_OperatingSystem class, bypassing legacy DCOM/RPC firewall blocks.

Timespan Calculation

Extracts the LastBootUpTime property (which CIM automatically converts into a standard PowerShell datetime object) and subtracts it from the current time to create a precise timespan.

Automated Alerting

Evaluates the calculated uptime days. If the value is greater than 7, it automatically injects a high-visibility warning string into the console output to alert the technician of potential system instability.

INTERACTIVE TRAINING ENGINE

⭐ 50 XP

How Junior Techs Learn This Tool:

While the UHDC uses PowerShell and WMI in the background for speed, a junior technician should know how to check this manually using classic command-line tools. The training engine teaches them how to utilize Sysinternals PsExec to remotely execute the systeminfo command and pipe the output to find to instantly grab the exact boot time without needing complex PowerShell scripts.

psexec \\$Target systeminfo | find "System Boot Time"

The In-Person Equivalent

Pressing Ctrl+Shift+Esc to open Task Manager, clicking the 'Performance' tab, selecting 'CPU', and looking at the 'Up time' counter at the bottom. Alternatively, opening a local command prompt and typing: systeminfo | find "System Boot Time"

Technical Q&A

Q: Why do users so frequently think they rebooted when they actually didn't?

Aside from simply confusing "logging off" with "restarting," the biggest culprit is the Windows "Fast Startup" feature. By default, when a user clicks "Shut down" in Windows 10/11, the PC doesn't actually turn off completely; it logs the user out and hibernates the Windows kernel to make the next boot faster. Because the kernel never stopped running, the WMI Uptime counter never resets. Only a true "Restart" command (or a forced shutdown) resets the counter.

Q: Why does the script use `Get-CimInstance` instead of the older `Get-WmiObject`?

Get-WmiObject relies on legacy DCOM/RPC protocols (Port 135 and dynamic high ports), which are frequently blocked by modern endpoint firewalls. Get-CimInstance is the modern standard; it routes the exact same WMI queries over the WinRM protocol (Port 5985/HTTP), which is much more firewall-friendly and reliable across enterprise networks.