# Software

*Applies to: Patch My PC Publisher*

## Operating System

WSUS support is dependent on the underlying Windows Server operating system version.

The Publisher supports WSUS when it is installed on Windows Server versions that are within Microsoft’s supported lifecycle.

The table below reflects WSUS support based on the Windows Server operating system version.

| Platform            | Core WSUS API Support | Full WSUS Server Role Support |
| ------------------- | --------------------- | ----------------------------- |
| Windows 11          | Supported             | Not Supported                 |
| Windows Server 2012 | Not Supported         | Not Supported                 |
| Windows Server 2016 | Supported             | Supported                     |
| Windows Server 2019 | Supported             | Supported                     |
| Windows Server 2022 | Supported             | Supported                     |
| Windows Server 2025 | Supported             | Supported                     |

{% hint style="warning" %}
**Important**

WSUS installed on operating systems that have reached end of support from Microsoft is not supported.

Publishing to WSUS requires a supported Windows Server operating system with the WSUS role installed. Windows 11 is supported only for standalone Intune publishing and requires the WSUS UpdateServices API provided by the RSAT WSUS tools for catalog read operations. See [Intune Software Requirements](https://docs.patchmypc.com/patch-my-pc-publisher/publisher-requirements/intune-requirements/software) for more information.
{% endhint %}

## WSUS Role

Before enabling third-party patching with the Publisher, Windows Server Update Services (WSUS) must be correctly installed and configured. In ConfigMgr environments, WSUS should already be installed as part of the initial configuration of a Software Update Point (SUP) role.

While this doc does not cover how to install WSUS, it’s important to understand what the WSUS server role installs and the supporting components it relies on, especially when preparing an environment for third-party patching with the Publisher.

{% hint style="info" %}
**Note**

For more information on how to install the WSUS role in a WSUS-standalone environment, see <https://learn.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/deploy-windows-server-update-services>

For information on how to install WSUS by way of configuring the SUP site system role in ConfigMgr, see <https://learn.microsoft.com/en-us/intune/configmgr/sum/get-started/install-a-software-update-point>
{% endhint %}

When the WSUS role is installed, either standalone or as part of a ConfigMgr SUP, it automatically deploys and configures several core components required for update publishing, synchronization, and client scanning.WSUS is installed through Server Manager and requires the following components:

* **Windows Server Update Services (WSUS)** role\
  This is the core role required to host update metadata and content.
* **RSAT Management tools**
  * Windows Server Update Services Tools
    * WSUS Management Console (MMC snap-in)
    * Supporting PowerShell and administrative components

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2F8YXaxvQnvS0X4HwXZ7Vp%2Fimage.png?alt=media&#x26;token=7fed4a00-d51d-4fa7-acc3-4a9651d1bef9" alt="WSUS Roles and Features" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/publisher-requirements/wsus-requirements/software.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.