You actually removed the executable, or renamed it? It's not really what I meant, things won't work if it's renamed / removed. What I'd like you to do is run faf-uid.exe to test if the executable works. The only problem is that it should be run in console to be meaningful - are you able to open the Windows console in FAF installation folder, run 'faf-uid.exe banana' and paste back the output?
i could set up another account with another email address, just wondering that that would set off somekind of spam software, for too many accounts for this computer etc?
The issue we're dealing with here has nothing to do with FAF accounts. faf-uid.exe collects and makes a hash of various bits of system info, and apparently fails to do that. I just need the console output of it to diagnose it - it should normally be logged in faforever.log, I have no idea why it's not.