Patch My PC Log Reference for Specific Scenarios

Below, you will find logs needed for specific scenarios.

Server-Side Logs

Software Updates – Failing to Publish Updates Using Patch My PC’s Publisher

When using the Patch My PC Publisher to published third-party updates to WSUS, we will need the following log files from the SUP/WSUS server where the service is installed.

%PatchMyPCInstallDirectory%PatchMyPC.log
%PatchMyPCInstallDirectory%PatchMyPC.lo_
%PatchMyPCInstallDirectory%Settings.xml
%PatchMyPCInstallDirectory%PatchMyPC-DownloadHistory.csv
%PatchMyPCInstallDirectory%PatchMyPC-PublishingHistory.csv
%SiteServerLogsFolder%wsyncmgr*.log
%SiteServerLogsFolder%WCM*.log

The following log may be needed upon request only due to large file size

%ProgramFiles%Update ServicesLogFilesSoftwareDistribution.log

Software Updates – Failing to Publish Updates Using SCCM In-Console Publishing

When using the SCCM in-console publishing, we will need the following log files from the SUP/WSUS server where the service is installed.

%SiteSystemLogsFolder%SMS_ISVUPDATES_SYNCAGENT*.log
%SiteServerLogsFolder%wsyncmgr*.log
%SiteServerLogsFolder%WCM*.log

The following log file may be needed upon request only due to large file size

%ProgramFiles%Update ServicesLogFilesSoftwareDistribution.log

SCCM Applications – Failing to Create/Update SCCM Applications Using Patch My PC’s Publisher

When using the Patch My PC Publisher for SCCM application creation, we will need the following log files to troubleshoot applications failing to create.

%PatchMyPCInstallDirectory%PatchMyPC.log
%PatchMyPCInstallDirectory%PatchMyPC.lo_
%PatchMyPCInstallDirectory%Settings.xml
%PatchMyPCInstallDirectory%PatchMyPC-DownloadHistory.csv
%PatchMyPCInstallDirectory%PatchMyPC-PublishingHistory.csv
%SCCMInstallFolder%LogsSMSProv*.log

Intune Applications – Fails to Create/Update Applications Using Patch My PC’s Publisher

When using the Patch My PC Publisher for Intune application creation, we will need the following log files to troubleshoot applications failing to create.

%PatchMyPCInstallDirectory%PatchMyPC.log
%PatchMyPCInstallDirectory%PatchMyPC.lo_
%PatchMyPCInstallDirectory%Settings.xml
%PatchMyPCInstallDirectory%PatchMyPC-DownloadHistory.csv
%PatchMyPCInstallDirectory%PatchMyPC-PublishingHistory.csv

Client-Side Logs

Intune Applications/Updates Failing to Install on Client Devices

When troubleshooting Intune application installation errors on a client, we will need multiple client logs. Please include the following logs:

%ProgramData%PatchMyPCIntuneLogsPatchMyPC-ScriptRunner.log
%ProgramData%PatchMyPCIntuneLogsPatchMyPC-SoftwareDetectionScript.log
%ProgramData%PatchMyPCIntuneLogsPatchMyPC-SoftwareUpdateDetectionScript.log

**Important**

For user-based apps, the logs mentioned above will reside in the following folders:

* %LocalAppData%PatchMyPCIntuneLogsPatchMyPC-Scriptrunner.log

* %Temp%PatchMyPC-SoftwareDetectionScript.log

* %Temp%PatchMyPC-SoftwareUpdateDetectionScript.log

%ProgramData%MicrosoftIntuneManagementExtensionLogsAgentExecutor.log
%ProgramData%MicrosoftIntuneManagementExtensionLogsIntuneManagementExtension.log
%ProgramData%MicrosoftIntuneManagementExtensionLogsWin32AppInventory.log
%ProgramData%MicrosoftIntuneManagementExtensionLogsAppWorkload.log

**Note**

Some Patch My PC log files listed above may be found in **%WinDir%CCM** folder if that folder exists.

SCCM Applications Failing to Install on Client Devices

When troubleshooting SCCM application installation errors on a client, we will need multiple client logs. Please include the following logs:

