versions don't match

Discussion in 'Windows 10' started by ratsalad, Oct 12, 2019.

  1. ratsalad

    ratsalad MDL Novice

    Feb 27, 2010
    25
    1
    0
    The version on my desktop doesn't match what winver says.
    Any fix?
    Thanks.
     
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    26,810
    38,836
    390
    What do you mean? What version on the desktop?

    Can you post a screenshot?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. ratsalad

    ratsalad MDL Novice

    Feb 27, 2010
    25
    1
    0
     

    Attached Files:

    • ver.jpg
      ver.jpg
      File size:
      105.5 KB
      Views:
      45
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    26,810
    38,836
    390
    That probably is the result of the mess MSFT created with trying to fool people that 1909/18363 is a real new build.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Carlos Detweiller

    Carlos Detweiller MDL Spinning Tortoise

    Dec 21, 2012
    3,442
    3,073
    120
    That's what you get with Registry-only build changes. To my knowledge, the desktop tattoo string in the bottom right corner uses another source of information to determine the build string. For example, nearly all files are shared between 19H1 and 19H2, so they are still branded as 18362.
     
  6. Myrrh

    Myrrh MDL Expert

    Nov 26, 2008
    1,480
    585
    60
    Same thing seen if you look at the version field in WSUS console. 18363.xxx shows as 18362.xxx. It also very frequently doesn't match the actual revision (the xxx part on the right of the decimal).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...