When a critical boot driver (like disk controllers or video drivers) is corrupt or incompatible, Windows fails to load [4]. The system detects this failure and automatically launches [1, 3]. However, if the repair tool cannot identify or replace the specific driver file, it fails and reboots, starting the cycle again [1, 4]. How to Fix It

In the Command Prompt, type bcdedit /set {default} recoveryenabled No to stop the auto-failover and force Windows to attempt a normal boot, which may reveal the specific failing file [4, 5].

The often triggers when a "Bad Driver" prevents the OS from booting, causing the system to enter a continuous loop of unsuccessful repairs [1, 2].