Skip to main content

App Corrupted Error

Issues related to the "corrupted" error modal that appears when launching the Electron application.

Quick Diagnostics​

  • Is the build under a new version that is not available in Control?
  • Is it a new build under an existing Electron version with additional changes in the /electron folder?
  • Does the checksum match the deployed MSIX?

Issue: "Corrupted" Error Modal on App Launch​

Symptoms​

  • Error modal appears immediately when opening the application
  • Application refuses to start
  • Message indicates the app is "corrupted" or integrity check failed

Environment​

  • Affected platforms: Windows (Electron/MSIX)
  • Frequency: After new release deployment, OR on an existing version with additional changes in the /electron folder (eg. changes from a Pull Request).

Root Cause​

The integrity check in Accedo Control does not have the new version's checksum registered, or the checksum doesn't match the deployed MSIX file.

When a new MSIX is deployed, its checksum must be added to Accedo Control. If this step is skipped or the checksum is incorrect, the app fails the integrity verification.

Additionally, if there are Pull Request (or local) changes to the /electron folder under an existing version, a new checksum will be generated, and must be addded in Accedo Control

Solution​

Option 1: Register the new version in Accedo Control

  1. Get the checksum from the build artifacts (generated during the MSIX build)
  2. Navigate to Accedo Control
  3. Follow the Integrity documentation to add the new version and checksum

Option 2: Verify existing checksum

If the version is already registered, verify the checksum matches:

  1. Compare the checksum in Accedo Control with the one from build artifacts
  2. If they don't match, update the checksum in Accedo Control

Verification​

  1. Uninstall the application
  2. Reinstall from the MSIX
  3. Application launches without the corrupted error

Prevention​

  • Always update Accedo Control with the new checksum before or immediately after deploying a new MSIX
  • Include the integrity update as a mandatory step in the Deploy to Production runbook
  • Generate and save checksums as part of the build pipeline artifacts

Still Stuck?​

If none of the above solutions work:

  1. Collect information:

    • Electron/MSIX version being deployed
    • Checksum from build artifacts
    • Current Accedo Control configuration

  2. Ask for help:

    • Post in #prj-hp-dev with collected information