Mit Build 2050 soll sich das aber geändert haben - ich zitiere mal von hier:
I slipstreamed into 2050 a licensing fix. It now properly uses only the motherboard serial number. You will need to make a new license when you grab this, theoretically the last you'll ever need for your specific motherboard.
There are some other changes to licensing. The license generator now detects duplicate machine IDs and won't increment the count if you re-enter a machine ID you already licensed. You can use that to query the license keys you already made. If you put a new machine ID, however, you will get incremented. Next, the maximum number of licenses was increased to 16. Finally, VBVChecker licensing was made the same as the other DG tools. Now all the tools should generate the same machine ID (except DGAVCDecDI, which I plan to kill very soon).
These changes make the licensing much more user-friendly. With these changes, going forward, I am less receptive to license count reset requests, as 16 unique machine IDs per donation is fair. Eliminating the reset also simplifies maintenance.
Sprich: ab dieser Version wird nur noch die Motherboard-Nummer zur Generierung der Machine-ID herangezogen. Solange man also nicht das Motherboard wechselt, sollte somit die bestehende Lizenz Gültigkeit behalten. Das war meiner Meinung nach schon lange überfällig, da ich (ebenfalls dank mehreren Software-Netzwerkadaptern) bislang schon 6 Mal eine neue Lizenz generieren durfte 
.
