It helped me.Enable checkbox.
Mouse and keyboard input not working after windows 10 upgrade from windows 7.
I upgraded to the window 10 tech preview from windows 7 and now my mouse and keyboard dont work once the os loads up and brings me to the sign in screen. I cant even roll back to windows 7 now because I have no mouse input except for when the bios splash screen is showing. Any help would be amazing thank you.
* Moved from Insider.
Windows for home | Windows 10 | Devices and drivers
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
269 additional answers
Sort by: Newest
-
Anonymous
2018-06-19T13:43:40+00:00 I cannot solve the non working mouse issue since upgrade
-
Anonymous
2018-03-08T16:14:39+00:00 ... yes, 3+ years ... I did solve the problem COMPLETELY tho ... bought a ChromeBook and another iPad !!
-
Anonymous
2018-03-02T17:17:26+00:00 Going on 3 years with the same problem, now that is customer service. You would think with all the brain power Microsoft has, they could fix this issue. I have three computers and all three have this issue. One is an HP desktop, one is an Acer notebook and one is an ASUS desktop, I also have one ASUS notebook that has not displayed this issue yet. They range in age from 18 M to two months. The only reliable way I have found to get them running again is to do a restore. This problem started for me after the Windows update last December.
-
Anonymous
2018-02-27T20:46:57+00:00 I'd try going through all options with the bios for anything to do with USB. ie, boot and go direct to bios, and try enabling or disabling each option. it will take time, but that is certainly what worked for me.
it would be good to know the manufacturer of the board, and also "when" the freeze happens. for my machine, it was at the splash screen when windows first started. it may be different for other issues, and might help others pinpoint what is loading and failing.
and I agree; two years on and still not fixed is nasty. get with it, Microsoft! ... if you cannot fix it, then at least have a compatibility check at the start of upgrade that tells the user to run far, far away.