Microsoft claims it’s solved the USB problem with Win10 1709 cumulative update KB 4090913

[woody]

[See the full post at: Microsoft claims it’s solved the USB problem with Win10 1709 cumulative update KB 4090913]

Reply | Quote

[anonymous]

Well….it does not fix my keyboard issue （Asus T303UA).

Reply | Quote

[Susan Bradley]

What is your keyboard issue?

Susan Bradley Patch Lady

Reply | Quote

[anonymous]

After uninstall KB4074588 and reinstall KB4090913.
Everything works fine.

TKS

Reply | Quote

[woody]

Tell us more, please. What keyboard issue? Are you using a USB keyboard?

Reply | Quote

[anonymous]

Hi Woody,

My laptop is Asus T303UA which is very similar to Microsoft Surface Pro series.

The Keyboard can be separated from the laptop itself.

I believe that keyboard port is using USB port, though it looks not like the USB port.

When I attached the keyboard to the laptop, the keyboard had no function at all.

In the device manager, it shows unknow USB  device.

This morning. I uninstall KB4074588 and reinstall KB4090913.

The keyboard came back as normal.

However, after few hours. It became unknow USB device again when I woke it up from standby mode.

 

 

1 user thanked author for this post.

woody

Reply | Quote

[abbodi86]

SSUs are never OOB 🙂

1 user thanked author for this post.

woody

Reply | Quote

[anonymous]

Spinning Solid Upper Stages are Out-Of-Band. Surely that is not what you mean, so what are SSUs?

Reply | Quote

[woody]

Servicing Stack Updates.

Reply | Quote

[anonymous]

Thank You. It can be somewhat frustrating when people have plenty of space to expand an abbreviation, comments are not short message service packets.

Reply | Quote

[neildon1]

i still have around 100 machines that will not install the feb update (.248), or this update(.251),  the patching software vendor i use confirms the same issue. seems the delta patch from jan was faulty, causing it to show as being installed twice. removing the jan patch does not help

now patch .248. or 251  will not install with error  0x80092004

the vendor, myself and other customers all have tickets in with microsoft about this.

the only way i have found around the issue is to do a reinstall of the rtm release of 1709, keeping settings,  then i can install the new patches….  but not something i want to have to do to all machines,,,,,

[Edited to remove HTML]

1 user thanked author for this post.

MrBrian

Reply | Quote

[neildon1]

patch .248. or 251  will not install with error  0x80092004 can be resolved  using these steps (credit to ivanti engineers for supplying this fix )

can confirm it works
dism.exe /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.248.1.17\
dism.exe /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.192.1.9
dism.exe /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9\
Machine will need a reboot after this.
Dism.exe /online /Cleanup-Image /StartComponentCleanup

Edit to remove HTML from cut/paste
PLEASE convert to plain text (.txt) before cut/paste operation

Reply | Quote

[anonymous]

Thanks neildon1 What you shared worked!!

Reply | Quote

[neildon1]

here is a screenshot, showing 2 installs of the jan update, and the subsequent failure to install any new updates

Attachments:

You must be logged in to access attached files.

1 user thanked author for this post.

MrBrian

Reply | Quote

[anonymous]

Updates are great and all. But if the previous update rendered your keyboard and mouse useless then you can’t get into a PC to retrieve an update :/

I just spent three days with different agents online and 6 hours today with an Escalation Engineer. The upshot? I have to take it to a store. Except Microsoft don’t have stores in the UK. So I have to take it to a computer store who fix HP computers to get *them* to try and fix it- more of my time and expense. Why are Microsoft offloading the issue onto HP- it wasn’t their hardware that caused the fault. It was Microsoft’s bug ridden update.

This is obviously just a rant but I can talk through everything which was tried if that’s at all useful to the forum?

Thanks for the info given here BTW. It has been useful to hear that I’m not alone. I feel your pain 🙁

Reply | Quote

[Paul T]

If you can connect a PS2 keyboard you may be able to get in far enough to roll back the update.

Other than that it’s a restore from the backup you made last week.  🙁
Speaking of which, you need to do one before sending the machine back, in case they blow the lot away to get it running.

cheers, Paul

1 user thanked author for this post.

woody

Reply | Quote

[anonymous]

KB4090913 MADE SYSTEM UNBOOTABLE – Didn’t even get a bios screen.
After trying to boot the computer several times without success, didn’t even get a bios screen. I removed all cables connected to back of desktop computer, booted system and could here hard drive working as if it where booting, reconnected all cables, video came on but mouse & keyboard did not work. Re-booted again and system was working fine. After shutting down and re-starting, same problem occurred, repeated above procedure to get system working. Restarted system using Repair Disk and restored system from an image backup. I immediately disabled Windows Update Service and then Paused Updates for 35 days. System is now working fine without KB4090913 and KB4090914 installed.

Edit to remove HTML.
PLEASE convert to plain text (.txt) before cut\paste

1 user thanked author for this post.

woody

Reply | Quote

[MrBrian]

Issue added to KB4090913: ‘After installing KB4090913 the Mixed Reality Portal may fail to initialize resulting in error “SXXXXXXX-X” or may present a “We couldn’t download the Windows Mixed Reality Software” message after the software is successfully downloaded.’

1 user thanked author for this post.

woody

Reply | Quote

[anonymous]

kb4090914 gives me two problems: I can only have one external monitor via USB/DisplayLink, and sound is gone. There’s no uninstall option for kb4090914 on my laptop. Issue has gone to 3rd-level support at Microsoft.

Reply | Quote

[MrBrian]

KB4090914 is a different update than KB4090913.

Reply | Quote

[Author]

Posts