[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 because WSUS does not recognize updates for Windows Server 2025. The problem may also affect Windows 11 clients.
Microsoft is no longer developing WSUS, as I reported in the blog post Microsoft discontinues WSUS development. 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) (see). WSUS should therefore still be available with Windows Server 2025.
Windows Server 2025 stuck with Updates from WSUS
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.
- 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.
- All Windows Server 2025 instances on the network are correctly recognized by WSUS and listed as "Windows Server 2025 Standard."
- The reader has approved the corresponding updates for "Microsoft Server Operating System Version 24H2."
- Nevertheless, the new updates cannot be found on the Windows Server 2025 instances.
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.
Windows Server 2025 Update registry entries
When analyzing the Windows Server 2025 instances, the reader noticed that Windows Server 2025 uses new registry entries related to update control (e.g., DeferFeatureUpdate, see screenshot above). These entries were unsuccessfully set in the registry 0.
Windows Server 2022 Update registry entries
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?"
I haven't heard anything about this yet. Does anyone know anything about this? But it wasn't an isolated case – other German blog readers confirmed this issue – also for Windows 11 24H2 client. And two readers came out with a suggestion for a solution.
Registry entries cause conflicts
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 German comment. Then open the article SCCM Co-management – Dual Scan and Scan Source Demystified linked here by German blog reader Klaus2, and take note of the information in the section "Co-management not configured for a device."
Co-management not configured for a device; Quelle
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.
KB5064401, the Cumulative Update for .NET Framework for Windows Server 2025, was not found on a Windows Server 2022 WSUS. After manual installation however, on the WSUS Server it was shown as "Installed".
KB5065426, the Cumulative Update for Windows Server 2025, was found and installed without any issues so far, from the very same Windows Server 2022 WSUS.
Think a German user mentioned a similar thing – the update was delivered later.