This point is related to the following Ticket FS#5399 : Kernel startet nicht korrekt durch und is somit nicht für Connect freigeschaltet. That could also be the reason, why you can't activate your Art-Net.
But I also can confirm the behaviour you recognise first, that Art-Net will not work. Every time I try to add a Art-Net interface, the Kernel shows the same message and the stage view does not response anymore in that way, that for example the changes color on a device group will not be shown at the devices itself. It does not happen by using a USB interface like a Nodle R4S.
Edit: I have created a ticket in our bugtracker FS#5400 : Aktivieren der Art-Net-Ausgabe für zu Deadlock
LightningBrothers
The fun fact is that I switched from my USB Enttec to Artnet node due to previous releases issue and now ... 
Yes... that's pretty shit indeed. But luckily, the Art-Net problem should be fixed much easier then that one with the Enttec interface because it's easier to test. For fixing the problem with the Enttec interface, we had to put one our one at first to a parcel and send them in this case to Arne, that he can take a detailed look on the issue. For fixing the Art-Net problem, it should be doable without any hardware and if not, almost everyone in our development team has at least one Art-Net node at home or could use a software node for testing. 
So stay tuned. 
lese ich das richtig heraus dass man als Nutzer von ArtNet Nodes derzeit lieber die Finger von der RC4 lassen sollte? 
Ja... das ist richtig. Wer auf Art-Net angewiesen ist, sollte den RC4 lieber für den Moment erstmal meiden.
Schade, hatte mich schon gefreut auf RC4
Ist sACN auch betroffen?
Das habe ich von meiner Seite bis jetzt nicht probiert.
Als Information: Wir werden uns das Problem in den nächsten Tagen (vielleicht am Wochenende) genauer anschauen und dann versuchen, möglichst zeitnah eine Lösung zu finden.
As information: We will look into this problem maybe at the weekend and see, what the issue is and try to get a solution for that as soon as we can.
Ist sACN auch betroffen?
sACN läuft mit dem RC4 bei mir soweit auch auf zwei verschiedenen Rechnern. Alles verhält sich wie erwartet und beispielsweise die Umschaltung zwischen zwei sACN sendenden PCs entsprechend der gesetzten Priorität funktioniert bei mir mit meinem Showtec Net 2/3.
sACN is running with RC4 on two different computers. Everything behaves as expected and, for example, switching between two PCs sending sACN according to the priority set works for me with my Showtec Net 2/3.
This is a English Thread!
It worked for me at first, then I set up Artnet 4 times. The next time I started it, the GoBo correlation error came up. From then on, there's nothing you can do. Not even a new installation worked. (The RC3 is still present on this test computer, though)
the DMXInterfaceMgmtConfig.xml, delete or rename, then DMXC at least starts again
That’s already noticed in the tickets FS#5399 : Kernel startet nicht korrekt durch und is somit nicht für Connect freigeschaltet and FS#5400 : Aktivieren der Art-Net-Ausgabe für zu Deadlock.
Ohh sorry, I hadn't read it yet
Sooo, for your information: Arne and I debugged together and we have now fixed two problems at once: One was a problem in the Art-Net plugin, which we found and fixed. The other was in the kernel itself. If there was a problem in a plugin or interface during startup, that blocked the main process of the kernel. This led to the behavior seen in RC4. With RC5 both problems have been solved. I am now finalizing this RC and then it will go through the internal test. You will get a fixed RC version soon.
Newly created posts will remain inaccessible for others until approved by a moderator.
