Last night two optional updates got installed on Server 2008 R2, KB3068708 and KB3050265. This morning, I pop open remote desktop from the machine in my office and connect to the main machine so I can do my morning maintenance on the guest running on the machine(Server 2003). After doing this same routine for the last 5 years every workday, to my shock, I was able to do exactly one mouse click and then it would not take any other keyboard nor mouse responses.
Since my Windows 8.1 machine also got upgrades, I went to the other building, unlocked the server room, turned on the monitor, logged in and tried local. Still no go. Tried full screen, still no go. Looked up every keyboard shortcut possible(since it says "keyboard input captured" at the bottom but "mouse input not captured"). Nothing, no gd response what-so-ever. I reboot the machine, I shut down the guest and start it back up, nothing. I know the vm is running because I can watch all the activity on the screen(including a helpful POS hacker doing a dictionary attack versus our SMTP server that I'd really like to block, but, of course, can't, because I can't type a damned thing).
I go through the list of windows updates installed, I uninstall both of them. Do all the rebooting. Same thing.
I go through every menu option I can think of, I do every search I can think of. The fixes people indicate for mouse is all sorts of things to do with the keyboard in the guest, which I can't do because it's not responding. You know, like, going to Action->Insert Integration Services Disk. But that comes up with a prompt to continue to upgrade or repair, which...requires keyboard or mouse interaction with the guest.
Finally get a little brainstorm when I see Clipboard->Type Clipboard Text. I open up notepad, copy a space, and am successfully able to click OK and then OK again after it says it's complete. I send a shutdown message, reboot it, still no keyboard nor mouse. Reboot the whole machine, still no keyboard and mouse.
I'm now 4 hours into this and at a complete loss as to what I can do to fix it. If this crap got broken by the two windows updates, why the blankety-blank didn't it get fixed by uninstalling them? Neither of those updates indicated they dealt with hyper-v, so why would they create this disaster anyway?
If I had the ability to do a windows+run from clipboard->type clipboard text, I could potentially work my way into uninstalling the services and reinstalling them(or using msconfig and doing the redetect hal thing that one person did when their mouse stopped working). But, I can't even get a tab to go over, much less alt+home or arrow keys.