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

The server repeatedly enters Startup Repair and never reaches normal boot, extending downtime.

Environment & Reproduction

Often appears after cumulative update interruptions or driver update rollouts.

bcdedit /enum
notepad C:WindowsSystem32LogFilesSrtSrtTrail.txt

Root Cause Analysis

Pending update actions or damaged boot-critical files force automatic repair cycles.

Quick Triage

Review SrtTrail output and pending package state before applying broad changes.

dism /image:C: /get-packages | findstr /i pending

Step-by-Step Diagnosis

Check repair logs and offline component store consistency.

type C:WindowsSystem32LogFilesSrtSrtTrail.txt
dism /image:C: /cleanup-image /scanhealth
Illustrative mockup for windows-server-2016 β€” terminal_or_powershell
Startup repair loop diagnostics β€” Illustrative mockup β€” Progressive Robot

Solution β€” Primary Fix

Revert pending update actions and run offline system file repair.

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

dism /image:C: /cleanup-image /revertpendingactions
sfc /scannow /offbootdir=C: /offwindir=C:Windows
Illustrative mockup for windows-server-2016 β€” event_or_log_viewer
Boot repair logs and events β€” Illustrative mockup β€” Progressive Robot

Solution β€” Alternative Approaches

Uninstall last quality update from recovery if loop persists.

dism /image:C: /remove-package /packagename:

Verification & Acceptance Criteria

Server exits recovery loop and boots successfully twice in a row.

shutdown /r /t 0

Rollback Plan

Restore system state backup captured before remediation steps.

wbadmin start systemstaterecovery -version:

Prevention & Hardening

Enforce staged patch testing and verify reboot completion before production rollout.

Get-HotFix | Sort InstalledOn -Descending | Select -First 10

Related to inaccessible boot volume and failed servicing stack updates.

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 Learn articles on startup repair diagnostics and offline DISM repair.

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.