The link below says Reflect will handle an image of up to 16 TB and I doubt if they would use that as a limit if it couldn't normally restore that size. This points to some issue with how BIBM has done something that is different from regular MS Windows possibly having to do with the EMBR that appears to be a Terabyte corporation construct (it isn't the same as the EBR) which you probably already knew. 

Let the finger-pointing begin!

You could try to raise this in a ticket to Reflect support which is pretty accommodating for problems even if you are out of support time; be sure to reference this thread.  You also might try Terabyte.

https://tecnobits.com/en/What-image-size-does-Macrium-Reflect-Free-support%3F/#:~:text=Image%20sizes%20%E2%80%8Csupported%20by%E2%80%8D%20Macrium%20Reflect%20%E2%81%A3Free%201,offers%20several%20compression%20%E2%81%A2options%20for%20disk%20images.%20

@pimjoosten If the Ex on the end of RegSetValue is what puzzles you, that's a common MS way of differentiating two versions of the RegSetValue (used to Set a new value in the Registry), with the Ex meaning Extended version (with more or different arguments, perhaps). 

As for the other thing you asked: why does it show up sometimes?  I note that the operation performed in the second picture of your examples shows a modified Disk ID. 
And that's explained in this  UserGuide/KnowledgeBase article:

... as part of a clone or restore process, Macrium Reflect will recalculate the signature according to the table below. If the signature is recalculated, the boot configuration data (BCD) store is located and updated and the drive mappings in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\ are also updated if necessary.

The whole article has more about why the disk id must be different.  


L.W. (Dan) Danz, Overland Park KS

@DanDanz, good info and I think explains his questions about why it changes the registry.

@Seekforever @DanDanz Thank you both for your replies. I was unexpectedly not able to respond to you for about a month, please accept my apologies for that. Your replies are much valued.

+x

 

Seekforever - 21 September 2023 2:34 PM

Let the finger-pointing begin!

You could try to raise this in a ticket to Reflect support which is pretty accommodating for problems even if you are out of support time; be sure to reference this thread.  You also might try Terabyte.

Yes, that is what I fear will happen in this case and why I am reluctant to contact the support of both companies. I have my doubts whether Terabyte Unlimited would be willing to help in this case, because they already have a strict policy of not allowing to mention a competing product on their forum. They will very likely refer to their own Image for Windows product. As far as Macrium is concerned, they have no knowledge about what BIBM actually does to the disk, and I do not feel that I am in a position to ask them to look at that. But maybe I will try to get some answers to my questions.

+x

 

Dan Danz - 21 September 2023 5:46 PM

@pimjoosten If the Ex on the end of RegSetValue is what puzzles you, that's a common MS way of differentiating two versions of the RegSetValue (used to Set a new value in the Registry), with the Ex meaning Extended version (with more or different arguments, perhaps). 

As for the other thing you asked: why does it show up sometimes?  I note that the operation performed in the second picture of your examples shows a modified Disk ID. 
And that's explained in this  UserGuide/KnowledgeBase article:

... as part of a clone or restore process, Macrium Reflect will recalculate the signature according to the table below. If the signature is recalculated, the boot configuration data (BCD) store is located and updated and the drive mappings in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\ are also updated if necessary.

The whole article has more about why the disk id must be different.  

Thanks Dan. I understand what that article says and it explains possible registry updates when there is a signature collision. Unfortunately it does not explain why even when restoring to the same drive as the image was made from also needs registry updates. I am still hoping somebody from Macrium can chime in why the registry is always updated during a restore and perhaps also the other questions in my opening post.