New
#31
I am a Systems Manager for a midsize church that has 17 devices. We have upgraded half of our units to Windows 10. I too ran into the annoying no keyboard/mouse on one of our HP Pavilion Desktops. It had been running beautifully. I tried all the tips from the Microsoft forum as well as other web sources to no avail.
I solved my problem but the following is not for novice users. This process took about two and half hours:
1. Knowing there could possibility be a reinstallation of the operating system with a chance to lose everything I needed to get to the data on the unit. I opened the computer case and attached a USB to SATA/IDE adapter kit ($14 to $25 at computer stores) I have in my toolbox for doing such things to the disk drive. (Laptops require removing the hard drive)
2. I attached the cable via USB to a nearby second computer. The drive appears as drive e: and a message to SCAN DISK and Fix appeared. After performing this task I went to USERS/MY DOCUMENTS and retrieved my data forwarding to the second computer.
3. After assuring I have my data, from the second computer I ran Check Disk on the ailing drive. This is done by keying CMD in the search line on Windows 7 or 10. Right mouse click on ICON and run as administrator. A DOS box will appear. Type CHKDSK space (drive letter) / F. It should look as following: CHKDSK e: /f
4. The information screen went crazy as numerous disk errors were detected and repaired. It ran for nearly 45-minutes.
5. I disconnected my KIT and reattached the SATA cables of the ailing system. I powered on and got a message to Wait, Windows 10 is preparing for boot. It took about 5 to 8 minutes and the system finally started correctly.
6. After such trauma to a drive I always use tools such as CC Cleaner to remove program junk. It found numerous registry errors from the many Windows 10 restart attempts. I restarted my computer again after performing this process. The first time this is done the system restart will be lengthy putting everything in place. Now the computer works as expected.
I have had two such Windows 10 blue screen events the past 90-days and the suggested Microsoft fixes don’t work very well. One system I had to perform a clean Windows 10 installation. That is for another topic on the forum