On Tue, 31 Jan 2017 07:51:05 -0500, Paul wrote:

Norm X wrote:
"mike" wrote
I once had a wireless mouse that only worked on some systems.
Changing the battery fixed it.

Yes. I put new batteries in the mouse after I checked the batteries
which a volt meter. Strange, the red laser light never faltered. I
guess RF consumes more energy. Then I powered up the mouse for Win10
to detect it. It was not detected. There might be some connection to
down time for the mouse and driver replacement by Win10.

You can see that laundry-lists of sins are known for Win10.
I wouldn't believe some of them, unless I had experienced them first
hand. I think I've had a RealTek audio package installed separately, and
don't recollect the HID subsystem falling over on me.

http://www.makeuseof.com/tag/finally...-mouse-issues/

My problems just seem to be more random. Like, if I rebooted six times,
sometimes a mouse would disappear. I don't recollect my serial (RS232)
test mouse disappearing, ever. It always seems to work. I don't have a
PS/2 mouse port available,
but I'm pretty sure if I had one, it would always work too.
"If it's flaky, it's USB" is my motto.

Excellent "Motto", Paul! :-)

I always thought it was extremely arrogant of Dell to assume that
'mission critical' interfaces such as the PS/2 keyboard and mouse ports
could be replaced by USB ports and totally done away with.

USB3 has the chance to become equal to the task of 'mission critical'
reliability embodied by such interfaces as serial, parallel, PS/2, SCSI,
IDE and SATA ports given enough time to reach maturity since, unlike its
brain-dead predecessors (USB1 and USB2), it isn't relying on the CPU to
shag itself out handling every tiny detail of the PIO task such cheap 'n'
nasty interfaces heaped upon a poor defenceless CPU as a ruse to sell
more powerful Intel CPUs to the consuming masses.

--
Johnny B Good