How to distinguish startup, update, performance, service, and endpoint-connectivity failures before choosing a repair path.
Boot, update, performance, and connectivity failures occur at different layers. Use the earliest observable failure boundary to choose the first diagnostic step.
| Symptom | First diagnostic lane |
|---|---|
| Repeated stop errors or shutdowns | Recent driver, hardware-adjacent change, update, and stability evidence |
| Slow system or memory warnings | Startup load, process pressure, available memory, and storage capacity |
| Service unavailable | Dependency, startup type, permission, and recent configuration change |
| No bootable operating system | Firmware boot order, storage detection, partition, and recovery environment |
| Mobile update fails | Storage, connectivity, support status, policy, and account state |
| Wi-Fi, Bluetooth, or NFC fails | Radio state, pairing, credentials, signal, and platform settings |
Check whether an update failure is local to one application, one device, or a service dependency before resetting or rebuilding the endpoint.