%WinDir%CCMLogsAppDiscovery*.log
%WinDir%CCMLogsAppEnforce*.log
%WinDir%CCMLogsAppIntentEval*.log
%WinDir%CCMLogsCAS*.log
%WinDir%CCMLogsCIAgent.*log
%WinDir%CCMLogsDataTransferService*.log
%WinDir%CCMLogsPatchMyPC-ScriptRunner.log
%WinDir%CCMLogsPatchMyPC-SoftwareDetectionScript.log
%WinDir%CCMLogsStateMessage.log

Third-Party Software Updates Failing to Install on Client Devices

When troubleshooting update installation errors on a client, we will need the following client logs:

%WinDir%CCMLogsCAS*.log
%WinDir%CCMLogsDeltaDownload*.log
%WinDir%CCMLogsScanAgent*.log
%WinDir%CCMLogsStateMessage.log
%WinDir%CCMLogsUpdatesDeployment*.log
%WinDir%CCMLogsUpdatesHandler*.log
%WinDir%CCMLogsUpdatesStore*.log
%WinDir%CCMLogsDataTransferService*.log
%WinDir%CCMLogsWUAHandler*.log
%WinDir%CCMLogsPatchMyPC-ScriptRunner.log (If exist)
%WinDir%WindowsUpdate.log

Download Stuck at 0% / Waiting to install / Preparing to download

When troubleshooting update installation errors on a client, we will need the following client logs:

%WinDir%CCMLogsCAS*.log
%WinDir%CCMLogsCIAgent.*log
%WinDir%CCMLogsClientLocation*.log
%WinDir%CCMLogsCMBITSManager*.log
%WinDir%CCMLogsContentTransferManager*.log
%WinDir%CCMLogsDataTransferService*.log
%WinDir%CCMLogsLocationServices.log*.log
%WinDir%CCMLogsStateMessage.log
%WinDir%CCMLogsUpdatesDeployment*.log
%WinDir%CCMLogsUpdatesHandler*.log
%WinDir%CCMLogsUpdatesStore*.log
%WinDir%CCMLogsPatchMyPC-ScriptRunner.log (If exist)

Configuration Manager Specific Logs

Automatic Deployment Rule Failing for Third-Party Updates

When troubleshooting automatic deployment rules failing for third-party updates, we will need the following server-side logs. In this example, we will assume the main SCCM installation directory is: C:Program FilesMicrosoft Configuration Manager

  • C:Program FilesMicrosoft Configuration ManagerLogsruleengine*.log
  • The PatchDownloader.log (Location may vary)
    • C:Program FilesSMS_CCMLogsPatchDownloader*.log (Most common location)
    • C:Program FilesMicrosoft Configuration ManagerLogsPatchDownloader*.log (Possible location)
    • %WinDir%CCMLogs (Possible location)
    • If unable to locate a current PatchDownloader.log, check HKLMSOFTWAREMicrosoftCCMLogging@Global:LogDirectory on the site server
how to locate the patchdownloader.log file
how to locate the patchdownloader.log file

Updates Failing to Download to Deployment Package using SCCM Console

When troubleshooting updates failing to download into a deployment package from the SCCM console, we will need the following log from the machine running the SCCM console:

%temp%PatchDownloader*.log

**Note**

If you are using an RDP session, the **patchdownloader.log** may be in a numbered sub-folder in your **Users** **%temp%** folder.

Patch My PC Publisher – How to Enable Debug Logging

Enabling Debug logging is often helpful for troubleshooting unique issues with publishing. Follow the steps below to enable Debug logging:

  1. Open the Publisher
  2. Click on the General tab
  3. In the dropdown under Logging Options select Debug
    Enable Debug Logging in Publisher
    Enable Debug Logging in Publisher
  4. Close the Publisher
  5. Open Services.msc and locate the PatchMyPCService
  6. Right-click and Restart the PatchMyPCService
  7. Debug Logging is now enabled

List of Specific Patch My PC Logs and Files

PatchMyPC.log

PatchMyPC.log is the primary log file for the Publisher and is often required by support for any troubleshooting. The file name and location are:

%PatchMyPCInstallDirectory%PatchMyPC.log
%PatchMyPCInstallDirectory%PatchMyPC.lo_

Settings.xml

Settings.xml stores all settings related to the Publisher. This file is also used for Backup and Restore. The file name and location are:

%PatchMyPCInstallDirectory%Settings.xml