Forum Discussion

Karl-WE's avatar
Karl-WE
MVP
Feb 18, 2021

Fixing WSUS OS description in WSUS DB based on Windows OS version number

Currently WSUS does no longer list the OS version correctly. I have passed on some links on this to Aria. This has started with the amazing change of enablement packages. Windows 1909 are repor...
AriaUpdated's avatar
AriaUpdated
Icon for Microsoft rankMicrosoft
Feb 18, 2021

Karl-WE Hey Karl, thanks for reaching out and sharing the information! I ended up looking into it and found that it has always been like this.  This happens because of the shared code base between 1903/1909 and 2004/20H2 and the fact wuaueng.dll version stay the same post upgrade to the newer version from the pairs.

 

We are looking at potential options to alleviate this pain. Thanks again for sharing your feedback.

  • Karl-WE's avatar
    Karl-WE
    MVP
    Feb 18, 2021

    Hi all,

    thanks for your time and feedback.

     

    I know and understand the point why it happens

    and would like to encourage you to have a talk with your MVP Adam Marshall from good ol' Canada, how he easily adresses this on a database layer with powershell.


    And no fear this would make his great WAM obsolete.

    The main point is the reason for this regression is not by design but rather unfortunate Implementation which never expected enablement packages.

    20H1 will be the next version that uses it so we have then 5 supported products usual WSUS admins cannot differentiate in reports and GUI. That should make a sufficient business case in terms of users 🙂

    Enablement packages and reduced CUs, imho are the best invention in Windows since.

    Now we need to get good old WSUS database fit for that news.

    Eventually considering to upgrade the WID from 2012 express to 2019 too 🙂 in the vNext.

Resources