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.
-
Anonymous
2015-07-09T12:22:08+00:00
269 additional answers
Sort by: Most helpful
-
Anonymous
2015-08-05T08:45:59+00:00 How do I go back to 7?
-
Anonymous
2015-08-05T13:56:40+00:00 I had the same problem. Not sure if this has already been posted..My laptop uses the Microsoft drivers for the keyboard to work. My resolution was to uninstall the driver for my keyboard and reboot. Windows will reinstall the driver and you can then login.
-
Anonymous
2015-08-08T01:17:03+00:00 I too have the Sabertooth 990FX but with a quad care cpu and only 8 gigs of AMD ram.
I upgraded to Windows 10 Pro from windows 7 pro this morning. It seemed to be just fine. My AMD catalyst driver wanted to update so I did that and then the system wanted to reboot. I am running the ASUS Sabertooth 990fx with the 1604 drivers. Asus help has been worthless saying that they don't plan to update the bios for any boards older than the current model release.
After restart my system hard drive light blinks and I have no mouse or key board functionality. In fact no USB functions at all. I have the Corsair K90 keyboard and the Corsair M60 mouse. I have tried other USB ports, done all the trouble shooting I can think of up too and including going through the bios, trying other boards, mice, and even an old PS2 keyboard. Still nothing.
My mouse and keyboard and all usb ports work in post but not after windows 10 OS takes over. At that point they become non responsive.
What the hell MS? This is one of those issues that SHOULD HAVE BEEN FIXED before launch. Now if I am able to roll back I will have to do a clean re-install of my windows 7 os and all the supporting materials just to upgrade again? I really wish there was someone I could (swear word) yell at about this but there isn't. MS should have fixed this issue BEFORE pushing the OS to consumers. This sort of thing just breaks faith with people.
sigh And I see no response form MS about this issue. Will there ever be one?
-
Anonymous
2015-08-08T02:01:23+00:00 Well I tried everything. I am currently attempting to restore previous version. My faith that this will go well is lower than lowest grain of sand at the deepest depths of the ocean. I am officially epically disappointed by this whole win10 upgrade bs. While the upgrade went well, and was working, upon reboot the system would load to the Win10 great page but none of my USB ports would work. This meant that I could not log in.
I was able to get an old PS2 keyboard to finally work after a few reboots. Thank you Asus for having this legacy port on the Sabertooth. Too bad that once I did get into windows I couldn't navigate to where I needed to go "device manager" because there are no keyboard commands that allow you to move to the left side of the system page in order to select that option. I know, I spent two hours trying everything I could.
Finally out of exacerbation I decided to just set it up to boot into safe mode. I typed in system configuration into the search window, it brought up the msconfig app, I went into the boot tab and enabled safe boot. I rebooted. I then pressed F8 and was taken to the trouble shooting options. I navigated that system and enabled safe mode.
However, when starting up in safe mode I got an exception error - wdf010000SYS. No matter what I did I kept getting exception errors. I gave up.
Thank you MS for making this a huge (swear word that rhyme's with truck) waste of my time. And for breaking my system. (thankfully I have back of the drive but **** MS.)
Follow up = I was right the restore failed. :(