• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Dan Gough (Patch My PC)

#1
Unless the installer is designed to copy the script to the correct location if it finds it next to the installer, you will need to write a post-install script to copy the file. If you've tried using a script already, can you post the script contents here?
#2
Sorry this change did not go in, I'll push to get it in today's release.

Skip means it will exit and not try to update. It will retry whenever WSUS / ConfigMgr / Intune (whatever is deploying it) decides to do so - we cannot indefinitely snooze updates since that would block other updates from running and also be subject to a timeout. Here is the a post on this:

https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications

And the docs for Patch My PC Cloud:

https://docs.patchmypc.com/installation-guides/patch-my-pc-cloud/deployments/deploy-an-app/configurations#conflicting-process
#4
The Edge update checks for a specific reg key that is only put down once the MSI has been installed at least once.

If you push out the App to all devices just the once, or include it as part of your build process, then the updates should apply.

We are doing a review internally to see if we are able to change this detection to make life easier.

#5
Upon further talks with the team, it seems LibreOffice released 25.2.0 as their stable release by mistake for a short while, then pulled it. It's now classified as a pre-release.

Hence the original URL (that had 'stable' in there) no longer being accessible:
https://download.documentfoundation.org/libreoffice/stable/25.2.0/win/x86_64/LibreOffice_25.2.0_Win_x86-64.msi

We plan to pull this release from our next catalog release.
#6
If you want to deploy 'LibreOffice Latest (MSI-x64)', you can get going quicker for now if you download manually and place in your local content repo:

https://download.documentfoundation.org/libreoffice/testing/25.2.0/win/x86_64/LibreOffice_25.2.0.3_Win_x86-64.msi.mirrorlist
#7
It appears that the 'LibreOffice Latest (MSI-x64)' package, which supplies 25.x, has a dead URL. We'll get this updated!

#8
I tried both, in both cases the previous version was installed, app launched and service running whilst update was applied.

Please could you raise a support case via https://patchmypc.com/technical-support?
#9
I was unable to reproduce any issue when upgrading from an older MSI to the current version. The app and service were closed automatically, without having to enable Manage Conflicting Processes.

Windows Installer automatically shut down and remove the previous MSI before installing the new one.

Were you upgrading from and to the same package type, e.g. MSI x64?
#10
LibreOffice was updated to 24.8.4.2 in the catalog yesterday, which is the latest stable release:

https://www.libreoffice.org/download/download-libreoffice/

25.2.x is a pre-release, so if you didn't have a pre-release version installed originally, this sounds like a bug in LibreOffice's auto updater, so should be raised with them.
#11
I will see if I can repro here - but the first thing that jumps out is that this MSI executes teamviewer.exe as part of its installation routine, so make sure the option is not selected to block execution during install.

I see this in the log:

WixQuietExec:  "C:\Program Files\TeamViewer\TeamViewer.exe" api --uninstall
WixQuietExec:  Error 0x80070003: Command line returned an error.
#12
I've just done some testing and have not been able to reproduce this so far.

With Manage Conflicting Processes enabled, the app is closed and the update succeeds.
If MCP is set to ignore the running app and proceed, then the installer fails quickly before attempting to install.

It doesn't make sense to have /NOCLOSEAPPLICATIONS though, so we'll remove this from the default command line as it seems it could conflict with the other option on offer /FORCECLOSEAPPLICATIONS.

I also tested with /FORCECLOSEAPPLICATIONS /LOGCLOSEAPPLICATIONS though, and that did force close anything either.
#13
Unfortunately we cannot add dependencies in our platform just yet - however Autodesk Access is in the catalog, and if you manually create a dependency, we will copy them forward when creating a new version of the update. However, these dependencies only relate to ConfigMgr apps, and Intune apps/updates.
#14
Unfortunately it's a bigger piece of work than you may think:

- Every app in the catalog needs to be assessed for ARM compatibility, or to see if there is native ARM variant that can be added.
- For apps that do not have an ARM native version, only Windows 11 can run x64 apps, whereas Windows 10 can fall back to the x86 version (if they work - e.g. anything that contains a driver won't be compatible).
- This compatibility logic needs to be built into the catalog and main Patch My PC platform as well as the Home Updater (it's particularly tricky for Intune deployments).
- Automated test platforms also need to be extended to run on ARM devices.

It is a big priority for us in 2025 however, as we have had many requests for this.
#15
If you have customised the TeamViewer online via:

https://www.teamviewer.com/en/global/support/knowledge-base/teamviewer-classic/deployment/download-the-msi-package/

Then we do not support this MSI, as it will be unique for each customer, and we verify the hashes of all installers.

You can download the generic MSI packages from these links:

https://dl.teamviewer.com/download/version_15x/TeamViewer_MSI64.zip
https://dl.teamviewer.com/download/version_15x/TeamViewer_MSI32.zip