🟠 High   ⏱ 5–30 min  Last verified: 29 May 2026
Affected versions: Windows Server 2016

📖 ~1 min read

Table of contents
  1. Symptom & Impact
  2. Environment & Reproduction
  3. Root Cause Analysis
  4. Quick Triage
  5. Step-by-Step Diagnosis
  6. Solution — Primary Fix
  7. Solution — Alternative Approaches
  8. Verification & Acceptance Criteria
  9. Rollback Plan
  10. Prevention & Hardening
  11. Related Errors & Cross-Refs
  12. References & Further Reading

Symptom & Impact

Server crashes during startup with CRITICAL_SERVICE_FAILED and cannot reach login.

Environment & Reproduction

Seen after driver or security software updates that alter boot-start services.

wevtutil qe System /f:text /c:40

Root Cause Analysis

A required boot-start service is disabled, corrupted, or blocked by incompatible filter drivers.

Quick Triage

Boot into recovery and inspect service start types for recent changes.

reg load HKLMOFFSYS C:WindowsSystem32configSYSTEM

Step-by-Step Diagnosis

Identify failing service entry and recent update activity.

dism /image:C: /get-packages | findstr /i install
reg query HKLMOFFSYSControlSet001Services
Illustrative mockup for windows-server-2016 — error_dialog
BSOD and stop code context — Illustrative mockup — Progressive Robot

Solution — Primary Fix

Restore default start type for affected critical service and remove incompatible update if needed.

Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.

reg add HKLMOFFSYSControlSet001Services /v Start /t REG_DWORD /d 2 /f
dism /image:C: /remove-package /packagename:
Illustrative mockup for windows-server-2016 — event_or_log_viewer
Service and kernel boot events — Illustrative mockup — Progressive Robot

Solution — Alternative Approaches

Use Last Known Good backup or system restore point from recovery environment.

rstrui.exe

Verification & Acceptance Criteria

Boot completes without stop code and dependent workloads start normally.

Get-Service

Rollback Plan

Reapply previously removed package only after vendor-approved compatibility confirmation.

dism /online /add-package /packagepath:.cab

Prevention & Hardening

Test security and driver updates in staging before production deployment.

Get-HotFix | Sort InstalledOn -Descending

Related to SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and inaccessible boot device.

Related tutorial: View the step-by-step tutorial for Windows Server 2016.

View all Windows Server 2016 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft guidance on boot-critical services and crash recovery procedures.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.