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

Page 8 of 13 FirstFirst ... 678910 ... LastLast
  1. Diankah's Avatar
    Posts : 28
    Windows 10 Home 64-bit v 1803
       10 Mar 2018 #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 ComputerSystem Spec


  2. Posts : 1
    Windows 10 Pro 64-bit
       10 Mar 2018 #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 ComputerSystem Spec

  3.    10 Mar 2018 #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:
    Click image for larger version. 

Name:	image.png 
Views:	4 
Size:	69.2 KB 
ID:	180334
    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 ComputersSystem Spec

  4. Bree's Avatar
    Posts : 9,113
    10 Home x64 (1809) (10 Pro on 2nd pc)
       10 Mar 2018 #73

    EdTittel said: View Post
    ... 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 ComputersSystem Spec

  5. Diankah's Avatar
    Posts : 28
    Windows 10 Home 64-bit v 1803
       10 Mar 2018 #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 ComputerSystem Spec

  6.    10 Mar 2018 #75

    Hi,

    Diankah said: View Post
    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 ComputersSystem Spec


  7. Posts : 969
    Windows 10 Home x64 and Pro x86
       11 Mar 2018 #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 ComputerSystem Spec

  8. ThrashZone's Avatar
    Posts : 3,984
    3-Win-7Prox64 2-Win10Prox64
       11 Mar 2018 #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 ComputersSystem Spec


  9. Posts : 49
    Windows 10 Professional
       11 Mar 2018 #78

    fdegrove said: View Post
    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 ComputerSystem Spec

  10.    11 Mar 2018 #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 ComputersSystem Spec


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

Related Threads
UPDATE 3/5: Cumulative Update KB4090913 Windows 10 v1709 Build 16299.251 - Mar. 5 - Windows 10 Forums Source: https://support.microsoft.com/en-us/help/4074588/windows-10-update-kb4074588 Direct download links for KB4074588 MSU file...
Source: https://support.microsoft.com/en-us/help/4058258 Direct download links for KB4058258 MSU file from Microsoft Update Catalog: :arrow: Download KB4058258 MSU for Windows 10 v1709 32-bit (x86) - 364.1 MB :arrow: Download KB4058258...
UPDATE 1/18: Cumulative Update KB4073291 Windows 10 v1709 Build 16299.201 - 32-bit - Windows 10 Forums UPDATE 1/17: Cumulative Update KB4073290 Windows 10 v1709 Build 16299.194 - 64-bit - Windows 10 Forums Source:...
Source: https://support.microsoft.com/en-us/help/4073291/january-18-2018-kb4073291-os-build-16299-201 Direct download link for KB4073291 MSU file from Microsoft Update Catalog: :arrow: Download KB4073291 MSU for Windows 10 v1709 32-bit (x86)...
UPDATE 11/30: Cumulative Update KB4051963 Windows 10 v1709 Build 16299.98 - Windows 10 Forums Source: https://support.microsoft.com/en-us/help/4048955 163809
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 19:41.
Find Us