Our "custom" driver is basically AMIDEWIN in a nutshell, we just reversed what AMI did, and then put it in our driver. That's it.Quote:
First of all, when I say driver, you perfectly know I mean custom driver like you're using at sync. Everyone say AMIDEWIN is trash when it's the source of the mobo. Mean when you spof, you use the natural way of your mobo to apply serials and it's more secure in a long run. We can get ratted, our customers will stay good.
Also, I first asked him his tpm.msc to check if he see something or not, don't try to create things I didn't said. For one of our customer who had a tpm chip, we custom flashed him and he was fine after but first he needs to see if it's on or off by default. Tpm.msc is accurate for 99% of people, at least at edgey, maybe you do other things at sync who make this different, idk and idc honestly.
Ofc disabling it in bios is the best thing to do, but from my experience, when someone can't, deleting it works most of time :)
There's really no other PUBLIC and EFFICIENT way to change serials permanently other than how AMIDEWIN does it.
If you get ratted then someone can easily just change the file on keyauth to install a ratted .exe, where as in our place its a bit harder changing a driver that won't load unless our server-side checks are met.
Anyways, this is not anything that you should be mad about. I am just giving you advice, take it however you would like.
tpm.msc doesn't resemble the true status of TPM.