- Welcome to Support Forum: Get Support for Patch My PC Products and Services.
Patch My PC Support
Recent posts
#31
Home Updater: General Discussions, Questions and Updates / Changes to App Library
Last post by dking02 - June 30, 2026, 02:12:14 AMA release of 22 new apps, 4 deleted apps, and 2 replaced apps was made to the Home Updater App Library on Sunday, 28 Jun 2026, increasing the total number of apps in the library from 536 which it had been at since Dec 2025 to 554. I had noticed the app count increase; however, no public announcement or release note was issued to the user community for this significant change/accomplishment. I have commented on the lack of such announcements in the past.
Attached is a 2-page PDF which I prepared which identifies the affected apps by name, type (non-portable or portable), and category. Note that it is impossible for a user to identify what has changed unless he has captured the configuration of the library before the change. This also requires some manual effort because some data (e.g., category) is not exportable from the Home Updater.
--
P.S. Many of the apps added in this release were in response to user requests (aka "ideas") for particular apps to be added to the library – see list below. While skimming through the titles of open app requests, I noticed that these requests included a reply that the app is now in the library, but the request had been left in the "SUBMITTED" status where it is still available for voting or comment and must be individually opened to determine its status. The status of such requests should be changed to "SHIPPED" which will remove the request from the backlog of open requests and conveniently consolidate all implemented requests under "SHIPPED" status. I also noticed this problem of requests being left in a "SUBMITTED" status seems to other app requests which have been implemented in earlier releases. Therefore, the entire list of open app requests should be reviewed and status changed to reflect "SHIPPED" where applicable.
* List of affected app requests: PATCHMYPC-I-5342, 5764, 5892, 6096, 6309, 6338, 6495, 6621, 6788, 7185, 7341, 8252.
Attached is a 2-page PDF which I prepared which identifies the affected apps by name, type (non-portable or portable), and category. Note that it is impossible for a user to identify what has changed unless he has captured the configuration of the library before the change. This also requires some manual effort because some data (e.g., category) is not exportable from the Home Updater.
--
P.S. Many of the apps added in this release were in response to user requests (aka "ideas") for particular apps to be added to the library – see list below. While skimming through the titles of open app requests, I noticed that these requests included a reply that the app is now in the library, but the request had been left in the "SUBMITTED" status where it is still available for voting or comment and must be individually opened to determine its status. The status of such requests should be changed to "SHIPPED" which will remove the request from the backlog of open requests and conveniently consolidate all implemented requests under "SHIPPED" status. I also noticed this problem of requests being left in a "SUBMITTED" status seems to other app requests which have been implemented in earlier releases. Therefore, the entire list of open app requests should be reviewed and status changed to reflect "SHIPPED" where applicable.
* List of affected app requests: PATCHMYPC-I-5342, 5764, 5892, 6096, 6309, 6338, 6495, 6621, 6788, 7185, 7341, 8252.
#32
Home Updater: Report Bugs and Issues Not Related to Installing Apps / PortableApps directory setting...
Last post by tavernhell - June 30, 2026, 01:42:27 AMHello, in the app settings I set the Portables Location setting to "C:\PortableApps", however when I install a portable app it gets DLed to the Desktop. Current version: 5.4.4.0
Attaching the GIF and diagnostics zip
Attaching the GIF and diagnostics zip
#33
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: WebEx Meetings User Instal...
Last post by Andrew Jimenez (Patch My PC) - June 26, 2026, 02:27:47 PMUnfortunately, the Webex user install will still register itself in HKLM when installed as system. We do have a workaround, and it is similar to what you suggested. We have a pre-install script that uses PSADT to uninstall the user-based versions.
https://github.com/PatchMyPCTeam/Community-Scripts/tree/main/Install/Pre-Install/Remove-WebexSystemUser
https://github.com/PatchMyPCTeam/Community-Scripts/tree/main/Install/Pre-Install/Remove-WebexSystemUser
#34
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / WebEx Meetings User Installs
Last post by DanERM - June 26, 2026, 11:01:04 AMWe have updates for Webex Meetings pushed to all devices, so I was surprised to get a ping from our Security Team because we have a significant number of vulnerable devices flagged in Microsoft Defender for Endpoint.
After digging into it, I can see that all of the impacted PCs have Webex Meetings installed under a user profile rather than as a system-wide installation. The uninstall information is stored under `HKEY_USERS\<User>\Software\Microsoft\Windows\CurrentVersion\Uninstall\ActiveTouchMeetingClient`, and I've yet to find any affected devices where it's installed under HKLM.
I can also see that the PMPC Webex Meetings updates are configured to install in the **System** context in the Portal, and there doesn't appear to be a **User** option.
Has anyone come across this before, or have any suggestions on the best way to deal with it?
One thing I considered was deploying the latest version to these devices and using `Uninstall-Software.ps1` as a pre-install script. However, from reviewing the script it looks like you can search HKCU, but surely that won't work when Intune runs it as **SYSTEM**, as the current user would be SYSTEM rather than the affected user profile?
After digging into it, I can see that all of the impacted PCs have Webex Meetings installed under a user profile rather than as a system-wide installation. The uninstall information is stored under `HKEY_USERS\<User>\Software\Microsoft\Windows\CurrentVersion\Uninstall\ActiveTouchMeetingClient`, and I've yet to find any affected devices where it's installed under HKLM.
I can also see that the PMPC Webex Meetings updates are configured to install in the **System** context in the Portal, and there doesn't appear to be a **User** option.
Has anyone come across this before, or have any suggestions on the best way to deal with it?
One thing I considered was deploying the latest version to these devices and using `Uninstall-Software.ps1` as a pre-install script. However, from reviewing the script it looks like you can search HKCU, but surely that won't work when Intune runs it as **SYSTEM**, as the current user would be SYSTEM rather than the affected user profile?
#35
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Publisher - Timeout wrong
Last post by Priscilla (Patch My PC) - June 25, 2026, 11:23:09 AMHi sw-deploy,
Sorry for the delayed reply. Yes, can you please submit a ticket with us here: https://patchmypc.com/technical-support/
Please include the following logs to help us troubleshoot the issue:
Could you please generate a server-side log bundle by following the steps below:
If possible, please also include client-side logs: https://patchmypc.com/kb/collect-sccm-intune-logs/#h-client-side-logs
Thanks!
Sorry for the delayed reply. Yes, can you please submit a ticket with us here: https://patchmypc.com/technical-support/
Please include the following logs to help us troubleshoot the issue:
Could you please generate a server-side log bundle by following the steps below:
- In the General tab of the Publisher, click on the Collect Logs button under Logging Options
- Pick a Folder where you want to save the logs to
- a ZIP file will be created in that location containing the relevant server-side logs needed for troubleshooting. You can then send that ZIP file over to us
If possible, please also include client-side logs: https://patchmypc.com/kb/collect-sccm-intune-logs/#h-client-side-logs
Thanks!
#36
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Publisher - Timeout wrong
Last post by sw-deploy - June 24, 2026, 11:26:20 PMAny idea, because this issue is quite serious?
Or should I create a ticket?
Or should I create a ticket?
#37
Home Updater: Report Detection Issues or Installation Issues / Veracrypt update needs differe...
Last post by apricoto - June 24, 2026, 03:44:44 PMI have a MS Surface 13 with Snapdragon ARM processor. win11 home
pmp is downloading and trying to install the .msi version for Veracrypt update. It then fails install.
It needs the .exe version to update. I manually downloaded the .exe and it installed.
pmp is downloading and trying to install the .msi version for Veracrypt update. It then fails install.
It needs the .exe version to update. I manually downloaded the .exe and it installed.
#38
Home Updater: Report Detection Issues or Installation Issues / Re: Owncloud Desktop App stops...
Last post by rarnold - June 23, 2026, 01:15:13 PMYour are welcome, Omar. It's a honor to assist you and the rest of the PMPC team!
#39
Home Updater: Report Detection Issues or Installation Issues / Re: Owncloud Desktop App stops...
Last post by Omar (Patch My PC) - June 23, 2026, 10:46:44 AMYou are correct! I just pulled it to v6.0.3
Will see if we can add v7 separately, Thank you!
Will see if we can add v7 separately, Thank you!
#40
Home Updater: Report Detection Issues or Installation Issues / Owncloud Desktop App stops wor...
Last post by rarnold - June 23, 2026, 08:14:19 AM20:59 21.06.2026 MEZ
Dear colleagues,
pls stop the (auto-) update from OC desktop client app 6.x to 7.1x!
https://github.com/orgs/owncloud/discussions/3#discussion-10285523
TL;DR
Background: 7.0 removed ownCloud Server support
Starting with Desktop App version 7.0, the client no longer supports ownCloud Server — it only connects to ownCloud Infinite Scale. If you need to keep using ownCloud Server, you must stay on a 6.x client.
So when a 7.x client is pointed at an ownCloud Classic server, the connection can no longer work as before. That is expected behaviour, not a bug in your setup.
Kind regards
Ronald Arnold
Support engineer ivdk.org
Dear colleagues,
pls stop the (auto-) update from OC desktop client app 6.x to 7.1x!
https://github.com/orgs/owncloud/discussions/3#discussion-10285523
TL;DR
Background: 7.0 removed ownCloud Server support
Starting with Desktop App version 7.0, the client no longer supports ownCloud Server — it only connects to ownCloud Infinite Scale. If you need to keep using ownCloud Server, you must stay on a 6.x client.
So when a 7.x client is pointed at an ownCloud Classic server, the connection can no longer work as before. That is expected behaviour, not a bug in your setup.
Kind regards
Ronald Arnold
Support engineer ivdk.org