[DISCUSSION] Windows 10 Enterprise/IoT Enterprise (N) LTSC 2021

Discussion in 'Windows 10' started by Enthousiast, Nov 16, 2021.

  1. awuctl

    awuctl MDL Member

    Jun 6, 2020
    107
    382
    10
    I read them and you seem to be very confused by something completely normal.
    And now you're talking about "features" (whatever that's supposed to mean) without any explanation (screenshots, write ups, packages, […] or really anything) for what you said.
    The only thing you mention in those posts is how "19041" instead of "19044" (or any other build with EPs) is a bug, when it absolutely isn't.

    You're the person that's confused about build numbers, not me.
    Explain what you mean or stop bothering people with your non-problem.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. awuctl

    awuctl MDL Member

    Jun 6, 2020
    107
    382
    10
    #1062 awuctl, Nov 25, 2021
    Last edited: Nov 25, 2021
    I'll assume this is what you mean..

    shell32.dll's CDesktopWatermark::s_GetProductBuildString function (this actually fetches the build to draw for PaintDesktopVersion), uses the following registry key:
    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\BuildLab
    This is as close to what you would call the "software build" as it gets. This is the designation of the build artifacts that Microsoft actually compiled.
    Those (ie. 19041 RTM's build artifacts) happen to be the same for 19041, 19042, 19043 and 19044.

    Builds 19042, 19043 and 19044 weren't rebuilt from scratch (as any new build's RTM is); they build upon (get it?) the build artifacts of 19041.

    Edit (about winver):

    winver uses shell32.dll's ShellAboutW (which is public) and that gets the entire version from:
    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuild
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DisplayVersion
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ReleaseId (for pre xxHx version naming)
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\UBR
    This build has nothing to do with the build artifacts used for it.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. trixeo

    trixeo MDL Novice

    Jan 23, 2009
    6
    14
    0
    Agreed. I think it is similar to that a page I've found googling for this:
     
  4. Tom Mix

    Tom Mix MDL Junior Member

    Jul 24, 2009
    77
    12
    0
    @awuctl
    this is fun :gathering:
    these M$ trainees wrecked the PaintDesktopVersion [call it: feature or function or tweak or gadget or whatever]
    i hope ur not employed by M$ and forced to call it normal

    i wrote several times that for my use case it:
    • worked until BUiLD 17763 as intended and expected
      [from w2k to win1809 (maybe later, i do not play on the SAC though)]
    • is still working on BUiLD 20348 as intended and expected
      [from server2k to server2022]
    only very few know that or even use that function!
    i guess not even 1% of those
    posted here regarding my confirmation request.:dunno:
    which btw was solved because a build is not a build anymore!

    hence the PaintDesktopVersion is rendered useless :suicide:
    'artifacts'; nice description/definition, ty for the additional confirmation :animatedwink:
     
  5. awuctl

    awuctl MDL Member

    Jun 6, 2020
    107
    382
    10
    It's confusing but definitely normal.
    The BuildLab value always meant the actual build ("build" as in: what they compiled, staged and released as RTM) designation (initial version, architecture, build type, branch and build datetime which you can find in BuildLabEx), not the current running build ("build" as in: the current running version/update of the operating system).
    PrintDesktopVersion's information was never the correct "running build", those just "historically" mostly happened to have been the same number..

    Nothing's broken. It is exactly the same thing it always was - it shows you the build lab designation. This is the running build/version, but not in the same sense that the information in winver is.
    19042, 19043, 19044 may be called different build numbers, but they're all based on the same build. Hence 19041, 19042, 19043 and 19044 are all version 19041.vb_release.191206-1406.
    Not really but ok I guess.

    I personally have an entirely different naming scheme for all those designations and I couldn't give a s**t about the confusion Microsoft causes.
    Microsoft themselves have no idea what a "build" is and I can agree with that much :p

    I can't even imagine the destruction I'd cause if I worked at Microsoft
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. rh_1363

    rh_1363 MDL Novice

    Oct 3, 2018
    9
    1
    0
    Thank you dear.
    there was two packages to use:
    AIO standalone script
    Traditional pack
    which one is better?
     
  7. trixeo

    trixeo MDL Novice

    Jan 23, 2009
    6
    14
    0
    #1067 trixeo, Nov 25, 2021
    Last edited: Nov 25, 2021
    It's always been useless, if you really need useful information printed on the desktop use Sysinternals BgInfo instead.
    Btw, you are confusing BuildLab with CurrentBuild/UBR.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion:
    BuildLab
    CurrentBuild
    UBR
     
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    38,300
    66,606
    450
    The AiO will be the easiest one to use.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. Super Spartan

    Super Spartan MDL Expert

    May 30, 2014
    1,549
    883
    60
    sorry if this has been asked before:

    Still no HWID activation for Enterprise LTSC 2021?
     
  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    38,300
    66,606
    450
    Nope.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. f23948

    f23948 MDL Junior Member

    Nov 29, 2017
    79
    11
    0
    how do i inplace upgrade?
     
  12. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    38,300
    66,606
    450
    Mount ISO and run setup.exe.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Mister Dev

    Mister Dev MDL Novice

    Jul 11, 2021
    16
    4
    0
    Hi, I've read that MAK keys for LTSC 2019 don't work for 2021. If I have an already activated LTSC 2019 and do an in-place upgrade to 2021, will the OS remain activated or will I have to buy and enter a newer key?

    Moreover, what if I'll later do a clean install of LTSC 2021, won't the 2019 key work on the same machine?
     
  14. Tom Mix

    Tom Mix MDL Junior Member

    Jul 24, 2009
    77
    12
    0
    nice to see u in the 99% :doh:
    i am aware of and use bginfo.
    if you know what u are writing about please clarify:
    is bginfo using the same technique to display the info on the desktop?
    can bginfo cover all scenarios like the regkey?
    guess what:
    maybe all skilled coders @ M$ are gone now and no one even knows about this hidden gem: so they screwed it :death:not providing an appropriate replacement :censored:
     
  15. Tom Mix

    Tom Mix MDL Junior Member

    Jul 24, 2009
    77
    12
    0
    you are definitely overestimating your talent! :roll1:
     
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    38,300
    66,606
    450
    1. Just hope the key still works when reapplied to LTSC 2019
    2. Only gVLK is still the same for both 2019 and 2021 LTSC.
    3. Stop wasting money on questionable keys, simply use KMS_VL_ALL or KMS38.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    38,300
    66,606
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. awuctl

    awuctl MDL Member

    Jun 6, 2020
    107
    382
    10
    I'm not the one who somehow cannot comprehend that absolutely nothing changed about that favorite toy of yours
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. Mister Dev

    Mister Dev MDL Novice

    Jul 11, 2021
    16
    4
    0
    I bought a fully legal, used LTSC 2019 key. Reselling of keys is legal in Europe.

    What I wanted to know is whether an in-place upgrade of LTSC 2019 to 2021 will stay activated or not?