Cumulative Update KB4090913 Windows 10 v1709 Build 16299.251 - Mar. 5

Page 8 of 13 FirstFirst ... 678910 ... LastLast

  1. Posts : 37
    Windows 10 Home 64-bit v 22H2
       #70

    Manually starting "check for updates" this afternoon found KB4090913, downloaded and installed it with no problems. Update history showed it successfully installed, and the OS Build info displayed 16299.251. Everything has been working fine. But when I checked update status at about 11:00 p.m., I saw the message "an update is being prepared for your device but it's not quite ready yet. We'll keep trying or you can retry now" followed by a retry button. I checked update history and saw that WU had attempted to install KB4090913 again and failed with error code 0x80240034 ("update failed to download" is the definition I found for this code).

    Any idea why it should attempt to download and install an update that was successfully applied? Has anyone encountered this situation before and fixed it? Thanks in advance.
      My Computer


  2. Posts : 1
    Windows 10 Pro 64-bit
       #71

    My Microsoft Wireless Mouse and Keyboard do NOT work with KB4090913. Plugging the wireless device in ALSO STOPS the laptop keyboard and touch pad to stop working. When I rollback to the January update KB4056892 everything works fine.

    Therefore KB4090913 does NOT work with Microsoft Wireless Desktop 3000 on my Laptop.
    Last edited by Peta; 10 Mar 2018 at 05:47.
      My Computer


  3. Posts : 4,224
    Windows 10
       #72

    Hey all! Mixed results here: the latest KB4090913 installed without apparent issue on all 4 of my Current Branch PCs. But I am suffering from the "KB4058258 hangover" issue that Bree reports so nicely in thread #31 (great job, sir!). I am therefore very happy to understand that an upgrade repair install should fix this issue. I'll try it on one of my non-production machines today, and see what happens. And wow! the DISM /startcomponentcleanup sequence is taking FOREVER to complete on those machines, too. Very interesting!
    Thanks again to Bree for his excellent detective work.
    --Ed--

    PS added 2 minutes later: I got this back on my production desktop when the aforementioned DISM sequence had completed:
    Cumulative Update KB4090913 Windows 10 v1709 Build 16299.251 - Mar. 5-image.png
    I therefore infer that, because I know I ran an upgrade repair install machine on this PC recently, it must've been AFTER the "hangover-causing KB update" had been applied. This one, apparently, is already fixed. Thanks again!
      My Computers


  4. Posts : 31,459
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #73

    EdTittel said:
    ... I am therefore very happy to understand that an upgrade repair install should fix this issue...
    Apart from DISM's 'un-reclaimable package' I know of no other issues this 'hangover' causes. An upgrade repair install this close to 1803 being released is probably overkill. Unless OCD is bothering you, I'd say just wait for the 1803 upgrade which should also fix the issue.
      My Computers


  5. Posts : 37
    Windows 10 Home 64-bit v 22H2
       #74

    Regarding my earlier post about Windows Update attempting to install KB4090913 a second time: I ran the troubleshooter today and it found no problems, so I hit the retry button to see what would happen. Check for updates ran and said the system is up to date. Whatever was going on yesterday has apparently gone away. This works for me. :)
      My Computer


  6. Posts : 2,832
    Windows 10 Pro X64
       #75

    Hi,

    Diankah said:
    Regarding my earlier post about Windows Update attempting to install KB4090913 a second time: I ran the troubleshooter today and it found no problems, so I hit the retry button to see what would happen. Check for updates ran and said the system is up to date. Whatever was going on yesterday has apparently gone away. This works for me. :)
    Yeah, that happens sometimes.
    Glad to hear it sorted itself out.

    Cheers,
      My Computers


  7. Posts : 16,781
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #76

    KB4090913 appears to have been partially withdrawn.
    • It was appearing in my [PSWU & WUMiniTool] list of updates but stopped doing so at some stage between14:00 [GMT] 9th March and 14:00 [GMT] 11th March.
    • I ran the check on 3 different ver 1709 computers.
    • There is nothing in the KB article to explain this change.
    • The update remains available in the WUCatalog.
    • My results match what diankah reported above.


    I checked my computers' Event viewer, System logs to confirm that I had not run this update then forgotten about it.
    I had downloaded it but had not got around to installing it yet so I might not bother at all.

    Denis
    Last edited by Try3; 12 Mar 2018 at 11:29.
      My Computer


  8. Posts : 7,724
    3-Win-7Prox64 3-Win10Prox64 3-LinuxMint20.2
       #77

    HI,
    Yeah I restored a system image that was on pause
    Loaded first round and paused updates again thankfully this steaming pile was not installed with that first round
      My Computers


  9. Posts : 49
    Windows 10 Professional
       #78

    fdegrove said:
    Hi,

    That plus a system check running Kyhi's excellent "Imagehealth" set of command seems in order too:

    https://toolslib.net/downloads/viewd...-image-health/

    Often troubles updating are indicative of native OS problems. Just saying.

    Cheers,
    I did just now update check, and it says that system is up to date. Then checked the update history, and there it still says that KB4090913 failed March 8th with error 0x800f0922. So Now I'll do a reboot once again and see how it goes, and a edit for this post follows in minutes.

    [EDIT] After 2 reboots prefect start without any notes of updates. Seems like MS is backing off and doing maybe a fix instead of letting thousands of users "do it yourselves"
      My Computer


  10. Posts : 2,832
    Windows 10 Pro X64
       #79

    Hi,

    But is it really up to date ? What does winver tell you ?

    I did just now update check, and it says that system is up to date. Then checked the update history, and there it still says that KB4090913 failed March 8th with error 0x800f0922. So Now I'll do a reboot once again and see how it goes, and a edit for this post follows in minutes.
    The error points to download problems and/or too little space left in the System Reserved partition for WU to work with.


    Cheers,
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:28.
Find Us




Windows 10 Forums