Unable to back up disk X: due to invalid partition table

Veeam Endpoint Backup;Veeam Agent for Microsoft Windows
1.x, 2.x
Last Modified:


The backup job fails with the following error:

Unable to back up disk X: due to invalid partition table


The error is caused by a volume type which has no partition table and due to this is not supported by Veeam Endpoint Backup.

In Windows Disk Management, the volume looks like a common MBR single partition. The Virtual Disk service which is used by Veeam Endpoint Backup to detect disks, generates the following messages that are then forwarded to Veeam log (log location: C:\ProgramData\Veeam\Backup\Endpoint\Backup_Job_*Machine name*\ Job.Backup_Job_Machine_name.Backup.log).

Info     Layout: MBR, disk signature: 1
Info     Partition 0, type 04 (FAT16), offset 0

The MBR partition table occupies sector 1 of the disk, so Partition 0 can start no earlier than sector 2. One sector equals 512 bytes for regular disks and 4096 bytes for 4K native hard disk drives. This means that the offset of Partition 0 must be greater than 512 or 4096.


Copy all data from the affected volume to another drive, because the workaround implies complete deletion of the volume in question. Open disk management > right click on the volume in question> delete volume. Then create a new volume and copy all the files back to it. After that you should be able to run the backup job successfully.

More Information

The described volume configuration is generally referred to as a "superfloppy". You can find more information about it on this Microsoft resource.

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
2.4 out of 5 based on 10 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: