Scappman Support Center
  • Scappman Support Center
  • 🖥️Applications
    • What is the difference between public and private applications?
    • How Scappman keeps your available apps up to date
    • Pausing Scappman Updates
    • How will Scappman interact with applications that already exist on my device
    • Why is there a Scappman pop-up
      • How to add custom branding to the pop-up
    • Request a new managed app
    • Using MST's with Scappman Apps
    • Bring your own app to Scappman
      • Uploading your own app to Scappman
        • Install Command Cheat Sheet
      • Updating your private (custom) applications in Scappman
      • Additional files in custom apps
    • My applications can't be opened after an update
    • Scappman PowerShell Certificate
    • Discovery & Autopatch
    • Deploy your first app
  • 🔓Permissions
    • 🧑‍🏫User permissions
      • How to add an additional admin in Scappman
      • Admin roles
    • 🤖App Registration
      • How to grant admin consent to Scappman
      • Why do we need permissions in your tenant?
  • 📃Billing
    • ⚖️How does billing work?
    • 🛑What happens when I cancel my subscription
    • ✉️Update company information and email recipients
  • 🤝Partner
    • How to activate a customer as a partner
    • How to invite customers in Scappman as a Partner
  • 📬Support
    • Contacting support
    • Custom app support
    • Troubleshooting log file reference
    • 🆘Error code reference
  • ⚠️Known Issues
    • Scappman reports not populating
  • ⌨️Advanced Configurations
    • Using custom registry keys during installation
    • TeamViewer Host activation
Powered by GitBook
On this page
  • Problem
  • Solution

Was this helpful?

  1. Applications

My applications can't be opened after an update

Scappman uses the PSADT module to add some additional features.

One of these features is to make sure that during an update, the application can't be opened to make sure files are not in use during the update. This function is called Block-AppExecution and does the following:

  1. Makes a copy of this script in a temporary directory on the local machine.

  2. Checks for an existing scheduled task from previous failed installation attempt where apps were blocked and if found, calls the Unblock-AppExecution function to restore the original IFEO registry keys. This is to prevent from overriding the backup of the original IFEO options.

  3. Creates a scheduled task to restore the IFEO registry key values in case the script is terminated uncleanly by calling the local temporary copy of this script with the parameter - CleanupBlockedApps.

  4. Modifies the "Image File Execution Options" registry key for the specified process(s) to call this script with the parameter -ShowBlockedAppDialog.

  5. When the script is called with those parameters, it will display a custom message to the user to indicate that execution of the application has been blocked while the installation is in progress.

Problem

It happens sometimes that the update is interrupted during the update. As an example, let's assume the computer ran low on battery. Then after reboot, the scheduled task was not removed, causing the application not to launch.

Solution

  1. Redeploy the application to the affected users, this will clean up the scheduled task.

  2. Use the following Powershell commands to clean-up the process. These commands should be run as an administrator.

Install-module PSADT
Import-module PSADT
Unblock-AppExecution

Last updated 2 years ago

Was this helpful?

🖥️