(Change C: to your Windows drive letter if different.)
To repair the boot process for , you must boot from installation media to access the Command Prompt within the Recovery Environment. 1. Accessing Recovery Environment
Select your language, time, and keyboard preferences, then click . windows server 2012 r2 boot repair
: bootrec /fixboot Writes a new boot sector to the system partition, which is useful if the boot sector was replaced by a non-standard one or is corrupted. 4. Rebuilding the Boot Configuration Data (BCD)
bootrec /scanos bootrec /rebuildbcd
sfc /scannow and dism /restorehealth targeting the offline directory
Sometimes boot failure stems from core OS file corruption, not just bootloader issues. You can run and DISM from the recovery environment. (Change C: to your Windows drive letter if different
— Scans for Windows installations and lets you add them to the BCD. Microsoft Community Hub Step 3: Advanced Manual BCD Rebuild rebuildbcd fails to find an installation, manually reset the BCD: Microsoft Community Hub Export/Backup current BCD: bcdedit /export C:\BCD_Backup Remove attributes: attrib c:\boot\bcd -h -r -s Rename old BCD: ren c:\boot\bcd bcd.old bootrec /rebuildbcd Step 4: System File and Image Repair
Locate the offending third-party driver name (which usually follows an oemXX.inf taxonomy format). Remove it cleanly from the boot stack: dism /image:C:\ /remove-driver /driver:oemXX.inf Use code with caution. 2. Purge Pending Update Actions : bootrec /fixboot Writes a new boot sector
Once the command prompt is open, run these commands in order to fix the Master Boot Record and boot configuration: bootrec /fixmbr – Fixes the Master Boot Record.