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

Anonymous
2015-01-27T00:02:04+00:00

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.

0 comments No comments
Answer accepted by question author
Anonymous
2015-07-09T12:22:08+00:00

It helped me.Enable checkbox.

Was this answer helpful?

400+ people found this answer helpful.
0 comments No comments

269 additional answers

Sort by: Newest
  1. Anonymous
    2016-01-01T22:55:12+00:00

    You can roll back.  Just hit power a couple of times and Win 10 will put you in a Repair Screen

    Where you will have the choice to go back to your previous OS.   And you mouse will work in that screen as it does in BIOS>

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-01-01T15:17:23+00:00

    How is this helpful? I can't interface with my computer in any way, except to stare at the Windows 10 splash screen and curse. No peripheral input devices available. Looks like the latest Windows 10 update broke all my USB ports and even the old PS ports don't work. Can't roll back, keyboard not responsive even during BIOS load.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-12-13T09:30:15+00:00

    Hi Perry,  Thanks for your reply.

    I personally refuse to disable USB3.0 and  related Bios changes as USB 3 is MUCH faster for USB 3.0 devices. 

    I too preferred Win 7 but upgraded purely as I knew Support will cont5inue longer.  There are  few things I like more but very few as I am not a smart device touchscreen user.  I spent weeks tweaking out Windows Event Errors. the latest Version 10586 (TH2) does seem much better than its first release.

    Working with Windows 10. Well except for 20% of logon attempts having a disabled keyboard and mouse I must say I have NO other known issues (except 2) with Windows 10 Pro (x64) and am finding it highly stable with the Latest TH2 release.

    Asus seem really slow in bringing out Windows 10 updates for their specific boards. I suppose Hardware and Software Brands are always willing to encourage Users to buy new hardware/software rather than help users continue to use their existing equipment/software.  I had to reject a perfectly good Webcam that worked with Win XP purely because the Brand would not produce a Win 7 driver (only bothering with their newer models).

    May I ask please. Are you saying disabling Fast start-up worked 100% for you and if so what loading time difference did you find it made to fully loading.

    Many thanks


    the 2 issues as I have mentioned them (in case you or others run into them). Both may need temporary UAC permission changes to "workaround fix"

    1) Registry Editor that came with Version 10586 (TH2) crashes during searches. Many have found this and think it is to do with Keys having entries longer than 255 chars. Workaround Solution replace regedit.,exe with the regedit.exe form the first Windows 10 release 10240.  (Note if you run sfc /scannow it will find this and replace it with the newer one that crashes (so this has to be done every time after sfc /scannow is run to check system

    2) sfc /scannow reported cannot fix) and Dism /Online /Cleanup-Image /RestoreHealth failed, after I upgraded my Nvidia Dirver via the Windows 10 Device Manager where it said there were newer drivers and updated.  It seems the culprit is opencl.sys.  The default Windows 10 version is much smaller than the Nvidia updated drivers installed. When SFC /scannow or DISM are run they realize the file in the source store is not the original and report they cannot fix the issue.  To resolve I had to replace the the newer larger Nvidia opencl.sys with the original Version 10586 (TH2) version.  After that sfc /scannow and DISM reported no issues.

    I am NOT CERTAIN but i believe if a user updates Nvidia Graphics Card drivers from downloads on the Nvidia Site and NEVER via Device Manager that Nvidia installs the newer drivers BUT does not change the original Version 10586 (TH2) source  file. Certainly after I "fixed" my issue and installed the latest Nvidia drivers from a download form the Nvidia site sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth worked as normal and reported as expected (no issues except finding my working older regedit.exe -reasons mentioned above)

    These 2 issues seem to be very much MS Windows 10 issues both caused BY Windows and not recognized in time by  Win 10 developers.  Regretfully the regedit.exe has been reported now for a few weeks is a MAJOR issue for those who view and search the Registry and yet still no fix has been raced out. VERY POOR IMHO for such an important function.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-12-12T23:31:58+00:00

    I, too, disabled all USB 3.0 devices and did the recommended settings in BIOS for my Asus P8Z68 mobo as well as making sure none of the AI software choices (even my tweaks) and it did not help.   I can not get my Logitech mouse/keyboard (wireless USB) to work.   I even bought a Microsoft mouse/keyboard thinking that all MSFT equipment should be compatible.

    At this point my feeling is that Asus (and Gigabyte) boards are simply not compatible with Windows 10.   Has anyone gotten either of these mobo manufacturers to work with Win 10.

    As I have stated before.   My Desktop is quite often on so the advantage of Win 10 (faster booting) is not needed and frankly other than that change I find Win 7 simply a better OS than Win 10, so have quit trying to get the desktop upgraded.

    Was this answer helpful?

    0 comments No comments