How to Fix the Disk Signature Collision Error on Windows

A disk signature is also known as an HDD signature, Disk Identifier, Unique Identifier (UID) and fault tolerance signature. It is a unique identifier stored as part of the MBR (Master Boot Record). They are used by the operating system to identify and distinguish between storage devices. It is commonly made up of eight alphanumeric characters.

What Is a Disk Collision?

A disk collision occurs when your operating system (Windows) detects that there are two disks with identical signatures. Windows may not always prompt the user when a collision occurs. In previous versions of Windows (like Windows Vista and XP), when a collision occurred the signature of the drive complaining of a collision would be changed automatically. Windows cannot permit two disks with the same signature to coexist and function at the same time. For Windows 7, 8, 8.1 and 10, it disables the second drive and does not allow it to mount until the disk collision has been rectified.

hard-disk-windows-disk-manager-2

If you have a disk collision issue, you might see one of these two messages: “The boot selection failed because a required device is inaccessible” or “This disk is offline because it has a signature collision.

These messages are usually seen from the Disk Management tool when a collision occurs. If your default boot drive goes offline as a result of a collision, then the computer becomes unable to boot properly. A 0xc000000e error is displayed at startup.

What Causes Disk Collision?

Although Disk collisions are a rarity, they can happen to you if you run a disk that has been cloned alongside its clone. Something similar can happen if you make a virtual hard drive from a physical one or use back up software that uses virtualisation.

How to Fix the Disk Signature Collision Error in Windows

1. Open Command Prompt or Windows PowerShell as an Administrator.

2. Type Diskpart in the command prompt window, and hit the Enter key.

windows-diskpart-command-prompt-disk-signature-2

3. Type list diskand press Enter. This will list all the disks that are currently on the system.

This is a list of actual physical disks and not partitions. It’s the same list you’d see under the Disk Management window.

command-prompt-windows-disk-signature-2

4. Type select disk x (where “x” is the number of the problem disk) and hit Enter. If you’ve done this successfully, Diskpart will display this message: “Disk x is now the selected disk.”

For clarification, if you typed in select disk 0, it will display “Disk 0 is now the selected disk.”

windows-disk-part-command-prompt-disk-signature-2

5. Type Uniqueid disk and hit Enter. This will display the disk’s signature.

command-prompt-windows-disk-signature-did-2

6. Type unique disk ID={NEW SIGNATURE},  where “{NEW SIGNATURE}” is the new ID you want for the disk (without the curly brackets).

windows-command-prompt-diskpart-uids-2

The Disk Signature must be in the form of a hexadecimal figure.

If it isn’t in the right format, DISKPART will throw an error that reads: “The specified identifier is not in the correct format. Type the identifier in the correct format: in hexadecimal form for an MBR disk or as a GUID for a GPT disk.”

Once you’ve followed these steps correctly, Windows will put the disk online and assign a drive letter to it. A reboot may be required.

Final Word

Although Disk collisions are a rarity, it can happen if you are not aware and leave you with a computer that cannot be booted. If you are having a disk collision issue in Windows, the method above seems to be the most surefire and low-risk way to sort this issue out.

The Complete Windows 10 Customization Guide

The Complete Windows 10 Customization Guide

In this ebook we’ll be exploring the multitude of options to fully customize Windows 10. By the end of this ebook you’ll know how to make Windows 10 your own and become an expert Windows 10 user.

Get it now! More ebooks »

5 comments

  1. Thank you very much! This is exactly the problem I was facing after cloning two HDDs that I wanted to mount simultaneously.

  2. Wonderful! This is the clearest and most straight-forward solution to a surprise problem. Followed the instructions (except used the Offline disk # of course), rebooted, and Voila! Thanks so much.

  3. This guide didnt work for me at the end because every hexdex number i used was invalid. I had to have several – with 5x hexdec numbers in it (just edited original one slighly) till it finnaly let me change it. Even one in example 1235678 did not work.

    1. Hi, encountering the exact same issue. Could you give me a concrete example of a number that worked for you?

      1. Type Uniqueid disk on its own to show the current ID, which is probably a GUID.
        Then change a couple of the digits to make it different and it should be accepted, however in my case I am still getting the collision error.

        There is a lot of copy and paste articles on the net with every single one only showing a MBR Id as an example (the clear giveaway they all copy and paste from an original article with the mistake).

        This is a GUID for a GPT disk.

        180208BF-7C48-4091-AFBC-2F4D87DFDE26

Comments are closed.