Super short answer: system UUIDs are a hardware thing, not an OS thing.
The only reason that you can change a Hyper-V VM's UUID is because you have access to its "hardware" via a file. For a physical system, the UUID is set by the motherboard manufacturer. If you have two physical machines with the same UUID and it's something other than all Fs, it's highly improbable that a restore caused that. The most logical reason is that your computer manufacturer used duplicates for some reason and you didn't find out until it mattered. It would not be possible for software to change the UUID unless the BIOS manufacturer added some technique to do that. Even if they did, it would be exceedingly unlikely for a restore operation to trigger it.
You can view the UUID of a system in PowerShell with Get-CimInstance -ClassName Win32_ComputerSystemProduct | select UUID
.
The operating system does not expose a way to change it:
If you're searching the Internet for something, look for your motherboard manufacturer and "SMBIOS UUID", possibly "SMBIOS GUID".