System Diagnostic Monitor
=========================

A colorized, btop/htop-style console dashboard for Windows that tracks, live:

  * USB peripherals   - connect/disconnect, device type, and a per-device LINK
                        QUALITY grade (negotiated speed, port status, SuperSpeed
                        downgrade, re-enumeration/"flapping" rate)
  * Network links     - Ethernet + Wi-Fi (Wi-Fi signal / rate / channel)
  * Bluetooth devices - present/idle, battery (if reported), last-connected time
  * Storage heartbeat - a live pulse + health + temperature for every disk

It runs in the system tray and mirrors events to a rolling local log at:
  %LOCALAPPDATA%\SysDiag\sysdiag.log


HOW TO RUN
----------
1. Unzip this folder somewhere (e.g. your Desktop).
2. Double-click  Run.cmd
3. Click "Yes" at the Windows UAC (Administrator) prompt.

   Admin rights are required only to read disk health/temperature and full USB
   link/port details - those are not readable from a normal process.

Keys inside the dashboard:
  Q  hide to tray      C  clear on-screen events      R  force refresh
Right-click the tray icon to show/hide or to quit.

Optional (advanced), from a command prompt in this folder:
  Run.cmd -Install     start automatically at logon, minimized to the tray
  Run.cmd -Uninstall   remove that autostart task


"MY ANTIVIRUS / EMAIL WARNED ABOUT THIS"
----------------------------------------
This package contains a PowerShell SCRIPT (SysDiag.ps1), not a compiled program,
specifically so you can read exactly what it does before running it - open it in
Notepad, it's fully commented.

Security scanners sometimes warn about ANY script that (a) asks for Administrator
rights and (b) uses "-ExecutionPolicy Bypass" to launch, because that shape is
also used by bad software. Here both are legitimate and necessary:

  * Administrator  - to query disk SMART health/temperature and USB port status.
  * ExecutionPolicy Bypass - so the script can run on a machine whose default
                             policy would otherwise block all scripts.

What it does NOT do (you can verify by reading the script):
  * No internet access of any kind - no downloads, uploads, or network callbacks.
  * No changes to security settings or antivirus.
  * No hidden/encoded code. Everything is plain, readable PowerShell.
  * The only file it writes is the local log named above.

Requires Windows PowerShell 5.1 (built in to Windows 10/11).