Hey James,
Thanks for reaching out to support!
That is expected behavior as all content deployed from SCCM is downloaded to the local cache (CCMCache). Updates are then copied over to the SoftwareDistribution folders since that's what the WUA uses to process the updates. Products that do not have any right-click options enabled on them from the PMPC Publisher, will not output logging info in the scriptrunner.log
It's possible, content was cleared out in the CCMCache for those updates but left over in the SoftwareDistribution folder.
We can also look at the following ConfigMgr logs (like CAS.log which will show you if ConfigMgr downloaded the file and WIndowsUpdate.log (which will show you if the WUA downloaded the file).
https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#update-troubleshooting-client-logs:~:text=Third%2DParty%20Software%20Updates%20Failing%20to%20Install%20on%20Client%20Devices
I also came across this post from Jason Sandies indicating the same behavior:
https://techcommunity.microsoft.com/t5/windows-servicing/location-of-windows-updates-download-with-configmgr/m-p/2144311
Thanks for reaching out to support!
That is expected behavior as all content deployed from SCCM is downloaded to the local cache (CCMCache). Updates are then copied over to the SoftwareDistribution folders since that's what the WUA uses to process the updates. Products that do not have any right-click options enabled on them from the PMPC Publisher, will not output logging info in the scriptrunner.log
It's possible, content was cleared out in the CCMCache for those updates but left over in the SoftwareDistribution folder.
We can also look at the following ConfigMgr logs (like CAS.log which will show you if ConfigMgr downloaded the file and WIndowsUpdate.log (which will show you if the WUA downloaded the file).
https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#update-troubleshooting-client-logs:~:text=Third%2DParty%20Software%20Updates%20Failing%20to%20Install%20on%20Client%20Devices
I also came across this post from Jason Sandies indicating the same behavior:
https://techcommunity.microsoft.com/t5/windows-servicing/location-of-windows-updates-download-with-configmgr/m-p/2144311