Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Microsoft claims it’s solved the USB problem with Win10 1709 cumulative update KB 4090913

    Posted on March 5th, 2018 at 20:15 woody Comment on the AskWoody Lounge

    Welcome to Patch Monday!

    A few hours after I posted my diatribe in Computerworld, taking Microsoft to task for not fixing Win10 Fall Creators Update, version 1709, wouldn’tcha know it, but Microsoft released yet another cumulative update for 1709 that claims to fix one (not all) of the admitted problems with Win10 FCU.

    KB 4090913 brings Win10 version 1709 up to build 16299.251.

    According to the KB article its sole raison d’être is fixing the USB bug introduced in the last cumulative update.

    Addresses an issue in which some USB devices and onboard devices, such as a built-in laptop camera, keyboard, or mouse, stop working. This may occur when the Windows Update servicing stack incorrectly skips installing the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance.

    That’s all she wrote. The other bugs are still there:

    • Windows Update History reports that KB4054517 failed to install because of error 0x80070643.
    • After installing this update, some devices may fail to start, and return INACCESSIBLE_BOOT_DEVICE.
    • Because of an AD FS server issue that causes the WID AD FS database to become unusable after a restart, the AD FS service may fail to start. / There is no way to undo the database corruption. To return your AD FS server to a functional state, you must restore it from a backup.

    There’s also an out-of-out-of-band Servicing Stack update, KB 4090914.

    I suggest you hold off until we find out if this patch actually fixes the problem, or if some other ogre jumps out and bites.

    If that helped, take a second to support AskWoody on Patreon

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

    This topic contains 19 replies, has 7 voices, and was last updated by  anonymous 8 months, 3 weeks ago.

    • Author
    • #172704 Reply

      Da Boss
    • #172716 Reply


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

      • #172736 Reply

        Susan Bradley
        AskWoody MVP

        What is your keyboard issue?

        Susan Bradley Patch Lady

        • #172759 Reply


          After uninstall KB4074588 and reinstall KB4090913.
          Everything works fine.


          • #172780 Reply

            Da Boss

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

            • #172799 Reply


              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.
    • #172723 Reply

      AskWoody MVP

      SSUs are never OOB 🙂

      1 user thanked author for this post.
      • #172753 Reply


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

        • #172779 Reply

          Da Boss

          Servicing Stack Updates.

          • #173025 Reply


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

    • #172790 Reply

      AskWoody Lounger

      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]

      • This reply was modified 9 months, 2 weeks ago by  PKCano.
      • This reply was modified 9 months, 2 weeks ago by  woody.
      1 user thanked author for this post.
      • #173943 Reply

        AskWoody Lounger

        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
        convert to plain text (.txt) before cut/paste operation

    • #172792 Reply

      AskWoody Lounger

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

      You must be logged in to view attached files.
      1 user thanked author for this post.
    • #172894 Reply


      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 🙁

    • #172901 Reply

      Paul T
      AskWoody MVP

      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.
    • #173633 Reply


      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.
    • #173821 Reply

      AskWoody MVP

      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.
    • #175985 Reply


      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.

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

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

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.

    Your information: