Disk signature collision errors in Windows occur when two connected disks share the same unique identifier, causing the system to mark one or both as offline to prevent data corruption. The fix is to change the duplicate disk signature using Disk Management or the DiskPart command-line tool, which takes only a few minutes and does not affect your files.
What Is a Disk Signature and Why Does It Matter
Every basic disk in Windows carries a 4-byte (32-bit) signature stored in the master boot record (MBR) or the protective MBR of a GUID Partition Table (GPT) disk. This signature is not the same as a volume serial number (which identifies a filesystem) or a disk number (which is just an enumeration). Windows uses the disk signature internally to identify a disk across reboots and to map drive letters and mount points. When two disks present the same signature, the operating system cannot reliably tell them apart, so it takes one offline and shows a warning in Disk Management: “The disk is offline because it has a signature collision with another disk that is online.”
This situation most often arises after cloning a hard drive or SSD to a new disk, restoring a system image to different hardware, or attaching a virtual disk (VHD/VHDX) that was cloned from another virtual machine. The clone copies the signature along with the data, so the original and the copy both claim the same identity.
Before You Start: Safety Checks
Changing a disk signature is safe for your data, but you must be careful to change the signature on the correct disk. If you change the signature on the disk that contains your Windows boot files, the system may fail to boot because the Boot Configuration Data (BCD) references the original signature. Therefore, before doing anything:
- Back up any important data on the disk whose signature you will change, especially if it is not a system disk.
- Identify which disk is offline by opening Disk Management (right-click Start > Disk Management) and looking for a disk marked “Offline” with the collision message.
- Note the disk number (e.g., Disk 1) and its size and model to avoid confusing it with the online disk.
- If the offline disk is the one you want to keep (for example, a newly cloned SSD), you can safely change its signature. If it is the old disk you are replacing, you can also change it, but you must then update the boot configuration if it contains Windows.
For a non-system data disk, the process is straightforward. For a system disk, you should change the signature before the first boot from the clone, or use a Windows recovery environment if you already booted and encountered the error.
Method 1: Change Disk Signature with Disk Management (GUI)
The graphical method is the simplest and works for basic disks (not dynamic disks). Dynamic disks do not have a traditional signature in the same way, but they can still collide; for those, use DiskPart or a third-party tool.
- Open Disk Management: press Win + X and select Disk Management, or type
diskmgmt.mscin the Run dialog. - Locate the disk that is offline. It will be labeled “Disk 1”, “Disk 2”, etc., with a red downward arrow.
- Right-click the disk’s left pane (where it says “Disk 1”) and choose Online. Windows will attempt to bring it online. If the collision is the only issue, it will succeed and assign a new signature automatically. If not, you will get an error.
- If the online attempt fails, right-click again and choose Initialize Disk? No, do not initialize—that would wipe the disk. Instead, use the DiskPart method below.
In many cases, simply bringing the disk online forces Windows to rewrite the signature automatically. If that does not work, proceed to the command-line method.
Method 2: Change Disk Signature with DiskPart (Command Line)
DiskPart is a built-in tool that gives you more control. You must run it as Administrator. The command to change a signature is uniqueid disk.
- Press Win + X and select Terminal (Admin) or Command Prompt (Admin).
- Type
diskpartand press Enter. - Type
list diskto see all disks. Note the disk number of the offline disk (e.g., Disk 1). - Type
select disk 1(replace 1 with your disk number). - Type
uniqueid diskto view the current signature. It will show something likeDisk ID: 1234ABCD. - To change it, type
uniqueid disk id=5678EF90(use any 8-digit hexadecimal value that is not the same as the other disk). Press Enter. - Type
exitto close DiskPart.
After changing the ID, the disk should come online automatically. If it does not, go back to Disk Management, right-click the disk, and choose Online. The new signature is now unique, so Windows will accept it. Your files remain intact because the signature is stored in the disk header, not in the filesystem.
What to Do If the Disk Still Shows Offline
If the disk remains offline after changing the signature, the collision may not be the only problem. Check the following:
- In Disk Management, right-click the disk and select Properties > Volumes to see if the disk is marked as “Foreign” or “Failed”. A foreign disk comes from another computer and needs to be imported (right-click and choose Import Foreign Disks).
- Open Device Manager and check if the disk controller driver is outdated or conflicting. Update the storage controller driver from the manufacturer’s website.
- If the disk is a dynamic disk, you cannot change its signature with DiskPart. Use a third-party partitioning tool that supports dynamic disks, or convert it to basic (which will delete data).
- Check the disk’s SATA/power cables. A loose connection can cause intermittent detection that mimics a collision.
- If the disk is a virtual disk (VHD/VHDX), the signature is stored in the VHD file. You can change it by mounting the VHD and using DiskPart, or by editing the VHD’s header with a hex editor—but the simplest is to recreate the VHD from the source.
If none of these work, the disk may have a failing controller or bad sectors. Run chkdsk on the disk after it comes online, but do not run it on an offline disk.
Preventing Future Signature Collisions
The most common cause is cloning a disk while the original is still connected. To avoid the problem:
- When cloning, disconnect the source disk after cloning, or use cloning software that automatically assigns a new signature to the target.
- If you must keep both disks connected, change the signature of the clone before connecting it to the system.
- For virtual machines, always use the “Clone” option in your hypervisor, which typically regenerates the disk signature.
- When restoring a system image to a new disk, do not connect the old disk until the new one boots successfully.
If you already have a collision, the fix above is permanent. Windows will remember the new signature, and you will not need to repeat it unless you clone again.
Frequently Asked Questions
Will changing the disk signature delete my files?
No. The disk signature is stored in the disk’s header, not in the filesystem. Changing it does not touch any partition or file data. Your files, folders, and drive letters remain exactly as they were. However, if the disk is a system disk, the boot configuration may reference the old signature, so you might need to repair the boot configuration after the change.
Can I use the same disk signature on two disks if they are never connected at the same time?
Technically yes, but it is not recommended. Windows may still get confused if you swap disks, and some applications (like backup software) rely on the signature to identify disks. It is always safer to give each physical disk a unique signature.
What is the difference between a disk signature and a volume serial number?
A disk signature is a 4-byte identifier stored in the disk’s MBR or GPT header, used by the operating system to track the entire disk. A volume serial number is a 4-byte number stored in the boot sector of a partition (filesystem), generated when you format the volume. You can change the volume serial number with vol command or third-party tools, but that does not affect the disk signature.
Does this fix work for GPT disks?
Yes. GPT disks also have a disk signature (called a GUID, which is 16 bytes instead of 4). DiskPart’s uniqueid disk command works for both MBR and GPT disks. For GPT, you can enter a 16-byte GUID in the format id=12345678-1234-1234-1234-123456789ABC.
What if I accidentally change the signature on the wrong disk?
If you change the signature on a data disk, the only effect is that Windows will treat it as a new disk, and drive letters may be reassigned. Your data is still there. If you change the signature on the system disk, the system may fail to boot because the BCD references the old signature. To fix that, boot from Windows installation media, open Command Prompt, and run bootrec /rebuildbcd.
Can I prevent the collision without changing the signature?
No. The only way to resolve a signature collision is to make one of the signatures unique. You cannot “merge” or “ignore” the collision. Windows will keep the disk offline until you change the signature.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to Add Another Account on Telegram
- Ubuntu Printer Detected But Won’t Print: Fix
- Autoplay Not Working on Windows 11? Fix It
- Edit Messages on iPhone & View Edit History
- How to Clean Rust Off Chrome Dinette Legs
- Prepare Your PC for a Major Windows Upgrade