{"id":40173,"date":"2026-07-03T10:54:03","date_gmt":"2026-07-03T08:54:03","guid":{"rendered":"https:\/\/borncity.com\/win\/?p=40173"},"modified":"2026-07-03T10:54:03","modified_gmt":"2026-07-03T08:54:03","slug":"windows-server-wsus-install-and-1st-sync-fails","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2026\/07\/03\/windows-server-wsus-install-and-1st-sync-fails\/","title":{"rendered":"Windows Server: WSUS install and 1st sync fails"},"content":{"rendered":"<p><img decoding=\"async\" style=\"margin: 0px 10px 0px 0px; display: inline; float: left;\" title=\"Windows\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2021\/04\/Windows-klein.jpg\" alt=\"Windows\" width=\"200\" align=\"left\" \/>[<a href=\"https:\/\/borncity.com\/blog\/2026\/07\/03\/windows-server-wsus-installations-erst-sync-problem\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]I'm posting just a warning for Windows Server administrators using WSUS here on the blog for informational purposes, as it was recently brought to my attention by two readers. WSUS currently cannot be reinstalled on Windows Server and\/or fails during the initial synchronization. This is something administrators may encounter if they want to set up a new system with WSUS.<\/p>\n<p><!--more--><\/p>\n<h2>Two reader reports about this WSUS issue<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg08.met.vgwort.de\/na\/b11fe7a80a43497d95a5cac867ef5909\" alt=\"\" width=\"1\" height=\"1\" \/>German blog reader Marc K. contacted me by email late in the afternoon on July 2, 2026 (thanks for that) and wrote that he was \"currently in a Windows Server course and was supposed to install WSUS as a role.\" However, he said this wasn't possible because the database wouldn't allow it. The XML data doesn't seem to match. Marc sent me the following error logs by email.<\/p>\n<pre>2026-07-02 13:35:30.230 UTC\u2003\u2003Warning\u2003\u2003WsusService.21\u2003\u2003DBConnection.ExecuteCommandNoResult\u2003\u2003SqlException occurred. Number 50000 and message invalid update identity in XML for update 023FBB11-14F5-4188-9C99-3CF16AA09A79\\100\r\n2026-07-02 13:35:30.241 UTC\u2003\u2003Warning\u2003\u2003WsusService.21\u2003\u2003DBConnection.ExecuteCommandNoResult\u2003\u2003SqlException occurred. Number 50000 and message invalid update identity in XML for update 872C37AF-7303-452E-A79D-9996339EBAC7\\100\r\n2026-07-02 13:35:30.261 UTC\u2003\u2003Warning\u2003\u2003WsusService.21\u2003\u2003DBConnection.ExecuteCommandNoResult\u2003\u2003SqlException occurred. Number 50000 and message invalid update identity in XML for update EA293276-0BCD-42B0-AC26-803F002E4AAF\\100\r\n2026-07-02 13:35:30.273 UTC\u2003\u2003Warning\u2003\u2003WsusService.21\u2003\u2003DBConnection.ExecuteCommandNoResult\u2003\u2003SqlException occurred. Number 50000 and message invalid update identity in XML for update D953C4E3-4A17-4BE5-A62A-194A48FBE726\\100\r\n2026-07-02 13:35:30.288 UTC\u2003\u2003Warning\u2003\u2003WsusService.21\u2003\u2003DBConnection.ExecuteCommandNoResult\u2003\u2003SqlException occurred. Number 50000 and message invalid update identity in XML for update 3CB61571-0F24-460A-88A4-D8BA91086CEE\\100\r\n2026-07-02 13:35:30.292 UTC\u2003\u2003Warning\u2003\u2003WsusService.21\u2003\u2003DBConnection.ExecuteCommandNoResult\u2003\u2003SqlException occurred. Number 50000 and message invalid update identity in XML for update F79191BF-5F81-4B85-92E0-BBBDE6FC9479\\100\r\n2026-07-02 13:35:30.304 UTC\u2003\u2003Warning\u2003\u2003WsusService.21\u2003\u2003DBConnection.ExecuteCommandNoResult\u2003\u2003SqlException occurred. Number 50000 and message invalid update identity in XML for update F8B4C8BE-B1C0-4FCB-AE66-1AD17C467089\\100\r\n2026-07-02 13:35:30.352 UTC\u2003\u2003Warning\u2003\u2003WsusService.21\u2003\u2003DBConnection.ExecuteCommandNoResult\u2003\u2003SqlException occurred. Number 50000 and message invalid update identity in XML for update AB2221A6-5C0A-499B-ABE2-FDF428AC4DC2\\100\r\n2026-07-02 13:35:30.368 UTC\u2003\u2003Warning\u2003\u2003WsusService.21\u2003\u2003DBConnection.ExecuteCommandNoResult\u2003\u2003SqlException occurred. Number 50000 and message invalid update identity in XML for update B8468628-4D28-4A00-98E0-C32556E15332\\100<\/pre>\n<p>It seems that the issue has happened since June 15, 2026, and is mentioned at several Microsoft Q&amp;A posts.<\/p>\n<h2>\u00a0Some reports at Microsoft Q&amp;A<\/h2>\n<p>Marc pointed me to the following sources on Microsoft Q&amp;A where the issue has already been discussed:<\/p>\n<ul>\n<li><a id=\"menurdto\" class=\"fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn\" title=\"https:\/\/learn.microsoft.com\/en-us\/answers\/questions\/5920536\/wsus-initial-configuration-fails-with-sqlexception\" href=\"https:\/\/learn.microsoft.com\/en-us\/answers\/questions\/5920536\/wsus-initial-configuration-fails-with-sqlexception\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\"Link WSUS initial configuration fails with SqlException 50000 invalid update identity - Microsoft Q&amp;A\">WSUS initial configuration fails with SqlException 50000 invalid update identity<\/a><\/li>\n<li><a id=\"menurdtq\" class=\"fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn\" title=\"https:\/\/learn.microsoft.com\/en-in\/answers\/questions\/5922617\/windows-server-2025-standard-wsus-synchronisation\" href=\"https:\/\/learn.microsoft.com\/en-in\/answers\/questions\/5922617\/windows-server-2025-standard-wsus-synchronisation\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\"Link Windows Server 2025 Standard - WSUS - Synchronisation failing - Microsoft Q&amp;A\">Windows Server 2025 Standard &#8211; WSUS &#8211; Synchronisation failing<\/a><\/li>\n<li><a id=\"menurdts\" class=\"fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn\" title=\"https:\/\/learn.microsoft.com\/en-us\/answers\/questions\/5924684\/downloads-to-wsus-not-working-in-my-mecm-system-wi\" href=\"https:\/\/learn.microsoft.com\/en-us\/answers\/questions\/5924684\/downloads-to-wsus-not-working-in-my-mecm-system-wi\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\"Link Downloads to WSUS not working in my MECM system with Software Update Point - Microsoft Q&amp;A\">Downloads to WSUS not working in my MECM system with Software Update Point<\/a><\/li>\n<\/ul>\n<p>In the forum posts above, this applies to Windows Server 2022 Standard and Windows Server 2025.<\/p>\n<h2>A note from my Microsoft source<\/h2>\n<p>Just three hours earlier, I received a personal message from a Microsoft source (thanks for the info), stating that there are \"currently issues with the initial sync of newly installed WSUS servers.\" It also referred to the first Microsoft Q&amp;A forum post in the list above.<\/p>\n<p>It was noted that very little information is available so far because the problem only occurs during the first sync, and not many new WSUS servers are being set up these days. But anyone who has to perform this task will run into the problem.<\/p>\n<p>The information from my Microsoft source was that \"if the affected administrator opens a support ticket at Microsoft, they will receive a workaround that involves manually importing the catalog via a script.\" My source is currently trying to clarify internally at Microsoft whether and when a fix from Microsoft will be available. He suspects that no hotfixes will be necessary on the customer side.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]I'm posting just a warning for Windows Server administrators using WSUS here on the blog for informational purposes, as it was recently brought to my attention by two readers. WSUS currently cannot be reinstalled on Windows Server and\/or fails during &hellip; <a href=\"https:\/\/borncity.com\/win\/2026\/07\/03\/windows-server-wsus-install-and-1st-sync-fails\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,2],"tags":[47,159,569],"class_list":["post-40173","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-issue","tag-windows-server","tag-wsus"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/40173","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=40173"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/40173\/revisions"}],"predecessor-version":[{"id":40174,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/40173\/revisions\/40174"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=40173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=40173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=40173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}