Argh.

[technicalfool]

That seems to be twice that KerbalEdu's DRM component has messed up on me now, and the second time seems to be permanent.

When I first installed it, I'd added that instance of KSP.exe to the Windows Firewall blacklist. I figured if it accepts the keycode and functions like ye olde copy protection then, well, yay.

Thing is, adding KSP.exe to the firewall evidently doesn't stop the DRM component doing its thing. I know this because after Edu told me that there was a problem with the code and stopped working, and after deleting the sneakily-named file that contains the keycode the first time, I managed to trip Edu into asking me to enter it again. So far so good, it does the "connecting to server" dance, and okays the code with a "this computer is already registered" message.

Okay, so whatever DRM servers are being used evidently have a record that it's been installed. Fine.

Problem is, the same problem has occurred again. KerbalEdu has randomly decided "there is a problem, contact an administrator."

So I do the same trick. Delete the keycode file. Re-enter the keycode. And now I get this:

The white block is censoring out the keycode from under the nope-window. Apparently my one single installation is too many installations for the keycode. I've even un-firewalled KSP.exe, not that it makes a difference, and get the same problem. What gives?

[MarkZero]

It seems your tinkering with the firewall and the license file has somehow made the system think you're now trying to run it on another computer.

Please contact us ([email protected]) or Squad directly and give the email address you used when registering your license, so we can reset the install count of your license.