>>1021314
running in a vm completely mitigates the issue.
if you don't want to VM, the guid is just stored as a registry entry in windows at the following path:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography
just make a text file to back up the string. if you want to do it via powershell / terminal:
1. this will show the current guid so you can save it
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Cryptography" | Select-Object MachineGuid
2. this will set it:
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Cryptography" -Name "MachineGuid" -Value "PASTE_GUID_HERE"
the only time guid won't get restored if the program is terminated abnormally - power outage / hard restart, so doing the backup is just precautionary, but might as well.
