locked
1607 Computer in Computer Group w/Multiple Approved Feature Upgrades (1703, 1709, 1803) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I got pulled into a WSUS issue late & I'm trying to make sense of it all.

    I'm starting w/a Win 10 Enterprise 1607 (14393.576) & am testing why 1803 isn't installing.

    What I've done is throw a computer into its own Computer Group that have all the 1607 (business editions) updates Approved, as per its' report in WSUS. I also have all 1607, 1703, 1709, & 1803 updates Approved. I was able to get it to upgrade to 1709 eventually & after multiple failures on 1803, I Not Approved 1803. Even after checking in when 1803 was Not Approved, it would try to install 1803 & fail.

    I eventually was doing so many things to try to get it to install, I messed it up & had to do a Reset PC (keep my files) & after that it upgraded to 1803 w/o issue. That really doesn't help me in determining why it won't install on our image. Previously trying to install 1803, I was getting 0xc1900107 as the result when I'd go back & check the Update History (I saw somewhere that might be a driver issue, so I upgraded the BIOS). I ran the WU Troubleshooter multiple times & it couldn't fix the WU db so I renamed the steps to rename the SoftwareDistribution folder, too (net stop wuauserv, crptsvc, bits, msiserver & the net starts). I had ran DISM & SFC & both came back good.

    I have another computer I'm doing the whole process on again, but my bigger question is: Is WSUS smart enough to see what a computer is @ & only install the appropriate update for that version before it tries to upgrade to the next feature upgrade? It appears to me that it's not & it's trying to do the 1709 updates & them the 1803 all in one shot. If that's the case, do I have to make separate groups for 1607, 1703, 1709, & 1803-level computers?

    My WSUS is on Server2016.

    If anyone has something meaningful to share re:this, I'd greatly appreesh it.

    Thanks

     
    Thursday, October 11, 2018 10:47 PM

All replies