Error exporting SEP client package from SEPM: "Failed to create a single .EXE file..."

Products

• Endpoint Protection

Issue/Introduction

Error exporting SEP client package from SEPM: "Failed to create a single .EXE file..."

Symptoms
Attempting to export a SEP client install package from the SEPM with the option select to "Create a single .EXE file for this package." results in an error at the end of the export:

Failed to create a single .EXE file under "[path name]"

Exporting a SEP client install package to the same location may export fine without error.

Cause

This is caused by a lack of permissions for the current user to the directory the install package is being exported to.

Resolution

Make sure the currently logged in user has proper permissions to the directory they are exporting the SEP client install package to.

The current user must have Modify, Read & Execute, List Folder Contents, Read, and Write permissions to the folder where the export package is being created.



Technical Information
Specifically it seems that not allowing the user (or group) "modify" permissions to the directory still allows the Install package to export if it's NOT a single EXE, but reproduces the same error if the option is checked for a single .EXE.

The [Path Name] is the actual path with a temporary subdirectory named with a long (seemingly random?) alphanumeric name (example: C:\A07EF524BBA.......)