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

Well you learn something every day, thanks for the tip, I would have thought it would kick off if you tried that in a different hardware based PC!

 

Yup, super helpful when selling a customer on a new/er pc, i just upgrade their existing one from 7->10 and throw their hdd in! The only thing is, if it's an oem activation of windows, you will need a key to activate, but those are cheap nowadays from certain places!

 

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.

 

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."

 

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.

 

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.

 

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

 

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/packagenameackage_for_RollupFix~31bf3856ad364e35~x86~~16299.248.1.17

For 64-bit versions of Windows:
dism.exe /image:c:\ /remove-package/packagenameackage_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.

 

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?)

 

May I be a bit observant and note that that is exactly the solution that I proposed earlier?

.... You're welcome *Smile


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.