How to Block Application Updates

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Posts: 7
Last visit: Mon Apr 19, 2021 6:51 am

How to Block Application Updates

Post by PNCCorpUseSoftware »

Product, version and build: PrimalScript 2021 7.7.146
Operating system: Win10 1909
PowerShell version(s):

*** Please add details and screenshots as needed below. ***
We have recently moved to the PrimalScript 2021 7.7.146 version, due to our company application update, approval and deployment process, we need to prevent users from getting prompted or doing the "check for updates" within the application so they do not attempt to download and install any version that hasn't been reviewed or approved. Due to most users of this application having "admin" rights to their workstation, that in itself is not restrictive enough.

If it is not possible to change something within the application setup/registry, can you provide what URL would need to be blocked that when users chose "check for updates" it would not find a newer version? Also any download URL's that would need blocked to stop them from downloading. I'll be submitting this same request for Powershell Studio as well.

User avatar
Alexander Riedel
Posts: 7671
Last visit: Thu May 13, 2021 5:46 am
Answers: 3
Been upvoted: 9 times

Re: How to Block Application Updates

Post by Alexander Riedel »

You can uninstall the SAPIEN Update tool. That would effectively put an end to PrimalScript and PowerShell Studio checking for updates.
However, we frequently update PrimalScript and PowerShell Studio to address changes in the operating system and PowerShell. PowerShell 7 is on a specially aggressive update path itself and requires us to frequently issue updates. Please note that while we can make a note on your account that you discourage unapproved updates for your employees, we cannot actively prevent your users from reading our change logs and downloading the current version themselves. If they request support in this forum for a specific problem, they may still get instructed to update to the latest build if that is solving the problem.
I also have to stress that if an update includes any security updates in the products or third party components (e.g. the WiX installer toolkit), it will be your responsibility to to inform your users and roll out any required updates.
Alexander Riedel
SAPIEN Technologies, Inc.