Please fix the bug of WSUS not correctly reporting 1909 clients.
Please fix the bug of WSUS not correctly reporting 1909 clients.
Anonymous
shared this idea
12 comments
-
Jean Marie THIA
commented
Since there is a tool than can fix the data base, may be we can have the sql query and update the database.
-
AC
commented
I set up a quick test environment with the current Server 2022 preview build, no net change there either. (I really didn't expect it, but didn't hurt to look)
I'm convinced that this won't be fixed until the Windows team figures out how to reconcile the Windows Update Agent build number for OS builds numbers resulting from enablement packages. It doesn't appear that the Windows Server devs will or want to read & display another string in a new column in WSUS itself.
-
AC
commented
21H1 will seemingly be another enablement package laid upon a 2004/20H2 base, so this issue will soon become even worse when we won't be able to distinguish 3 separate Win10 versions from each other in WSUS. Seriously, this has to get fixed, either by Windows 10 itself updating the build number of the Update Engine, or WSUS getting patched to instead reflect clients' build numbers.
-
Mika Melonen
commented
This same situation is now with 2004 to 20h2 upgrades using WSUS. This problem was reported already in 2019 so fixing this seem to be low or "no priority". This is an issue now with production since don't know which upgrades went right and which not. Have to find other ways to see which version is installed.
-
Stephane SAINTILAN
commented
Currently, you not show the OS version but the WU Agent version.
and I think the issue is when you upgrade from version 2004 by using the "Feature Update to Windows 10 Version 20H2 x64-based systems 2020-10 via Enablement Package"so you have 3 ways to fix that :
1- update also the agent version when you do the upgrade
2- Replace in the WSUS server the agent version by the os version
3- Add a new column in the WSUS server named "OS Version" and rename the currect column "version" with "Agent Version"the fix is very urgent because now I cannot throught the WSUS console know what computers are with the latest version !
Thanks.
-
Anonymous
commented
The problem is, that WSUS gets the numbers from "Windows Update Engine" and not the build number from the OS. Because of this, WSUS reports correctly but the wrong number.
I (and apparently many others) want the OS build number to show up and not the build number of "Windows Update Engine". Please fix this.
-
Flavio Alves
commented
POR FAVÕ ARRUME ESSE BUGUI. TÁ ATRAPAIANO EU TRABAIA
-
Thalles Leonel
commented
Hello, version 20h2 has a similar bug.
-
Arnaud DANGIEN
commented
Dear WSUS developers,
Could you please display in the WSUS console the correct version of Windows 10 1909 (build 18363) which unfortunately appears until now as Windows 10 1909 (build 18362)? -
Anonymous
commented
This isn't just limited to WSUS.
ntoskrnl.exe and ntdll.dll in windows\system32 are also reporting the Build 1903 versions across both the Enterprise and Professional editions.So it looks like MS have made a basic build numbering error - and its still there in the July 2020 .iso on MSDN Downloads.
-
Anonymous
commented
We need a fix fast!
-
Anonymous
commented
hi I would like to be able to see inside the Wsus console the correct version of Windows 10 1909 that is 18363 instead of the version 18362. Thanks