That may have happened because a "update model from database" was performed, and the names of the fields in the table "[AspNetUserRoles]" have changed since the initial update.
The two navigation properties ("AspNetUsers1" and "AspNetUsers") and ("AspNetRoles1" and "AspNetRoles"), which are the newly formed properties, are replicated in the tables "AspNetRoles" and "AspNetUsers."
Therefore, deleting the previous association and navigation attributes is required to resolve the issue.
After that, you might rename the properties from AspNetUsers1 to AspNetUsers again to maintain the model tidy. The association is in agreement.