Log Reference Guide
Below, you will find logs needed for specific scenarios.
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 file may be needed upon request only due to large file size
%ProgramFiles%\Update Services\LogFiles\SoftwareDistribution.log
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 Services\LogFiles\SoftwareDistribution.log
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%\Logs\SMSProv*.log
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
When troubleshooting Intune application installation errors on a client, we will need multiple client logs. Please include the following logs:
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareDetectionScript.log
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareUpdateDetectionScript.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
Note: Some Patch My PC log files listed above may be found in %WinDir%\CCM folder if that folder exists.
When troubleshooting SCCM application installation errors on a client, we will need multiple client logs. Please include the following logs:
%WinDir%\CCM\Logs\AppDiscovery*.log
%WinDir%\CCM\Logs\AppEnforce*.log
%WinDir%\CCM\Logs\AppIntentEval*.log
%WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\CIAgent.*log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log
%WinDir%\CCM\Logs\PatchMyPC-SoftwareDetectionScript.log
%WinDir%\CCM\Logs\StateMessage.log
When troubleshooting update installation errors on a client, we will need the following client logs:
%WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\DeltaDownload*.log
%WinDir%\CCM\Logs\ScanAgent*.log
%WinDir%\CCM\Logs\StateMessage.log
%WinDir%\CCM\Logs\UpdatesDeployment*.log
%WinDir%\CCM\Logs\UpdatesHandler*.log
%WinDir%\CCM\Logs\UpdatesStore*.log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\WUAHandler*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
%WinDir%\WindowsUpdate.log
You need to run Get-WindowsUpdateLog on Windows 8.1 and newer in PowerShell.
When troubleshooting update installation errors on a client, we will need the following client logs:
%WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\CIAgent.*log
%WinDir%\CCM\Logs\ClientLocation*.log
%WinDir%\CCM\Logs\CMBITSManager*.log
%WinDir%\CCM\Logs\ContentTransferManager*.log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\LocationServices.log*.log
%WinDir%\CCM\Logs\StateMessage.log
%WinDir%\CCM\Logs\UpdatesDeployment*.log
%WinDir%\CCM\Logs\UpdatesHandler*.log
%WinDir%\CCM\Logs\UpdatesStore*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
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 Files\Microsoft Configuration Manager
C:\Program Files\Microsoft Configuration Manager\Logs\ruleengine*.log
The PatchDownloader.log (Location may vary)
C:\Program Files\SMS_CCM\Logs\PatchDownloader*.log (Most common location)
C:\Program Files\Microsoft Configuration Manager\Logs\PatchDownloader*.log (Possible location)
%WinDir%\CCM\Logs (Possible location)
If unable to locate a current PatchDownloader.log, check HKLM\SOFTWARE\Microsoft\CCM\Logging\@Global:LogDirectory on the site server
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.
Enabling Debug logging is often helpful for troubleshooting unique issues with publishing. Follow the steps below to enable Debug logging:
Open the Publisher
Click on the General tab
In the dropdown under Logging Options select Debug
Close the Publisher
Open Services.msc and locate the PatchMyPCService
Right-click and Restart the PatchMyPCService
Debug Logging is now enabled
%PatchMyPCInstallDirectory%\PatchMyPC.log
%PatchMyPCInstallDirectory%\PatchMyPC.lo_
PatchMyPC.log is the primary log file for the Publisher and is often required by support for any troubleshooting.
%PatchMyPCInstallDirectory%\Settings.xml
Settings.xml stores all settings related to the Publisher. This file is also used for Backup and Restore.
