This might sound bloody obvious, but have you tried the keyboard/mouse/dongle rig in another computer entirely? If it fails in a different rig, then there's your problem right there. If it works perfectly in another rig, but not in yours, then your simplest option is to save any important files (assuming you use the PC for more than just gaming and general browsing, of course) to en external source such as a flash drive, then restore your system to a time when everything functioned correctly*. You do set system restore points when everything is functioning smoothly, don't you? If that fails, you're beyond the kind of help it's reasonable to expect on a non-tech oriented community. There are plenty of good and reliable tech fora and blogs out there out there, though. Google (or the search engine of your choosing) is your friend in these matters.
I will make one suggestion before departing this thread which may be of use to you, and is minor enough to cause no collateral damage (Sounding as it does, like an irritating, but relatively minor, INFCACHE problem), i.e. It might help, is easy to do and absolutely will not hurt anything, even if it doesn't work.
-1. Go to control panel>system and maintenance>system>device manager
-2. Once inside the device manager, expand the tree for Human Interface Devices.
-3 Update the drivers for all unknown devices.
-4 Windows won't actually find any unknown devices. When prompted, select "Browse my computer for Driver software"
-5 type or browse to C:\Windows\winsxs as the driver location
-6 If your system warns you about unsigned drivers (which it most likely will), ignore it and continue
-7 At this point, if you're lucky, Windows
should install the correct driver for your devices.
-8 If this succeeds, punch the air in jubilation at your victory over the machine, maybe do
a little victory jig. If this
fails, drop to all fours and give it your best
Chuck Heston in Planet of the Apes, and get Googling to find someone far more tech savvy than I am.
* Disclaimer: - I know that to some users, doing a system restore (to a previous working configuration, not factory settings
) for this particular issue seems like fumigating an entire house to kill one fly, but at some point in a thread like this, some muppet will invariably suggest it's a registry problem. Once that happens things go one of two ways. Someone with no knowledge at all and access to Google messes around in there and things get even wonkier, or far worse, someone with a little bit of knowledge, but nothing like as much as they think, will start spouting "advice" and things will get
really fucked up.
The registry is not for amateurs, no matter how well mentored or enthusiastic they may be.