Unfortunately, I can't get the method described in this thread to work at all. Whenever I kill OVRservice_x64.exe, Windows stops recognizing the DK2 as a display and the status light on the kit turns off. When I launch Elite after that, status light turns on (in amber, not blue), Windows plays the "device found" sound in the background, and my main screen turns black for half a second as usually happens when the GPU driver accomodates a new display. But just a second later, Windows plays "device lost" signal, status light turns off, and the screen blinks again, with Elite window reappearing on the desktop. Then the device is found again and window disappears again. This repeats indefinitely, never stopping.
All I can deduce from that is that OVRservice_x64 should not be stopped as otherwise Windows is unable to complete the setup of the kit and drops the device. Is there anything I can do to work around that?
If that's relevant, I'm using Windows 8.1 x64 and GTX680. I have tried any and all combinations of disabling services with and without the aforementioned tool, made sure to set Rift to External mode, checked the hardware to work in the standard demo (everything works flawlessly), and tried to set DK2 as primary and secondary display in the Windows display preferences. Nothing helps. I either get no tracking and distorted image if Oculus config tool and services are kept running, or I get infinite display lost/found loop if the service is not running.