Examine the laptop’s software activity
Stage 1 reads Windows observations while you run the collector. Stage 2 requires a separately identified physical sensor and connector. Neither stage currently grants automatic repair or equipment control.
1 · Run the software scan
Keep your signal reference ready. Copy the collector, paste it into Windows PowerShell, then press Enter. Read the collection notice and type yes to proceed.
- Paste your exact submitted signal reference.
- Enter a short location label, such as home desk. This is your report; Gabriel does not verify your room or GPS location.
- Choose before or after and use MY-LAPTOP-01 consistently.
- Keep applications unchanged until 12 readings finish. Ctrl+C stops collection.
The file contains CPU and available memory, disk queue/read/write observations when available, up to ten process names, PIDs and working-set sizes per sample, and estimated battery charge/status when Windows exposes them. Review it before selecting it in Gabriel. It contains no process commands, document contents, account credentials or serial number. The collector makes no network requests or configuration changes.
Download scanner source2 · Review the scan with the same signal
When PowerShell prints Saved:, select that JSON file in Review laptop recordings with your signal. The software scanner uses gabriel-software-before-…json and gabriel-software-after-…json. A different embedded signal reference is rejected.
Gabriel can describe recorded workload, disk activity and process memory, then guide a single corrective trial. A busy process is an investigation lead, not a proven fault. Unknown readings remain unknown.
3 · Examine supported hardware reports
The collector attempts to read Windows battery charge and status. If available, Gabriel shows those reported observations separately. It does not infer battery health or measured voltage from charge percentage.
No physical sensor is connected by this software scan. To proceed, identify your actual sensor’s manufacturer, model, supported connection interface, measurement/unit, calibration reference and mounting location. For company equipment, use The Realm Protector’s approved source and perimeter setup.
Temperature, voltage, current and vibration require measurements exposed by supported hardware. Registering a source alone does not establish data receipt. Gabriel must receive case-matched readings and validate the connector before it reports operational sensor presence.