> 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/customizations/list-customizations/manage-logging.md).

# Manage Logging option in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*\
*Available at level: All Custom Products, All Products, Vendor, Product*\
*Available on tab: WSUS Updates, ConfigMgr Apps, Intune Apps, Intune Updates*

The **Manage Logging** right-click option in Patch My PC (PMPC) Publisher enables *additional* client-side logging during product installation to help troubleshoot failures or unexpected behavior.

When enabled, Publisher configures the installer to generate a Patch My PC installation log and, when supported, the vendor’s native installation log. These logs are created during product installation on the client device and can be collected for diagnostic purposes.

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

Some vendor installers can generate their own installation logs, most commonly MSI-based installers. The **Manage Logging** option allows Patch My PC ScriptRunner (which manages the installation) to pass the appropriate logging parameters to the installer so that additional vendor-specific logs are created. These logs are useful for client-side troubleshooting when an installation fails.

This option only affects vendor logging behavior. The Patch My PC ScriptRunner logs are created regardless of whether this option is enabled.

More information on log files and locations can be found in the [Log File Reference](https://docs.patchmypc.com/patch-my-pc-publisher/technical-references/log-file-reference.md).
{% endhint %}

## Logging Options

The **Logging Options** dialog provides the following options.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FzJLfdnjSMbxNpPKjavDw%2Fimage.png?alt=media&amp;token=0ea10792-dfbc-46e4-8780-8ee71acb1499" alt="&#x27;Logging Options&#x27; dialog" width="450"><figcaption></figcaption></figure>

### **Enable logging**

Controls whether logging is enabled.

### **Log folder path**

Specifies where client-side installation logs are written. The default location depends on the product installation scenario:

* Products installed from **ConfigMgr and WSUS** store logs in `C:\Windows\CCM\Logs\PatchMyPCInstallLogs`
* Products installed from **Intune** store logs in `%ProgramData%\PatchMyPCInstallLogs`

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

User-based installations write logs to folders within the user profile. See the [Log File Reference](https://docs.patchmypc.com/patch-my-pc-publisher/technical-references/log-file-reference.md) for more information on log files and their locations.
{% endhint %}

### **Enable verbose logging for MSI installation**

Enables verbose logging for MSI-based installers that support this mode to capture additional detail.

### **Prefix the log with the computer name**

Adds the device name to the beginning of the log file name to simplify identification when collecting logs from multiple devices.

### **In case of installation failure, copy the log file to this secondary folder**

Creates a second copy of the installation log when the product fails to install and writes it to the specified path. The device must be able to access this location at install time and have permission to write to it. If the path is an SMB share, the installation context must have write access.

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

Separate log files are created for installs and uninstalls, named after the software title and version. If a log file with the same name already exists, the newer version will be appended with  **\_01**, **\_02**, **\_03**, etc. at the end of the file name.

For example:

* **7z2601-x64.msi.log**
* **7z2601-x64.msi\_01.log**
  {% endhint %}


---

# 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/customizations/list-customizations/manage-logging.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.
