none
windows 10 1909 not correct number version in WSUS RRS feed

  • Question

  • Hi,
    I noticed that my computers who have upgrade to windows 10 1909 have not the correct number version in wsus report.
    They appears like 10.0.18362.xxx instead of 18363.xxx  (https://docs.microsoft.com/fr-fr/windows/release-information/)

    Is it normal ?

    Regards

     
    Friday, November 15, 2019 8:37 AM

Answers

  • Hi,
      

    They appears like 10.0.18362.xxx instead of 18363.xxx  (https://docs.microsoft.com/fr-fr/windows/release-information/)

    The version number 10.0.18362.xxx that you viewed in the WSUS console is the version of the Windows Update Agent for the client. You can verify it by checking the version of the client's wuaueng.dll (located on Windows\System32).
       

    In my test, as you can see, the currently installed Windows 10 Version 1909 client's WUA version is indeed 10.0.18362.XXX. By reporting to WSUS, it also prompts for the 1909 version of the monthly summary and service stack update. So for now, everything works fine.
        

    Hope the above can help you.
       

    Regards,
    Yic


    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Florentyyy Monday, November 18, 2019 10:36 AM
    Monday, November 18, 2019 2:07 AM

All replies

  • I did notice the same problem

    Gert MCITP SA, EA & VA, MCSE Private Cloud, MCSA Windows 2012

    Friday, November 15, 2019 12:55 PM
  • Hi,
      

    They appears like 10.0.18362.xxx instead of 18363.xxx  (https://docs.microsoft.com/fr-fr/windows/release-information/)

    The version number 10.0.18362.xxx that you viewed in the WSUS console is the version of the Windows Update Agent for the client. You can verify it by checking the version of the client's wuaueng.dll (located on Windows\System32).
       

    In my test, as you can see, the currently installed Windows 10 Version 1909 client's WUA version is indeed 10.0.18362.XXX. By reporting to WSUS, it also prompts for the 1909 version of the monthly summary and service stack update. So for now, everything works fine.
        

    Hope the above can help you.
       

    Regards,
    Yic


    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Florentyyy Monday, November 18, 2019 10:36 AM
    Monday, November 18, 2019 2:07 AM
  • Hi,

    could you answer the question, please? How to correct display version in WSUS??

    Monday, November 25, 2019 9:22 AM
  • Seems to me that WSUS isn't doing anything wrong, Microsoft just didn't make the Windows Update agent reflect the new build number in 1909.  They'd have to fix it in Windows itself.

    I'm not a fan of distinct Windows versions sharing a baseline and differing only through feature enablement.  This similar issue is littered all over the OS-- Open Windows Sandbox on 1909, and you get a 1903 guest.  Query any base system devices in 1909, and their driver version will be 10.0.18362.1.

    WSUS misreporting due to Windows itself misreporting is just one of many fails with 1909.

    • Edited by ac513 Tuesday, November 26, 2019 6:29 PM
    Tuesday, November 26, 2019 6:27 PM
  • I know that WSUS isnt´doing anything wrong.

    Microsoft Development or Quality Assurance team are doing things wrong. But for me solution - "it isn´t bug, but feature" or "It is how Microsoft works" - simply ISN´T the solution .  We cannot accept this kind of behavior. Sorry for that.

    Friday, December 6, 2019 1:36 PM