1909 Machines Reporting to WSUS as Build 18362 Instead of 18363 RRS feed

  • General discussion

  • I'm running WSUS (standalone) on Server 2019.  All of our pilot machines on Windows 10 1909 are reporting to WSUS with build numbers of 18362 (1903) instead of 18363 (1909).

    I understand that 1903/1909 share the same baseline and that the difference between them is basically a feature enablement package, but the different build numbers still need to be properly reported in WSUS. Otherwise, a whole bunch of reporting that I do just goes out the window.

    Wednesday, November 13, 2019 3:31 PM

All replies

  • Same issue here.  If the Windows Update client is truly pulling this info from Windows and sending it up to the WSUS server then I have no idea why it would be reporting 10.0.18362 instead of the correct 10.0.18363.

    It's bad enough that WSUS cannot correctly display Windows 2016/2019 vs Windows 10 under the Operating System column but you think they could at least show the correct Version number.

    Wednesday, November 13, 2019 7:26 PM
  • I have the exact same problem.

    This gives me a problem of distinguishing which of my clients are on 1909 and which ones are on 1903.

    Thursday, November 14, 2019 8:51 AM
  • It does at least look like it's Windows fault, since 1909's update agent and a few base system devices all report a build number of 18362.

    MSFT folks, any comment/update? This can't just not be fixed, is the appropriate Windows dev team being made aware?

    • Edited by ac513 Monday, November 18, 2019 2:35 AM More details
    Monday, November 18, 2019 2:29 AM
  • I have this problem also. I think that Microsoft is fully overwhelmed by internal problems.
    Friday, November 22, 2019 1:25 PM
  • I have the same problem. Any news?
    Wednesday, November 27, 2019 2:20 PM
  • Per the other thread on this, the Windows Update agent in Windows itself is still build 18362. So it's a Windows problem with it reporting an inaccurate build number due to this, not a WSUS problem it seems.

    I don't know if there's much of a "fix" other than Microsoft fixing it in Windows. The issue is present in Server 1909 too... It reports as build 18362.

    • Edited by ac513 Wednesday, November 27, 2019 2:37 PM
    Wednesday, November 27, 2019 2:26 PM
  • Also evident if you use testsigning ("bcdedit -set TESTSIGNING on"). The text in the lower right corner of the screen ("Test Mode, Windows 10 Pro, Build 18362.19h1_release.190318-1202") will report build number as 18362. "winver" correctly reports 18363.

    Friday, December 13, 2019 8:46 AM