How to Use Bootsect /nt60 to Update the VBC to BOOTMGR

This article explains how to update the VBC to BOOTMGR using the bootsect command in Windows Vista and newer.

How to Update the VBC to BOOTMGR

Follow these steps to boot to Command Prompt and run the appropriate command:

1. Access Advanced Startup Options (Windows 11, 10 & 8) or boot to the System Recovery Options menu (Windows 7 & Vista).

   Feel free to borrow a friend's Windows disc or flash drive to access one of these diagnostic modes if you don't have Windows media on hand.

   Using original installation media is just one way of accessing these repair menus. See How to Create a Windows 8 Recovery Drive or How to Create a Windows 7 System Repair Disc (depending on your version of Windows) for help creating repair discs or flash drives from other, working copies of Windows. These options aren't available for Windows Vista.

2. Select Command Prompt.

   Command Prompt functions similarly between operating systems, so these instructions will apply equally to any version of Windows setup disc you're using—Windows 11, Windows 10, etc.

3. Type this command, and then press Enter:

   bootsect /nt60 sys
   

   This will update the volume boot code on the partition used to boot Windows to BOOTMGR, the one that's compatible with Windows Vista and later Windows operating systems.

   The nt60 switch applies the [newer] boot code for BOOTMGR while the nt52 switch applies the [older] boot code for NTLDR.

   Some documentation online regarding the bootsect command refers to it updating the master boot code, which is incorrect. The bootsect command makes changes to the volume boot code, not the master boot code.

4. You should now see a result that looks something like the text below. Close the Command Prompt window and then remove the Windows disc from your optical drive or the Windows flash drive from its USB port.
   

   C: (\\?\Volume{37a450c8-2331-11e0-9019-806e6f6e6963})
   Successfully updated NTFS filesystem bootcode.
   Bootcode was successfully updated on all targeted volumes.
   

   If you receive some kind of error, or this doesn't work after you try to start Windows normally again, try running bootsect /nt60 all instead. The only caveat here is that if you dual boot your computer, you may inadvertently cause a similar, but opposite, problem with any older operating systems you boot to.

5. Select Restart or Continue, whichever option you see.

Windows should start normally now. If you're still experiencing your problem, like a hal.dll error for example, see the note in Step 4 for another idea or continue with whatever troubleshooting you were following.