Server 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"

If everyone could go into Feedback Hub in the settings of 2025, and explain this. Strength in numbers. I also have an open case with them that they have escalated to the product team. I have had this case open even since the pre-release. They took lots of captures, and logs, in both the failed states and after restarting the NIC. They thought my scheduled task to restart the NIC at boot up was clever. Yea, it works, but it's not clean and native and they understand this is not a true workaround or fix. There is light at the end of the tunnel as they were able to reproduce this issue in their lab.