Recent update causing USB mouse/keyboards to stop working

Thank you people for your suggestions. I don't have a PS/2 port nor a spare slot for a card. I've tried a bluetooth keyboard and it didn't work. I tried the command line above (I've triple checked, I'm sure I typed it exactly, and I know I'm 64 bit), and I get the error message:

Error 87: The remove-package/packagename option is unknown.

When I go to the command prompt, it is x:\windows\system32>

That's where I typed in the code. Is this correct?

Any other suggestions, rather than the miserable ones of losing at the least all my programs?

thanks again, I so appreciate people trying to help me, Emily

Emily,

These are the steps to follow I think you can jump to step 3 as you must already have got into the command line:

Step 1

Do the 3x power off thing to get to your system restore menu

Step 2

Get the command prompt going

Step 3

Type:

Bcdedit /enum

Step 4

This will produce a list of text blocks, in one of them look for the word:

"osdevice"

Somehwere in that same block of text there will be a drive letter, make a note of that and use that as the letter you use in the next  step after "/image:"

If you don't see OSDevice in any of the blocks try typing:

C:

Followed by the enter key (this will change the drive to the C: drive, then type:

dir

And again press enter.  If you see a listing that includes:

C:\Users and C:\Windows and possibly C:\Windows.old then the drive letter you want is "c:".

If you don't see these folders listed type:

D:

And press enter and then type:

dir

And again press enter straight after it.  Again see if you see C:\Users C:\Windows etc listed, if you do then d: is the drive to use.

Keep repeating this process until you find the drive letter that has those folders.

Once you have the drive letter, then move onto the next step and replace the part of the line that is /Image:G:\ in the example with your letter, so if you found the folders on the D: drive then swap "/Image:G:" with "/Image:D:".

Step 5

Type:

Dism /Image:G:\ /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17

Then press ENTER to run the command.

Note you must type the above line exactly as it appears above, if when I post this it has split onto two lines understand that it is all one line starting at "Dism ..." and ending at "...1.17".  Also note that there are spaces between Dism and /Image, there is another space between "/Image:D:" and /"Remove-Package" and another space between "/Remove-Package" and /PackageName:"... Also note that the tilde symbols are NOT normal dashes (on my UK keyboard the tilde appears as the shifted version of the "Hash" or "Pound" key if you are in the US.

The tilde looks like this:

~

I have blown it up to a larger size so that you can see it.

Note also that there are two tildes between "amd64" and "16299.".

You must get the line exactly the same as it is shown above or it will not work.

Best of luck, let's hope you succeed this time.

Siv

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

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

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