Windows 10: Keyboard and mouse not recognized after boot-up! Solved

Page 10 of 11 FirstFirst ... 891011 LastLast
  1.    22 Feb 2018 #91

    themillen said: View Post
    WOW! We have a winner folks!!!!! This absolutely kills my solution, just fixed 2 more (with UEFI since i haven't had time to bring my board from home to the shop with both UEFI and ps2) UEFI boots with this! /bow!!!!!
    devnull, give this a shot, im 2/2 so far, be sure if you get an error, try again i must've fudged typing it out the first time!
    Thank you, themillen, I may do this later, but at this point I'm hesitant to run this command on my PC, as I'm concerned that it might not be appropriate for my particular Dell PC. I was given a couple of similar commands yesterday by a Dell tech, which didn't work, but at least I could be confident that they wouldn't do further damage, as Dell was providing the commands and they know my PC. If you or anyone else who may have a better grasp of this than I do thinks that I have no reason to be concerned, I'd like to hear about it. Thanks again.
      My ComputerSystem Spec

  2.    22 Feb 2018 #92

    In the event that it may be of some interest, here's something that I was told via email today by a Dell tech concerning this issue:

    "We have already escalated the case to Microsoft . As per Microsoft they will be releasing a new set of windows updates in a couple of weeks which can resolve this issue."
      My ComputerSystem Spec

  3.    22 Feb 2018 #93

    Is it not time to consider a clean install of W10?
    And after that to install a program for imaging your C:// for recovery purposes, such as for instance Macrium Reflect? If you make such images, it is always possible to fall back to an earlier, working condition. Don't rely to much on the MS recovery options.
      My ComputerSystem Spec

  4.    22 Feb 2018 #94

    PiKo said: View Post
    Is it not time to consider a clean install of W10?
    And after that to install a program for imaging your C:// for recovery purposes, such as for instance Macrium Reflect? If you make such images, it is always possible to fall back to an earlier, working condition. Don't rely to much on the MS recovery options.
    Not yet. Reinstallation requires a very significant investment of time, when the installation of not just the OS but all the desktop applications and customization that I do is taken into account. Just customizing the OS alone---including not just the basic UI stuff, but many items in Settings (Control Panel), Services, gpedit, and regedit---takes me several hours.

    However, this experience has convinced me to create a disk image, something that I used to do but stopped doing about 10 years ago, partly because of the increasing stability of Windows, partly because I never really needed the image, and partly because the imaging apps were less than stellar. I intend to use Macrium Reflect, which I bought for the first time (based on the recommendations here) a couple of days ago.
      My ComputerSystem Spec

  5.    23 Feb 2018 #95

    Hi devnull, Been follow your saga with great interest. Very sorry for your pain. I had a similar experience to yours.
    Shortly after Win 10 came out I upgraded my main box from Win 7. After a week I tried to upgrade iTunes only to discover that the new iTunes would not install because it couldn't find the uninstaller for the previous version. After trying various fixes I gave up and did a clean install. Even though I had image backups they didn't help in this situation. So I took that opportunity to write a detailed step by step disaster recovery process for the entire reinstall effort and to make sure I had all of my reinstall materials up to date. I hope you don't end up doing a clean install be it you do at least make it count for something and document the process. Good luck with this.
    Last edited by SoFine409; 23 Feb 2018 at 13:59. Reason: spelling
      My ComputerSystem Spec

  6.    23 Feb 2018 #96

    Thanks, I need all the luck I can get at this point!
      My ComputerSystem Spec

  7.    25 Feb 2018 #97

    Leaving aside the fact that some other things this update broke (e.g., my Office install) are still in need of fixing, I want to report that the main problem has been fixed. Here is the link to the relevant Microsoft webpage:

    USB devices may stop working after installing the February 13, 2018 update (KB4074588)

    Here is the relevant section:
    Method 2: Restoring your system without a working keyboard

    If a working keyboard is not available after installing the update, your keyboard and mouse should work within the Window 10 Recovery Environment, which you can use to restore your system.

    • Start the Windows 10 Recovery Environment.

    If you restart the system before Windows finishes loading the desktop three times in a row, Windows should automatically start the Windows 10 Recovery Environment.
    If Windows will not automatically boot to the recovery screen, you can also use installation media to enter the Windows 10 Recovery Environment:

    How to create and use installation media to load the Recovery Environment


    • Use the Command Prompt to uninstall the update:


    • At the recovery screen, select Troubleshoot, then Advanced Options, and then Command Prompt. You may be asked to enter a BitLocker Recovery Key or username/password.  If prompted for a username/password, you must enter a local administrator account.
    • In the Command Prompt window, type the command listed below for your version of Windows and press ENTER.


    For 32-bit versions of Windows:

    dism.exe /image:c:\ /remove-package/packagename:Package_for_RollupFix~31bf3856ad364e35~x86~~16299.248.1.17

    For 64-bit versions of Windows:

    dism.exe /image:c:\ /remove-package/packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17

    Note: If Windows is not stored on the C: drive, replace the C: in the above commands with the appropriate drive letter.


    • Close the Command Prompt and click Continue to exit the Recovery Environment. Restart to enter Windows.


    Note that the command shown above includes the letter 'c', as you'd expect, to refer to the 'C' drive, that is, the presumed OS drive. However, though my OS is indeed on the 'C' drive, the drive identified as my 'C' drive when the Command prompt was accessed in the WinRE Troubleshoot > Advanced Options menu was *not* actually my 'C' drive---it was my 'D' drive. In order to successfully run the above command on my actual 'C' drive, I had to change the letter "C" to "D", because what the Command prompt thinks is my 'D' drive is actually my 'C' drive. (I've seen this sort of drive letter swapping occur before at the Command prompt, though I don't know why it happens.) Finally, to be clear, the "Note" near the end of the above instructions telling the user to enter a letter other than the letter "C" for their OS if their OS is not stored on the 'C' drive is *not* what I'm talking about here, as my OS is indeed on my 'C' drive. Again, I'm pointing out that the Command prompt identifies my 'C' drive as my 'D' drive, and vice-versa, and it almost certainly will misidentify the drives of some others who have a second hard drive in the same way.
      My ComputerSystem Spec


  8. Posts : 19,218
    windows 10 professional version 1607 build 14393.969 64 bit
       25 Feb 2018 #98

    Does the uninstall prevent the reinstall indefinitely?
    Does the uninstall prevent the installation of one or more windows updates? (Are any future windows update problems expected? or does this allow closure of the problem?)
      My ComputerSystem Spec

  9.    25 Feb 2018 #99

    devnull said: View Post
    Leaving aside the fact that some other things this update broke (e.g., my Office install) are still in need of fixing, I want to report that the main problem has been fixed. Here is the link to the relevant Microsoft webpage:

    USB devices may stop working after installing the February 13, 2018 update (KB4074588)

    Here is the relevant section:
    Method 2: Restoring your system without a working keyboard

    If a working keyboard is not available after installing the update, your keyboard and mouse should work within the Window 10 Recovery Environment, which you can use to restore your system.

    • Start the Windows 10 Recovery Environment.

    If you restart the system before Windows finishes loading the desktop three times in a row, Windows should automatically start the Windows 10 Recovery Environment.
    If Windows will not automatically boot to the recovery screen, you can also use installation media to enter the Windows 10 Recovery Environment:

    How to create and use installation media to load the Recovery Environment


    • Use the Command Prompt to uninstall the update:


    • At the recovery screen, select Troubleshoot, then Advanced Options, and then Command Prompt. You may be asked to enter a BitLocker Recovery Key or username/password.  If prompted for a username/password, you must enter a local administrator account.
    • In the Command Prompt window, type the command listed below for your version of Windows and press ENTER.


    For 32-bit versions of Windows:

    dism.exe /image:c:\ /remove-package/packagename:Package_for_RollupFix~31bf3856ad364e35~x86~~16299.248.1.17

    For 64-bit versions of Windows:

    dism.exe /image:c:\ /remove-package/packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17

    Note: If Windows is not stored on the C: drive, replace the C: in the above commands with the appropriate drive letter.


    • Close the Command Prompt and click Continue to exit the Recovery Environment. Restart to enter Windows.


    Note that the command shown above includes the letter 'c', as you'd expect, to refer to the 'C' drive, that is, the presumed OS drive. However, though my OS is indeed on the 'C' drive, the drive identified as my 'C' drive when the Command prompt was accessed in the WinRE Troubleshoot > Advanced Options menu was *not* actually my 'C' drive---it was my 'D' drive. In order to successfully run the above command on my actual 'C' drive, I had to change the letter "C" to "D", because what the Command prompt thinks is my 'D' drive is actually my 'C' drive. (I've seen this sort of drive letter swapping occur before at the Command prompt, though I don't know why it happens.) Finally, to be clear, the "Note" near the end of the above instructions telling the user to enter a letter other than the letter "C" for their OS if their OS is not stored on the 'C' drive is *not* what I'm talking about here, as my OS is indeed on my 'C' drive. Again, I'm pointing out that the Command prompt identifies my 'C' drive as my 'D' drive, and vice-versa, and it almost certainly will misidentify the drives of some others who have a second hard drive in the same way.
    May I be a bit observant and note that that is exactly the solution that I proposed earlier?

    .... You're welcome :)


    Also, my windows is most definitly installed on drive C: however the commandline didn't work for me with C: . hence I had to use the command Bcdedit /enum to figure out that it was in fact drive G:
      My ComputerSystem Spec


  10. Posts : 13,550
    Windows 10 (Pro and Insider Pro)
       25 Feb 2018 #100

    Flying Dutchy said: View Post
    May I be a bit observant and note that that is exactly the solution that I proposed earlier?

    .... You're welcome :)


    Also, my windows is most definitly installed on drive C: however the commandline didn't work for me with C: . hence I had to use the command Bcdedit /enum to figure out that it was in fact drive G:
    Solution posted by devnull (from Microsoft support) is for both x386 and x64 systems. Maybe that difference (most of us have 64 bit OS, but not all) prevented somebody from successfully revert changes.


    All of you guys in this thread did a great job.
      My ComputerSystem Spec


 
Page 10 of 11 FirstFirst ... 891011 LastLast

Related Threads
Keyboard & Mouse: Acer Desktop Ever since I would say, the past upgrade for Windows 10, my mom's Acer desktop's keyboard has been really laggy. For example, when I go to wake it from sleep to unlock it, the keyboard's Number lock and Caps lock...
When I start the computer it runs well with mouse and keyboard live until Windows 10 starts when both go dead.n Of course cannot control anything. This is after Evaluation copy build 15063v2 shows at foor of right bottom. I have tried F10 but...
Hi, no USB mouse is anymore recognized by the windows 10 No Drivers visible in Device Manager for USB mouse s No System Restore points available Plugging in other USB devices gives them power, but no USB sticks are recognized I...
My setup: Intel i5 with 4Gb Ram with Nvidia GeForce GT 610 video card, 64Gb SSD (Win7), 330 Gb hdd (Win Vista), and 1Tb hdd. I've been running Win7/Vista for several years now, and decided to upgrade to 10 as some of the new software I want won't...
I use left handed mouse, and swapping left / buttons works OK. I also set the wheel button to be "double click". But the wheel button brings up the context menu instead of double click. If I change to right hand mouse, the wheel button gives double...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 13:13.
Find Us