Fix EXE Installer Script Failed Errors on Windows

Executive Summary

• Affected scope: Windows devices running PowerShell-based custom scripts deployed through Hexnode.
• Common symptom: Start-Process reports that the downloaded file or directory is corrupted and unreadable.
• Primary cause: The download URL does not return the actual installer file without user interaction.
• Confirmed resolution: Replace the cloud storage link with a publicly accessible direct-download URL, such as a public Google Cloud Storage Bucket URL.
• Validation step: Run the same PowerShell script manually on a test Windows device before deploying it through Hexnode UEM.

Error message shown during script execution

The script may show output similar to the following after the installer download and installation command begins:

The path under C:\Hexnode\Hexnode Agent\Current\resource\... refers to the location where the Hexnode Agent downloads the script resource before executing it. It does not necessarily mean that Hexnode UEM is trying to run the installer from that path.

The Output can be verified from the Action History sub-tab of the device and clicking on the corresponding the Execute Custom Script action.

Learn more about executing custom scripts on Windows devices.

Why the downloaded installer becomes unreadable

The Start-Process error can appear even when the script syntax and installer arguments are correct. In the confirmed case, the issue was caused by the file URL rather than the PowerShell command.

When a script downloads an installer from a cloud storage link, the URL must return the installer binary directly. The deployment can fail if the URL returns any of the following instead:

• A Microsoft sign-in page or any authentication prompt.
• A cloud storage preview page instead of the file.
• A browser-based confirmation prompt for large files.
• An incomplete or redirected download response.

Note: Some cloud storage services generate additional confirmation prompts for files larger than 100 MB. If the installer is over 100 MB, verify that the URL downloads the file directly without any browser prompt or credentials.

Resolve the Start-Process corrupted file error

1. Host the .exe installer in a location that supports public direct downloads.
2. Confirm that the URL does not require credentials, browser interaction, or a confirmation prompt.
3. Open the URL in a private or signed-out browser session to verify that the installer downloads immediately.
4. Update the PowerShell script to use the verified direct-download URL.
5. Confirm that the downloaded file path in the script points to the actual installer filename, such as falconsensor.exe or the installer filename used in your deployment.
6. Run the script manually on a test Windows device through PowerShell to validate the download and installation behavior.
7. After the script succeeds manually, deploy the same script remotely through Hexnode UEM.

Workaround: Replacing the failing cloud storage link with a public Google Cloud Storage Bucket URL allows the PowerShell script to install the Windows application successfully.

Validate the script manually before deploying through Hexnode UEM

Manual validation helps separate script issues from remote deployment issues. On a test Windows device, run the PowerShell script locally and confirm that it downloads and starts the installer without requiring any interactive sign-in or browser prompt.

If PowerShell blocks local script execution, the device may show an error similar to:

To view the execution policy configuration, run:

To allow the current user to run scripts for manual testing, run:

Note: Changing the PowerShell execution policy on a test device is only a validation step. It does not resolve a failed download URL that returns a sign-in page, confirmation page, or incomplete installer.

Troubleshooting checklist for Windows installer script deployments

The URL opens a sign-in page

Use a different hosting location that provides a public direct-download URL. Links that require Microsoft credentials or any other authentication cannot be used as unattended installer downloads.

The installer is larger than 100 MB

Verify that the hosting service does not show an additional large-file confirmation prompt. If it does, move the installer to a storage service that supports direct public object downloads, such as a public Google Cloud Storage Bucket URL.

The script works manually only after changing the execution policy

The local device is blocking PowerShell script execution. Use Get-ExecutionPolicy -List to inspect the policy and adjust it only as needed for validation. If the script still reports that the file is corrupted after the policy change, re-check the installer URL.

The script output references C:\Hexnode\Hexnode Agent\Current\resource

This path refers to where the Hexnode UEM Agent stores the script resource before execution. It is expected during Hexnode script deployment and is not, by itself, the cause of the installer failure.

Review script execution activity in Hexnode

Script-related device actions can be reviewed from:

Reports -> Action reports -> Action history.

Sort the action by “Execute Custom Script” and filter the devices.

Note: Custom reports for selecting script execution attributes or filtering custom script results by success and failure can be created from Hexnode UEM.

1. Navigate to Reports -> Custom reports -> Add -> Action.
2. Provide Report name and Description.
3. Set Condition Filters where Action name is “Execute Custom Script”.
4. Add the available columns including Action status.
5. This report will segregate all the Execute Custom Script action executed across various Windows devices.