Messages

Hi Andrew

Without log files, I'm not entire sure what is happening here.

Since you mentioned servers, I'm assuming you're deploying Patch My PC Updates through ConfigMgr. May you please gather the following logs from an affected client and send them to [email protected]

 %WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\DeltaDownload*.log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.
%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\WUAHandler*.log
%WinDir%\WindowsUpdate.log
You need to run Get-WindowsUpdateLog on Windows 8.1 and newer in PowerShell.

Thanks
Scott

Hey @Ashearera

Intune Policy runs every hour and evaluates win32apps.
when initially deployed, the updates should be installed by Intune within an hour of deployment. If the installation fails, Intune will retry the installation every 24 hours, unless the exit code is Retry.

We have a KB article on retries here - https://patchtuesday.com/blog/tech-blog/win32app-retry-interval/

[ProductLanguage=1033]

Hi Shahab

This issue is caused by the device running in a different locale than the version of Webex being installed. Webex will always try to upgrade in the device's language, even if an English version is already installed.

To resolve this, you must instruct the installation to use the English language code.

You can do this by adding "ProductLanguage=1033" to the Modify Command Line right-click option within the Patch My PC Publisher, after which you will need to republish the update/app

https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications#modify-command-line

https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications#republish-updates

Hi @itguy85

Splunk Inc still maintains Splunk 7, 8 and 9, so we list them separately in the catalogue.

We have requirement rules written for each of those Updates that ensure a Splunk 7 update will only ever apply to a device running Splunk 7, the same applies for Splunk 8 and Splunk 9.

If you want to upgrade from Splunk 7 or 8 to Splunk 9 using Software Updates, you will want to publish Splunk Latest (which is version 9 currently, as its applicability rules are different, allowing it to apply to devices running any previous version of Splunk.

We have this documented here - https://patchmypc.com/products-multiple-versions-patch-my-pc

Good morning @L.A

Our packaging team added QGIS LTR 3.28 as well as resolving the issue you were experiencing.

Hey @L.A

That page is automatically generated from the list of products in our catalogue.

We found an issue with the product for QGIS Latest, which was causing it to not display in our catalogue correctly, and in turn not display on that page correctly.

We should hopefully have the fixes in the catalogue today or tomorrow!

Hey

Thanks for pointing this out, we'll look into it today!

Scott

Hey @pmptrad

Pulse Connect Secure is 1 of the applications in our catalogue that requires a manual installer download before our Publisher can package it. You can see this in the following KB article - https://patchmypc.com/local-content-repository-for-licensed-applications-that-require-manual-download

I'm interested in the Object Reference errors you are receiving. May you please click Collect Logs in the General tab of the Patch My PC Publisher and share the resultant zipped log bundle with me at [email protected] FOA Scott?

Hey @LubosN

Can you please generate a log bundle by clicking "Collect Logs" in the General tab of the Patch My PC Publisher and send those logs over the [email protected] along with a screenshot of the Chrome apps as the exist in your Intune portal?

Hey @oletaschmeler

Are you able to elaborate on your comment? I'm unsure on the context based on the topic of this post.

Hey tei2007

We'll look to get this updated as soon as possible

[jre-8u351-windows-x64.exe]

Hey @gsterling

Apologies for the delayed response, I checked the Publisher in my lab and the file we are looking for is jre-8u351-windows-x64.exe. Are you able to test this again today to see if the issue persists?

Quick follow-up Vik, We've identified the issue and it should be resolved today!

I'll keep you updated, but once it's resolved you'll need to republish PyCharm Professional Edition for the fix to take effect

Hey Vik

Thanks for bringing this to our attention. We'll review this internally and get back to you

Hey

Can you please reach out to [email protected] with the following Client-Side log files?

• %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log (This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Company Portal.)
• %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareDetectionScript.log
• %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareUpdateDetectionScript.log
• %ProgramData%\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log
• %ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
• %ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
• %ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml

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

Additionally, a Server-Side log bundle, which can be generated by clicking the Collect Logs button in the General tab of the Patch My PC Publisher.