Mouse and keyboard input not working after windows 10 upgrade from windows 7.

I tried disabling the AHCI or xHCI in bios and all the USB bios support for 3.0 and unfortunately it did not help for me.

It is dismaying reading this continuiing thread as it is apparent that MSFT has a lot of work to do on Win 10 that is not being done.

So I decided to try a full Win10 clean install, since I'm well past the date to go back to 7 (shame on me, I suppose). It's definitely something with how Windows handles USB 3.0, or possibly how it speeds up boot by not fully starting some driver services. I don't know how to fix it, but take this as an example:

When I start Win 10, my Logitech G13 (gamepad, USB, works on the rear panel) flashes a few times, but never loads fully and when it gets to the login screen it turns off completely. No lights, no functionality, I have no idea why. My mouse, also Logitech, works but does not move at the correct DPI meaning it is not loading drivers also.

Now my wireless keyboard is the tricky part. It doesn't seem to load at all when I first boot to Win10 no matter what I do. However, if I take the receiver/dongle out after I get to the login screen, then do a restart and wait to get to the login and plug it back in, it magically registers and works--or at least basic functionality works. 

Another stupidly silly thing is if I get into Windows and everything is working great, then try plugging in my Xbox 360 wireless receiver everything goes FUBAR and my keyboard no longer responds, and the 360 receiver can't find a controller anyway which requires a restart. There is definitely something up with drivers or how they're loaded currently.

EDIT: I've found disabling xHCI mode in BIOS helps with the issue, and now seem to get keyboard on startup. This basically nullifies 3.0 ability from what I understand. Another weird issue is that when I plug in my 360 receiver, my Logitech G13 stops working. Really weird USB issues in Windows 10.

Have you seen my earlier post about booting off a Kaspersky rescue CD (or similar) and editing the registry.  Of course you will need another PC to make the CD - but that solution recovered the PC I was working on (after a revert to Win 7). And noone sems to have commented if they have tried it or not on an affected Win10 machine.

The UpperFilters for keyboard and Mouse were the culprits...

this issue is a show stopper for me.  I cannot risk my machines being upgraded so that they won't work at some unpredictable time.  I have retrograded my one failure machine, and am not upgrading anything else. 

Microsoft has to develop a fix.  if it is that all usb drivers are deleted and replaced when the upgrade happens, so be it.  they also have to add in some sort of intelligent (?) feedback at windows boot that determines if there is a problem and switches perhaps to an idiot level usb driver, so that the machine is at least not a win10-splashscreen-illuminated brick.  I am curious what other os sub-systems are having brain farts of similar or worse proportions.

seems to me that Microsoft should be boasting that they have windows 10 installed on 100 million beta machines.

seriously and respectfully, a fix is needed.  and yes, not having a recovery partition, and choking machines with downloads awaiting upgrade is a problem.  perhaps smaller machines should offload an image to a microsoft cloud, and perhaps there should be a dos level boot menu that allows directly activating a "save me now" hail Mary.