Judging by the "Getting Started" section in the documentation at http://helpwayk.devolutions.net/#_ga=1.220966040.188973404.1473697646, It seems that the SourceID field on the "computer to be controlled" should be set to one of the network interfaces (presumably so that the application knows which interface to listen).
It seems as though it's missing some interfaces on my machine(s), and it seems like only my Oracle VirtualBox "Host Only" network adapters are enumerated in this list.
After I removed the network adapters from the Virtual Box interface, Wayk now refuses to launch "A problem caused the program to stop working correctly. Please close the program"
Windows 10 (10.0.14393)
Faulting application name: WaykNow64.exe, version: 0.9.0.0, time stamp: 0x58040182
Faulting module name: WaykNow64.exe, version: 0.9.0.0, time stamp: 0x58040182
Exception code: 0xc000041d
Fault offset: 0x0000000000029e50
Faulting process id: 0x1ef0
Faulting application start time: 0x01d22940ebc2a1c0
Faulting application path: C:\Users\ccrossan\AppData\Roaming\Wayk\WaykNow64.exe
Faulting module path: C:\Users\ccrossan\AppData\Roaming\Wayk\WaykNow64.exe
Report Id: 95066c0d-392f-4b89-a32a-1f3356d10c3c
Faulting package full name:
Faulting package-relative application ID:
Can you run "ipconfig /all > ipconfig.txt" with your network interfaces enabled as they normally would and report it back. We do filter a few IP addresses to avoid listening on certain private addresses. As for the crash, I will experiment with disabling network interfaces and see if I can reproduce the crash this way.
I have uploaded the 0.9.1.0 beta bug fix release here:
The crash should be resolved. As for the missing interfaces, I have modified the code that removes certain interfaces from the list, and made it more permissive. Let me know if it helps.