
Volume Boot Record (VBR): What It Is, How It Works, and How to Fix It
The volume boot record is a small but critical piece of every formatted disk partition. If it is damaged, your computer may refuse to start, display a “boot device not found” error, or stop at a black screen — even though your files are still intact on the disk. Understanding what a volume boot record is, how it works, and how to repair it can save you from an unnecessary reinstall and from losing data.
In this guide, we explain the volume boot record in plain language: its structure, its role in the boot process, how it differs from the master boot record and the GUID partition table, the errors it causes when it fails, and the exact steps to fix it on Windows and Linux.
What Is a Volume Boot Record?
A volume boot record (VBR) — also called a partition boot sector or volume boot sector — is the first sector of a formatted partition on a storage device. It contains the code and data a computer needs to start loading the operating system from that partition.
Think of a hard drive or SSD as a building with several rooms. The partition table is the directory at the entrance that says which rooms exist and where they are. The volume boot record is the light switch just inside each room: it is the first thing the boot process touches when it enters a particular partition, and it tells the computer how to find and start the operating system stored there.
Every formatted partition has its own VBR, even partitions that do not contain an operating system. A data-only partition still has a VBR, although its boot code may simply report that the partition is not bootable.
What Is Inside a Volume Boot Record?
A VBR is normally one sector long — 512 bytes on most traditional drives, or 4,096 bytes on Advanced Format drives. Despite its tiny size, it packs in several essential parts.
| Component | What it does |
|---|---|
| Jump instruction | The first bytes tell the processor to jump to the boot code inside the VBR. |
| OEM / manufacturer name | An eight-byte field identifying the system that formatted the volume, such as “MSDOS5.0” or “NTFS”. |
| BIOS parameter block (BPB) | Describes the file system: bytes per sector, sectors per cluster, reserved sectors, number of file allocation tables, and total sectors. |
| Extended BPB (FAT) or NTFS data | Extra file-system details, such as the cluster where the root directory or the master file table starts. |
| Boot code | A small program that finds the operating system’s boot loader — for example, bootmgr on Windows or GRUB files on Linux — and hands control to it. |
| Signature (0x55AA) | The last two bytes, 55 AA, mark the sector as a valid boot sector. Without them, the BIOS or UEFI will not treat the partition as bootable. |
The BIOS parameter block is what makes the VBR file-system specific. The VBR of an NTFS partition looks different from that of a FAT32 or exFAT partition, because each file system stores its metadata in different places. That is why formatting a partition rewrites its VBR: the format process writes a fresh VBR matched to the new file system.
How the Volume Boot Record Works During Startup
The boot process is a chain, and the VBR is one of its middle links. Each link hands control to the next.
- Power-on self-test. When you switch the computer on, the firmware (BIOS or UEFI) checks the hardware and looks for a bootable device.
- Master boot record or GPT. On an MBR disk, the firmware reads the master boot record in the first sector of the whole disk and finds the active partition. On a GPT disk, it reads the EFI system partition instead, but the principle is the same: find the partition to boot from.
- Volume boot record. The firmware loads the VBR — the first sector of that partition — into memory and runs its boot code.
- Boot loader. The VBR’s code locates the operating system’s boot loader, such as Windows Boot Manager (bootmgr) or GRUB, and starts it.
- Operating system. The boot loader loads the kernel and drivers, and the operating system starts.
If any link in this chain is broken, booting stops. A damaged VBR typically stops the process at step three: the computer knows which partition to boot from, but the code that should start the boot loader is unreadable, corrupted, or pointing at the wrong place.
Volume Boot Record vs. Master Boot Record vs. GPT
These three terms are often confused. They describe different things at different levels of the disk.
| Feature | Volume boot record (VBR) | Master boot record (MBR) | GUID partition table (GPT) |
|---|---|---|---|
| Location | First sector of a partition | First sector of the whole disk | First sectors of the whole disk |
| Scope | One partition | Entire disk, up to 4 partitions | Entire disk, up to 128 partitions |
| Maximum disk size | Depends on file system | 2 TB | About 9.4 ZB |
| Contains | File-system data and boot code for one volume | Partition table and boot code | Partition entries with GUIDs |
| Used with | BIOS and UEFI systems | Legacy BIOS | Modern UEFI systems |
In short: the MBR or GPT tells the computer where the partitions are; the VBR tells the computer how to boot from one specific partition. On a modern UEFI/GPT system, the VBR is still present, but the UEFI firmware usually loads the boot loader directly from the EFI system partition, so a damaged VBR is less likely to stop the boot than on a legacy BIOS/MBR system.
Common Volume Boot Record Errors
When a VBR is damaged, the symptoms are usually clear — and alarming.
- “Operating system not found” or “No bootable device” — the firmware cannot find valid boot code in the partition.
- “BOOTMGR is missing” (Windows) — the VBR cannot locate the Windows boot manager, often after a failed update, a disk clone, or a partition resize.
- “Invalid partition table” — the partition table or the VBR’s signature is damaged.
- A black screen with a blinking cursor — the VBR loads, but its boot code jumps to the wrong location.
- Boot loops — the computer restarts repeatedly, never reaching the login screen.
Common causes include sudden power loss during a write, a failed Windows update, disk errors and bad sectors, a virus or bootkit that overwrites the boot sector, incorrect use of partitioning tools, and cloning a disk to a drive with a different sector size.
How to Fix a Damaged Volume Boot Record on Windows
Do not reinstall Windows first. In most cases the data is fine, and the VBR can be rebuilt in minutes from Windows Recovery Environment (WinRE).
- Boot into WinRE. Start the computer from Windows installation media or a recovery drive, choose your language, and click “Repair your computer” instead of “Install now”. If Windows fails to start three times, WinRE usually opens automatically.
- Open Command Prompt. In WinRE, go to Troubleshoot > Advanced options > Command Prompt.
- Rebuild the boot configuration. Run these commands, pressing Enter after each one:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
The/fixbootcommand writes a new boot sector — a new VBR — to the system partition, while/rebuildbcdrebuilds the boot configuration data that lists the installed operating systems. - Check the disk. Run
chkdsk C: /f /r(replacing C: with your system drive letter if needed) to find and repair file-system errors and bad sectors that may have caused the damage. - Restart. Close Command Prompt, remove the installation media, and restart. Windows should now boot normally.
If bootrec /fixboot reports “Access is denied,” try assigning a drive letter to the EFI system partition with DiskPart, or run the commands from an administrator Command Prompt in a working Windows installation. For UEFI/GPT systems, the equivalent repair is bcdboot C:\Windows, which recreates the boot files in the EFI system partition.
How to Fix a Volume Boot Record on Linux
On Linux, the VBR is less central, because GRUB is usually installed in the MBR or the EFI system partition rather than the VBR. If GRUB is damaged, you can reinstall it from a live USB.
- Boot from a live Linux USB and open a terminal.
- Identify your root partition with
lsblk -forfdisk -l. - Mount it, for example:
sudo mount /dev/sda2 /mnt, then mount the EFI partition if your system uses UEFI. - Reinstall GRUB with
sudo grub-install --boot-directory=/mnt/boot /dev/sda, replacing the device names with your own. - Regenerate the GRUB configuration with
sudo update-gruband reboot.
Always back up important files before running repair commands. The commands above rewrite boot structures, and a typing error — especially a wrong device name — can make the problem worse. A hypervisor or a virtual machine is a safe place to practise these steps before you try them on a real system.
Volume Boot Record Security: Bootkits and Secure Boot
Because the VBR runs before the operating system, it is an attractive target for attackers. A bootkit is malware that infects the boot sector so that it loads before Windows, giving it deep control and making it hard for antivirus software to detect or remove.
Modern defences help. Secure Boot, part of UEFI, checks that the boot loader is signed by a trusted authority before it runs, which blocks most unauthorised boot code. Trusted Platform Module (TPM) chips and measured boot go further by recording the boot chain so tampering can be detected. Keeping firmware up to date, using Secure Boot, and running reputable endpoint protection are the practical steps that matter. For general guidance on protecting the computers behind these systems, see our guide to how to protect your home computer.
Best Practices
- Back up regularly. A system image backup lets you restore a working boot sector and operating system in minutes.
- Do not interrupt updates or disk operations. Most VBR corruption happens during a power cut or a forced shutdown while the disk is being written to.
- Use a UPS on desktop computers to ride out short power outages.
- Keep firmware and drivers updated so the boot chain uses current, signed code.
- Scan for malware with a reputable tool if you see unexplained boot problems, and check the disk’s health with your manufacturer’s diagnostic tool.
- Label partitions clearly in Disk Management before resizing or cloning, so you do not write boot code to the wrong partition.
Conclusion
The volume boot record is only a few hundred bytes long, but without it your computer cannot find its own operating system. It sits at the start of each partition, describes the file system in its BIOS parameter block, and carries the small boot program that starts the boot loader. When it is damaged, the fix is usually a repair of the boot sector, not a reinstall — and with Secure Boot, regular backups, and careful disk management, most VBR problems are preventable.
Frequently Asked Questions
What is a volume boot record?
A volume boot record is the first sector of a formatted disk partition. It contains file-system information in its BIOS parameter block and a small boot program that finds and starts the operating system’s boot loader.
What is the difference between a VBR and an MBR?
The master boot record is the first sector of the whole disk and holds the partition table; the volume boot record is the first sector of one partition and holds that partition’s file-system data and boot code. A disk has one MBR but one VBR per partition.
Can a damaged volume boot record cause data loss?
Usually not by itself. A damaged VBR stops the computer from booting, but the files on the partition are normally still there. Repairing the boot sector, or reading the disk from another computer or a live USB, usually recovers them.
How do I fix a volume boot record in Windows 10 or 11?
Boot into Windows Recovery Environment, open Command Prompt, and run bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, and bootrec /rebuildbcd. Then run chkdsk to check the disk, and restart.
Does GPT still use a volume boot record?
Yes, each GPT partition still has a VBR, but UEFI systems usually boot from the EFI system partition rather than through the VBR, so VBR damage is less likely to prevent booting on a modern UEFI/GPT computer.


