question

DANGIENArnaud-4228 avatar image
0 Votes"
DANGIENArnaud-4228 asked RitaHu-MSFT rolled back

Windows 10 1909 (build 18363) not correct number version in WSUS (1903 - build 18362)

Hello,

Windows 10 1909 (10.0.18363.xxx) computers have not the correct number version in WSUS report.

They appear like 10.0.18362.xxx (Windows 10 build 1903) instead of 10.0.18363.xxx (Windows 10 build 1909)


No fix yet for this problem that has been present for a year ?


Answers explaining that the WSUS console displays the agent version (C:\Windows\System32\wuaueng.dll) but not the operating system version are not relevant.


Regards


Related links :

https://social.msdn.microsoft.com/Forums/en-US/a78aeebd-5a2c-46e7-92b2-57fddedbaa3e/windows-10-1909-not-correct-number-version-in-wsus?forum=winserverwsus

https://social.msdn.microsoft.com/Forums/en-US/f0e2d417-6873-4943-8d6f-f22fcfda01d4/wsus-showing-bad-build-and-cu-numbers?forum=winserverwsus

https://docs.microsoft.com/en-us/windows/release-information/

windows-10-generalwindows-server-update-services
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RitaHu-MSFT avatar image
0 Votes"
RitaHu-MSFT answered RitaHu-MSFT edited

Hi DANGIENArnaud-4228,


Thanks for your posting on Q&A.


In my opinion, it is not a problem but it is the design. In the WSUS console, the Version is Windows Update Agent's version of the client, not the OS version. The WUA version is not always consistent with the OS version.


We could check the WUA version of the client by the following steps:

  • Open the %systemroot%\system32 folder. %systemroot% is the folder in which Windows is installed. For example, the %systemroot% folder is C:\Windows\System32

  • Right-click Wuaueng.dll, and then select Properties.

  • Select the Details tab, and then locate the file version number.


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.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ThallesLeonel-0834 avatar image
1 Vote"
ThallesLeonel-0834 answered

Hello, if microsoft thinks this is not a bug, WSUS has to change.

Instead of showing the Windows Update Agent version, you have to show the Windows version.

This is hampering the organization of updates that are typically applied by computer group.

Is it very difficult for the giant Microsoft to fix this?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RitaHu-MSFT avatar image
0 Votes"
RitaHu-MSFT answered RitaHu-MSFT rolled back

Hi ThallesLeonel-0834,


Thanks for your response.


If we integrate the WSUS into Configuration Manager, we could check the operating system version on the CM console. But the WSUS doesn't have the feature now.

Forum teams are support to troubleshoot the related product and collect feedback from all the users. I will try the best to deliver the information to the product team to see if they have some additional comments. once there is a reply, I will get back to you for the first time.

In addition, it is recommended to deliver your feedback on the Windows Server UserVoice. Feedback here is more timely. The product team will collect the feedback and give the solutions in time.


Thank you for your kind understanding. Hope you have a nice day.


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.


· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

We appreciate the fact that you are community support but, your ability to deliver to the product team an issue that is preventing clear understanding of the operating system and its ability to be patched properly is hindering the intended use of someone else's property (hardware not sold by Microsoft). Currently your Operating System as programmed by the Employees or Contractors of Microsoft is effectively committing tortious interference and trespass of chattel. You can inform your upper tier support chain that your customers are either going to be given the due access to the product development team (since that is the team responsible for the failures) or your customers will file valid class actions against Microsoft for tortious interference in business process and trespass to chattels claims. I suggest you apes find a way to address this and treat is as the urgent matter that it is.

0 Votes 0 ·

The fact that it's by design and doesn't fit your needs doesn't mean that it has to change. The Windows Update Agent has a file version that's reported in WSUS. If you are relying on this version information to say that the system is up to date, then you're identifying and relying on the wrong column. WSUS Automated Maintenance © has a a stream that renames the OS Description based on what the OS version is from the computer details table to make it easy, not only to identify, but be able to sort by the column in WSUS so you can easily figure out what systems are "feature upgrade"-based up to date.

Full disclosure, WSUS Automated Maintenance (WAM) © is our product.

82816-image.png


0 Votes 0 ·
image.png (9.8 KiB)

@ScottJohnston-4661
I totally understand your concern. and we're very sorry for any inconvenience that may caused. It doesn't seem like a problem and more like a new feature. I have feedback to the Product Team but i'm not sure when they will take action. In my opinion, forum team is limit to do further. I'm sorry about this.

0 Votes 0 ·