AGD

I used the IP of my first posting. The second one was an error. I have no idea how to fix that issue.

I opened ncpa.cpl, righ mouse on the Bunny Ethernet (definitely the right one called 'ethernet'), Properties, when I click on TCP4 it opens the second window (Properties of TCP4). I put in the correct IP (172.16.16.64/255.255.255.0) and I click on "OK". Second window closes and the first window (Properties of Ethernet) is still open. At this point the internet sharing works. If I then click OK on the Window (Properties of Ethernet) the (bad) IP 192 seems to automatically come back.

Yes. I changed the wifi, but I do this once in a while depending on connection speed. The only way out is, when I change the tcp4 ip I only confirm the first window and let the second window open, because at that time the right ip 172.16.16.64 still works, but as soon as I confirm the second window, the other 192 ip shows up and the Bunny has no more internet.

I have been running BB for months now and sharing the internet connection on a Windows pc was no hassle at all until today. Now , when I try to give the ip 172.16.64.64 to the RNDIS adapter, after confirming with OK, the IP adress changes to a local network adress (192.168.137.1 - dunno where this suddenly comes from) Can't ping and apt-get from the Bunny anymore.

You can use powershell: https://gallery.technet.microsoft.com/scriptcenter/Get-Remote-Logon-Status-d8c2318a

You probably have tried out this payload: https://github.com/hak5/bashbunny-payloads/tree/master/payloads/library/credentials/PasswordGrabber It on switch 2 and it might still be there. Is it possible, that you were using switch position 2 instead of 1 to test your own payload?