Recent update causing USB mouse/keyboards to stop working

Hi Siv,

Both my computer and my wife's were hit with no keyboard and no mouse. Mine is now back to Windows 8.1 and hers to Windows 7. I have not yet seen anything to suggest that the problem has been fixed, but you say there does seem to be a mitigating patch out that fixes the issue. Can you please  point me to a reference to that patch, or anything that says if and how Microsoft has fixed the issue.

Thank you,

Bill

Hi Siv, that worked! (Partially). My mistake was, I didn't have a space between "/Remove-Package" and /PackageName:"

It only partially worked: DISM attempted to run, then told me it had failed to do the restore, but mysteriously my mouse and keyboard then worked. I was able to log on, but while update KB4091240 had disappeared, KB4074588 was still there and refused to be uninstalled (I tried via the control panel, then by downloading the update manager from Microsoft, then by running the code again). W10 also refused to do any new updates, and everything was glacially slow. At least I could run a (painfully slow) full backup. In desperation I finally reinstalled W10, which seems to have worked. (Fingers crossed). So ... only 14 days later, and countless hours of misery, I hope Microsoft's update present has been resolved.

Thanks to you and everyone who offered help - I really appreciate it, especially as the advice I was getting from Dell on the issue was plain wrong.

Emily

Emily,

I am really pleased you managed to get somewhere with it in the end. It's so frustrating when nothing seems to work.

There does seem to be a mitigating patch out now that fixes the issue so hopefully others won't have the pain we have all been through.

Siv

Hi Siv, that worked! (Partially). My mistake was, I didn't have a space between "/Remove-Package" and /PackageName:"

It only partially worked: DISM attempted to run, then told me it had failed to do the restore, but mysteriously my mouse and keyboard then worked. I was able to log on, but while update KB4091240 had disappeared, KB4074588 was still there and refused to be uninstalled (I tried via the control panel, then by downloading the update manager from Microsoft, then by running the code again). W10 also refused to do any new updates, and everything was glacially slow. At least I could run a (painfully slow) full backup. In desperation I finally reinstalled W10, which seems to have worked. (Fingers crossed). So ... only 14 days later, and countless hours of misery, I hope Microsoft's update present has been resolved.

Thanks to you and everyone who offered help - I really appreciate it, especially as the advice I was getting from Dell on the issue was plain wrong.

Emily

I did the steps exactly as stated above.   Multiple times and triple checked everything was correct.   My windows in in C: so I did change to that.  I keep getting this error:

Error 1009:

An error occurred while attempting to access the image.

For more information, review the log file.

The DISM log file can be found at x:\windows\logs\DISM\dism.log

Did you run the "Bcdedit /enum" command and check what the drive letter listed against "OSDevice" as even though when your PC is running normally C: is the drive your Windows folder is on, when you are in the troubleshooting mode it can be mapped to a completely different letter like G: or D: so you must use Bcdedit /enum to check. This is my output when running normally in Windows:

C:\Windows\system32>bcdedit /enum

Windows Boot Manager

identifier              {bootmgr}

device                  partition=\Device\HarddiskVolume1

description             Windows Boot Manager

locale                  en-GB

inherit                 {globalsettings}

default                 {current}

resumeobject            {0210b412-b392-11e7-8a71-c90cad9caa2c}

displayorder            {current}

toolsdisplayorder       {memdiag}

timeout                 30

Windows Boot Loader

identifier              {current}

device                  partition=C:

path                    \Windows\system32\winload.exe

description             Windows 10

locale                  en-GB

inherit                 {bootloadersettings}

recoverysequence        {0210b414-b392-11e7-8a71-c90cad9caa2c}

displaymessageoverride  Recovery

recoveryenabled         Yes

allowedinmemorysettings 0x15000075

osdevice                partition=C:                   <<============== This is the line to look at.

systemroot              \Windows

resumeobject            {0210b412-b392-11e7-8a71-c90cad9caa2c}

nx                      OptIn

bootmenupolicy          Standard

hypervisorlaunchtype    Off

C:\Windows\system32>

As you can see mine is running as C: but if I was in the troubleshooting screens it might be D: or G: as you are not running in "normal" mode.

If you did do the above and your drive letter was c: then I am not sure what the issue is and someone with more knowledge on this matter may need to jump in.

On other forums I have seen them use:

wusa /uninstall /kb:4074588

From the command line and it apparently works, it might be worth a try on your system?

Siv