Skip to main content

Application Start Does Not Trigger Profiles Operation

Problem​

If you've configured a Profiles object in Simplify Profiles 6.x to perform operations at application start or end, you might notice it's not actually doing anything. This isn't a configuration mistake on your part—it's a known bug that affects all versions of 6.x.

The issue affects both HKCU registry operations and file operations. When you set a profile to trigger "at application start/end" on the Config tab, the profile operation simply won't apply. The configuration looks correct in the console, but the trigger never fires.

Workaround​

Until this issue's fixed in a future release, you'll need to work around it by changing when your profile operations occur. Instead of using application start/end triggers, configure all your Profiles objects to perform operations at user logon/logoff.

This workaround applies to both types of operations:

  • HKCU registry operations
  • File operations

While this doesn't give you the exact same timing as application-level triggers, it ensures your profile operations actually apply. For most use cases, logon/logoff triggers provide similar functionality and work reliably.

Affected Versions​

This bug's present in all versions of Simplify Profiles 6.x. Tricerat plans to address it in a future release, though a specific timeline isn't available yet.

If application-level triggers are critical for your environment and you can't work around them with logon/logoff triggers, contact Tricerat Support to discuss your specific requirements and potential alternatives.