> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/manage/advanced-tab/technical-references/about-staged-content-repository.md).

# About the Staged Content Repository in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

The **Staged Content Reposito**ry is commonly used for licensed or restricted applications where Publisher cannot automatically download installer binaries. In these scenarios, administrators must manually obtain the installer files and place them into the repository so Publisher can consume them during publishing.

Common reasons include:

* The software vendor uses a paywalled portal that requires authentication to download installers.
* The vendor provides the installer in a file format that is not compatible with Publisher's download or extraction process.
* Legal, licensing, or EULA restrictions prohibit automated downloads by third-party tools.
* The vendor enforces technical controls on their website that block automated or scripted downloads.
* Organizational security policies restrict access to specific vendor sites or CDNs from the Publisher server.

To work around these limitations, administrators can download the required installer binaries from a separate machine with appropriate access and place them into the Staged Content Repository.&#x20;

During publishing, Publisher uses the locally staged files instead of attempting to download content directly from the vendor.

This approach ensures publishing can continue reliably while remaining compliant with vendor and organizational constraints.

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

See [Local Content Repository for Licensed Applications that Require Manual Download](https://patchmypc.com/kb/local-content-repository-licensed-applications/) for a list of applications that require manual downloads and detailed guidance.
{% endhint %}

## How the Staged Content Repository Works

Products requiring manual download (often referred to as *binary-free*) are identified in the Product Tree by a manual download icon (![Manual download icon](https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FfhQRqFW2pmD0W5IURGIH%2Fimage.png?alt=media\&token=2a82920c-0a34-4228-bf80-e950f70a2e5d)) on the following tabs:

* **WSUS Updates**
* **ConfigMgr Apps**
* **Intune Apps**
* **Intune Updates**

When this icon is present, Publisher will search the configured Staged Content Repository path for the required installer during publishing.

## Folder Structure in the Staged Content Repository

The folder structure within the Staged Content Repository is flexible and does not need to follow a specific layout. Publisher recursively searches all subfolders when locating installer content.

When evaluating files in the repository, Publisher validates only:

* The installer file name.
* The file hash matching the Patch My PC catalog.

The physical folder location of the file is not considered.

Some software vendors reuse the same installer file name across multiple versions. In these cases, administrators may want to keep older binaries for manual rollback, auditing, or troubleshooting purposes.

To support this, you can organize the repository using versioned subfolders, such as:

* Product name
* Product version

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FmYYaN77xcsminK0w2rFy%2Fimage.png?alt=media&amp;token=a033e983-27f7-45e4-bacc-94b2d383b0c8" alt="Example Local Content Repository Folder Layout" width="563"><figcaption></figcaption></figure>

This structure is fully supported and does not affect publishing, as long as the correct installer file exists somewhere in the repository and matches the expected file name and hash.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/manage/advanced-tab/technical-references/about-staged-content-repository.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
