{"id":249885,"date":"2021-02-22T00:13:00","date_gmt":"2021-02-21T23:13:00","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=249885"},"modified":"2024-02-11T18:59:44","modified_gmt":"2024-02-11T17:59:44","slug":"windows-10-v1909-wsus-bug-verhindert-eine-korrekte-anzeige-der-build-nummer","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2021\/02\/22\/windows-10-v1909-wsus-bug-verhindert-eine-korrekte-anzeige-der-build-nummer\/","title":{"rendered":"Windows 10 V1909: WSUS-Bug verhindert eine korrekte Anzeige der Build-Nummer"},"content":{"rendered":"

[English<\/a>]Der Windows Server Update Services (WSUS) hat Probleme, die korrekten Build-Nummern bei Windows 10 Version 1909 zu erkennen. Wegen eines Bugs wird eine falsche Build-Nummer zur\u00fcckgeliefert.<\/p>\n

<\/p>\n

\"\"Die Information steckt bereits einige Tage in meinem Posteingang. Blog-Leser Karl hat das Ganze auf Patchmanagement geteilt, mich aber auf CC gesetzt und schreibt:<\/p>\n

please RT \/ Share and upvote this so this gets more attention, no matter if you use WSUS or not.<\/b><\/p>\n

It is not responsible to leave customers down with this strategy. WSUS very apparently is a \"do not touch\" or least effort zone for MS and they try to promote WuFB \"instead\".<\/p>\n

Problem: 1903 \/ 1909 \/ 2004 \/ 20H2 and soon 21H1 will report wrong client OS identification strings in WSUS. This makes reporting near impossible with the default reports and GUI views.<\/p>\n

What makes me upset is that MSFT has invented a really good achievement with enablement updates and same updates for the core OS but refuse to address a WSUS database logic.<\/p>\n

With this in mind I completely understand why there is no separate product category for 1903 and later (1903\/1909) and another one for 2004 and later (2004\/20H2)<\/p>\n

They basically planned this welcomed change without executing for WSUS.<\/p>\n

If MS is okay that people need to buy a 3rd<\/sup> party script to fix this (AJtek WAM) and telling at the same time this is \"by design\" then I suppose their design is not okay.<\/p>\n

If Adam Marshall is able to fix this, Microsoft should be the first instance to address this natively.<\/p>\n

Changes to improve security for Windows devices scanning WSUS – Microsoft Tech Community<\/a><\/p>\n

I have listed 4 seperate uservoices all chiming for a change with each 30+ upvotes which is \"a lot\" compared in this uservoice area category.<\/p>\n

Thanks for your help and upvotes on the linked uservoice items and your time. It helps much use twitter tagging @windowsupdate and express your feedback on this.<\/p><\/blockquote>\n

Das Ganze ist hier als Uservoice<\/a> zu finden, wird aber initial bereits im November 2020 in diesem Technet-Thread<\/a> genauer beschrieben.\u00a0 Weil Windows 10 Version 1903 und 1909 die gleiche Codebasis verwenden, erhalten diese auch die gleichen Updates. Die Buildnummern unterscheiden sich nur in einer Ziffer – und auf Grund eines Bugs erkennt der WSUS dies nicht. Im konkreten Fall schreibt der Nutzer:<\/p>\n

I'm running WSUS (standalone) on Server 2019.\u00a0 All of our pilot machines on Windows 10 1909 are reporting to WSUS with build numbers of 18362 (1903) instead of 18363 (1909).<\/p>\n

I understand that 1903\/1909 share the same baseline and that the difference between them is basically a feature enablement package, but the different build numbers still need to be properly reported in WSUS. Otherwise, a whole bunch of reporting that I do just goes out the window.<\/p><\/blockquote>\n

Der WSUS meldet also immer die Fr\u00fchjahrsbuild einer Windows 10-Version, auch wenn das Herbst-Update installiert ist. Inzwischen wird das Ganze auch f\u00fcr Windows 10 Version 2004 und 20H2 best\u00e4tigt. Karl bittet, dass die Leser diesen Bug auf UserVoice hochvoten und Druck auf Microsoft aus\u00fcben, damit das Ganze behoben wird. Oder ist das Ganze schon korrigiert? Denn Microsoft hat am 7. Februar 2021 angemerkt, dass man das Problem ansehen will.<\/p>\n","protected":false},"excerpt":{"rendered":"

[English]Der Windows Server Update Services (WSUS) hat Probleme, die korrekten Build-Nummern bei Windows 10 Version 1909 zu erkennen. Wegen eines Bugs wird eine falsche Build-Nummer zur\u00fcckgeliefert.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7459,3694],"tags":[4378,881],"class_list":["post-249885","post","type-post","status-publish","format-standard","hentry","category-software","category-windows-10","tag-windows-10","tag-wsus"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/249885","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=249885"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/249885\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=249885"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=249885"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=249885"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}