{"id":39270,"date":"2025-09-12T00:01:21","date_gmt":"2025-09-11T22:01:21","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=39270"},"modified":"2025-09-11T22:43:10","modified_gmt":"2025-09-11T20:43:10","slug":"windows-11-24h2-windows-server-2025-is-not-receiving-updates-from-wsus","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2025\/09\/12\/windows-11-24h2-windows-server-2025-is-not-receiving-updates-from-wsus\/","title":{"rendered":"Windows 11 24H2\/Windows Server 2025 is not receiving updates from WSUS"},"content":{"rendered":"<p><img decoding=\"async\" style=\"margin: 0px 10px 0px 0px; display: inline; float: left;\" title=\"Windows\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2021\/04\/Windows-klein.jpg\" alt=\"Windows\" width=\"200\" align=\"left\" \/>[<a href=\"https:\/\/www.borncity.com\/blog\/2025\/09\/11\/wsus-erkennt-updates-fuer-windows-server-2025-nicht\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]I'm posting a problem on the blog that was brought to my attention by a reader. It concerns WSUS (Windows Services Update Server), which is also to be used for update management for Windows Server 2025. An administrator contacted me because WSUS does not recognize updates for Windows Server 2025. The problem may also affect Windows 11 clients.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg04.met.vgwort.de\/na\/6840a84bc60142cc9dda1ea22fec61be\" alt=\"\" width=\"1\" height=\"1\" \/>Microsoft is no longer developing WSUS, as I reported in the blog post <a href=\"https:\/\/borncity.com\/win\/2024\/09\/22\/microsoft-discontinues-wsus-development\/\" rel=\"bookmark\">Microsoft discontinues WSUS development<\/a>. In response to a reader's question in my German blog: \"What solution do you use to distribute Windows updates when WSUS is discontinued?\", German blog reader Bernie replied. He pointed out that although Microsoft is no longer developing WSUS, the WSUS server role will still be available in Windows Server 2025 (end of support 11\/14\/2034) (<a href=\"https:\/\/www.windowspro.de\/news\/microsoft-mustert-wsus-aus-deprecated-ist-server-2025-aber-noch-enthalten\/05761.html\" target=\"_blank\" rel=\"noopener\">see<\/a>). WSUS should therefore still be available with Windows Server 2025.<\/p>\n<h2>Windows Server 2025 stuck with\u00a0Updates from WSUS<\/h2>\n<p>A blog reader who works as an administrator at a company I know has just contacted me by email because he has run into problems with WSUS.<\/p>\n<ul>\n<li>The blog reader runs Windows Server 2022 (Build 20348.4052), which, according to him, is running the latest SSU and CU and has the WSUS role installed.<\/li>\n<li>All Windows Server 2025 instances on the network are correctly recognized by WSUS and listed as \"Windows Server 2025 Standard.\"<\/li>\n<li>The reader has approved the corresponding updates for \"Microsoft Server Operating System Version 24H2.\"<\/li>\n<li>Nevertheless, the new updates cannot be found on the Windows Server 2025 instances.<\/li>\n<\/ul>\n<p>The reader has already verified that the Windows Server 2025 instances appear in WSUS and that the approvals are set correctly. This can therefore be ruled out as the reason why the instances are not receiving the updates.<\/p>\n<p><a href=\"https:\/\/i.postimg.cc\/rF6xnZrS\/image.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone\" title=\"Windows Server 2025 Update registry entries\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2025\/09\/image.png\" alt=\"Windows Server 2025 Update registry entries\" width=\"640\" height=\"434\" \/><\/a><br \/>\n<em>Windows Server 2025 Update registry entries<\/em><\/p>\n<p>When analyzing the Windows Server 2025 instances, the reader noticed that Windows Server 2025 uses new registry entries related to update control (e.g., <em>DeferFeatureUpdate,<\/em> see screenshot above). These entries were unsuccessfully set in the registry 0.<\/p>\n<p><a href=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2025\/09\/image-1.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone\" title=\"Windows Server 2022 Update registry entries\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2025\/09\/image-1.png\" alt=\"Windows Server 2022 Update registry entries\" width=\"640\" height=\"414\" \/><\/a><br \/>\n<em>Windows Server 2022 Update registry entries<\/em><\/p>\n<p>Windows Server 2022 and Windows Server 2019 are working fine and receiving updates from WSUS. The reader wrote: \"I'm slowly becoming unsure whether this is a general problem or whether I'm overlooking a step. Do you have any experience with this, or is this kind of behavior already known to occur with Windows Server 2025?\"<\/p>\n<p>I haven't heard anything about this yet. Does anyone know anything about this? But it wasn't an isolated case &#8211; other German blog readers confirmed this issue &#8211; also for Windows 11 24H2 client. And two readers came out with a suggestion for a solution.<\/p>\n<h2>Registry entries cause conflicts<\/h2>\n<p>Once again, the collective knowledge of my German readers has led to a solution. If anyone is affected by this problem, read Willi K.'s <a href=\"https:\/\/www.borncity.com\/blog\/2025\/09\/11\/wsus-erkennt-updates-fuer-windows-server-2025-nicht\/#comment-229759\" target=\"_blank\" rel=\"noopener\">German comment<\/a>. Then open the article <a href=\"https:\/\/patchmypc.com\/blog\/sccm-co-management-dual-scan\" target=\"_blank\" rel=\"noopener\">SCCM Co-management \u2013 Dual Scan and Scan Source Demystified<\/a> linked <a href=\"https:\/\/borncity.com\/win\/2025\/09\/10\/patchday-windows-10-11-updates-september-9-2025\/\" target=\"_blank\" rel=\"noopener\">here <\/a>by German blog reader Klaus2, and take note of the information in the section \"Co-management not configured for a device.\"<\/p>\n<p><a href=\"https:\/\/patchmypc.com\/app\/uploads\/2025\/04\/20.png.webp\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/patchmypc.com\/app\/uploads\/2025\/04\/20.png.webp\" alt=\"Registry-Entries\" width=\"640\" height=\"316\" \/><\/a><br \/>\nCo-management not configured for a device; <a href=\"https:\/\/patchmypc.com\/blog\/sccm-co-management-dual-scan\" target=\"_blank\" rel=\"noopener\">Quelle<\/a><\/p>\n<p>With the registry settings fixed, the issue should be solved. As Klaus2 notes in his comment, the problem may affect Windows 11 24H2 as well as Windows Server 2025. Thank you to our readers for their contributions, which helped those affected by the patch.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]I'm posting a problem on the blog that was brought to my attention by a reader. It concerns WSUS (Windows Services Update Server), which is also to be used for update management for Windows Server 2025. An administrator contacted me &hellip; <a href=\"https:\/\/borncity.com\/win\/2025\/09\/12\/windows-11-24h2-windows-server-2025-is-not-receiving-updates-from-wsus\/\">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,22],"tags":[47,195,2860,2845,569],"class_list":["post-39270","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","tag-issue","tag-update","tag-windows-11-24h2","tag-windows-server-2025","tag-wsus"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/39270","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=39270"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/39270\/revisions"}],"predecessor-version":[{"id":39275,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/39270\/revisions\/39275"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=39270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=39270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=39270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}