I don't see the point in answering you really, you sure have made up your OCD mind about something that you have gotten all wrong in your mind. You talk about "hidden gem" like this regkey would be something hidden and unknown to public and even the programmers at MS? Why I say it's been useless is because the information given on the desktop by that regkey has never given any real useful information for an administrator like me, I need more info from the client than this can give. Like way back in the day when Windows NT 4.0 was the hottest Windows version there was, that regekey was not even programmed to work yet. In Windows 2000 the regkey was introduced but always showed "Windows 2000 Professional, Build 2195" no matter what Service Pack was installed. After that Windows XP Professional for some time showed some useful info "Windows XP Professional, Build 2600.xpsp1.020828-1920 (Service Pack 1)", but after that Window Vista was back to not say anything about what Service Pack was installed "Windows Vista (TM), Build 6002". Same thing with "Windows 7, Build 7601", no matter the Service Pack level. In this case, Windows 10 Enterprise LTSC 2021 BuildLab really is "Build 19041.vb_release.191206-1406" so I don't get what your fuss is about, just because earlier versions that you compare to was not build that same way Windows 10 Enterprise LTSC 2021 is. Windows 10 Enterprise LTSC 2021 is really just a "patched up" version of Windows 10 version 2004 (Vibranium) Build 19041, hence that "19041" in your complaints. ATM there is no newer version of ANY Windows 10 with a higher build than 19041. All versions after 2004 are patched 19041, 20H2 and 21H1 including LTSC 2021 (21H2). Have a look at wikipedia "List of Microsoft Windows versions" for details. As I said earlier, Bginfo can give you the information YOU want instead of this useless PaintDesktopVersion. It's not using the "same technique", it's using whatever technique you want instead to print the information that you tell Bginfo to retrieve from either registry or WMI query, even environment variables, information from within files, timestamp of a file, contents of a file or a VB script file. In your case you probably want to create custom fields like this in your BGInfo config: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\BuildLab HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DisplayVersion HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuildNumber HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\UBR (note: ReleaseId was earlier in use before DisplayVersion came, but is now deprecated and still only in use for compatibility reasons) Which could yield on the desktop: Windows 10 Enterprise LTSC 2021 19041.vb_release.191206-1406 21H2 (OS Build 19044.1387)
More and more topics are changing into war between some. - 99.9% of users do not care about your views - they do not even know what's going on - finish these wars or continue privately - not in this forum!
Several pages of debate because of just "numbers" I haven't even read in depth what it's about but the truth is that Microsoft realized that it couldn't deliver a stable build twice a year after the bug that erased files when doing inplace upgrade in 1809 and decided to invent the "Enablement package" to trick laypeople into thinking they keep getting 2 feature updates a year when in fact they only get one "number" upgrade and with it makes everyone happy then they created a Windows 10 with a new skin and one feature update a year and called it Windows 11.
I think the one feature update per year (kind of like the old service packs) is much better than every 6 months, which was originally introduced by stupid MSFT. They were the ones insisting how every 6 months were a great idea. A lot of us like LTSB/C because we wanted to get away from MSFT's semi-annual channel and have stability and as little bloat instead. MSFT is the one who is actively discouraging users from installing LTSC. I think everyone on this thread has chosen to ignore MSFT
Actually only a relatively few (seekers) got the 2 feature updates a year, most systems ran a build to the eos limit of the build they were on before the upgrade was enforced upon it.
lets have a look: ><o(((°> @zbigniew59 as the COMEDiAN said: it is all a joke! indeed! think about all those wasted hours on SAC running servers good to read they dropped this stupid idea on server2022 and ruined at again big time by letting vanish hyper-v well almost, maybe a lot, though not the majority. the most asked question over the years was: how get store? or am i wrong on that?
Once I used Add-AppxProvisionedPackage, the appx package got also installed for the current user (Get-AppxPackage | findstr "Microsoft.VCLibs" returned the libs), thus Add-AppxPackage is unnecessary afterwards.