Originally Posted by jocala
Sorry, I can't duplicate your issue using any version of Windows, nor have I gotten other reports. Offhand I don't have any theories. For diagnostics I'd try launching from the command-line and see if any errors appear. You could also try booting into safe mode.
Okay, thanks, I'll give that a try.
---------- Post added at 09:17 PM ---------- Previous post was at 08:45 PM ----------
The same thing happened in Safe Mode with Networking, which is unfortunate because that means it's nothing to do with my startup or background applications, which is something I could troubleshoot on my own. But here are some more symptoms which may bring something to mind...
1) The adbLink log shows "starting server" very quickly, even though the GUI doesn't show up for at least 10 minutes later. Does that suggest that the "server" (whatever that is in this case) is taking to long to initialize or whatever?
2) Whenever I try to exit formally, using File->Quit, the GUI never goes away (or at least not soon enough). And when I click the close box, the GUI disappears immediately but the task manager shows it is still active, along with at least two copies of adb.exe
3) When I launch adbLink.exe in normal boot mode, I use Process Hacker 2 to list it's open windows, which is an empty list until the GUI appears. I note this because I wondered if something in my setup prevented the GUI window from appearing earlier.
Okay, about trying the command line, which command string should I enter?