Windows 10: How does disk signature collision affect the BCD Boot Configuration Data on GPT GUID...

I have 2 OS disks GPT partitioned and have the same disk signature. When both of these are made online in parallel, the disk signature is changed automatically for 2nd disk, and its BCD gets corrupted.Now when this 2nd disk is used to boot a VM, the error is shown as highlighted below and VM does not bootThe only way till now that worked and found is to rebuild BCD after disk gets corrupted and then rebooted again

:)

 

Cloning and disk signature collisions

I do both a clone of my C drive and an image backup.

On a couple of occasions I have had to boot the newly cloned drive and forgot to remove the original source drive.

This gives me Disk Signature collision which I think I understand.

What I'd like to do is change the disk signature of the original source drive which is a GPT SSD.

All the articles I've found on the net seem to suggest using diakpart which I have no problems using. Where I do have an issue is with determining how to provide a new disk signature.

What is the format of the GUID GPT disk signature?

How do I create a new disk signature? Is it just a string of random numbers?

If diskpart doesn't like the format or the actual id how do I create one that diskpart will accept.

Thanks

 

Cloning and disk signature collisions

Yes, it is random:

Code:

8 hex characters-4 hex-4 hex-12 hex

Hex characters are 0-9 and letters a-f.

I'd recommend you do the diskpart command uniqueid disk. Copy the GUID. Then run uniqueid disk id={then paste the previous GUID and just change one of the four character sets in the middle}

 

Disk X has the same disk identifiers as one of my other disks

Ooooh maaan, I followed your post and accidentally changed my boot drive's uniqueid. I somehow had a gut feeling that it was gonna mess up my Windows boot if I restarted my PC, so I had to look for another thread on how to remedy this. This was the thread that helped me: [guide] modify disk UniqueId + GPT BCD to point at it before rebooting This is what I get for fiddling with stuff I don't know much about. I ain't messing with Windows' stuff anymore. lmao - - - Updated - - -

I almost messed up my Windows install since I accidentally changed my UniqueID for my boot drive. lmao Good thing I didn't restart my PC immediately. Thankfully, this thread helped me out: [guide] modify disk UniqueId + GPT BCD to point at it before rebooting