Windows 10 20h2 not correct number version in WSUS

Question

Hello everyone. I detected that the correct version number of Windows 10 is not appearing correctly on WSUS 20h2. Version 10.0.19041.546 is appearing instead of version 10.0.19042.x. Apparently it is the same flaw of the Windows 10 version 1909 that appears 10.0.18362.x instead of 10.0.18363.x. Has anyone managed to solve this?

Answer 1

I have the same issue and I can see that it probably is the Windows Update Agent not being updated.

OS Built version is 19.042.572 (20H2)
Windows Update Agent version is 10.0.19041.546
WSUS console shows version 10.0.19041.546

Regards
Kenneth

Answer 2

Hi Kenneth,

Thanks for your response.

It is known that the version shown in the WSUS console is the Windows Update Agent version. I know that it is very troubling for us. The forum team is assigned to troubleshoot the product and collect feedback from the users to the product team. I have already delivered the associated information to the Product Teams. But I'm not sure I'll get feedback.

In addition, it is recommended to post our ideas or suggestions into the Windows Server User Voice. The Microsoft Engineer Teams will collect and submit the information to the related engineers in time.

Thanks for your understanding and cooperation.

Regards,
Rita

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Any update on this issue?

I was planning to upgrade machines to 20H2 via WSUS, but tested on some machines and the version showed 19041 just like Windows 10 2004.

Thanks,

Qiulin

Answer 4

Microsoft still hasn't fixed this? It's a glaring problem in WSUS that just becomes more of a problem with the release of Windows 11 and newer versions of Windows 10.

Answer 5

I ran into this as well, so after working out the relevant tables in the WSUS database, I used the following SQL

use SUSDB;

select CT.FullDomainName, CONCAT(STR(CTD.OSMajorVersion,2,0), STR(CTD.OSMinorVersion,2,0), STR(CTD.OSBuildNumber,6,0)), CTD.ClientVersion, CT.LastReportedStatusTime from tbComputertarget CT LEFT JOIN tbComputerTargetDetail CTD ON CT.TargetID=CTD.TargetID ORDER BY CTD.OSBuildNumber;

Sample bit of output with names removed - shows how 21H2 (19044) shows against the client version.
10 0 19044 10.0.19041.1320 2022-01-14 14:11:27.467
10 0 19044 10.0.19041.1320 2022-01-15 16:13:33.963

I would have used CONCAT_WS to get . in the OS build version but it wasn't in the SMSS version I was using.
The build numbers don't show in the "Additional Details" section in the WSUS console.
Possibly the Mobile Operator field could be updated with this information using an SQL script, so it was visible in the console..

Hope this helps,