Hi @ Larry Desmond ,
Typically, when you change this registry, the change is propagated to all servers that host copies of this database.
I recommend that you could recreate these two new database copies in Srv3 to see if the issue persists.
If it is still not synchronized, it is recommended that you run Test-ReplicationHealth and check the event log for any messages indicating a problem that might prevent the GUID update for the new database.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.