Troubleshooting Application Control issues
What to do if applications are not launching
Despite user overrides, applications do not launch. This is because the associated processes of the applications are not added to the allow list.
Monitor the events for the blocked process of the associated application and then add the blocked process to the allowed list in the Application Control policy.
Checking to see if a device is licensed for Application Control
- To check to see if a device is licensed for Application Control
- On the client device, locate the Common Agent Framework log. For example:C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.2.984.0100.105\SAEP\Common Agent Framework\Log
- Open the file and make sure that it contains a line that shows the licensing state as entitled:"APP_CONTROL_WHITELIST\"state\":\"ENTITLED\"
Viewing the local allowed applications list on a device
To view the local allowed app list on a device
- You must have administrator privileges on the local device.
- Open a command window and type a command similar to the following command. Use the folder structure that is relevant on the local device."C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.2.984.0100.105\SAEP\IPS\bin\sisipsconfig.exe" -localwhitelist
- The command returns a list of applications and files that are allowed on the local device by user overrides and trusted updaters.
Check interaction with Application Isolation
If you also use Application Isolation, you should make sure that you understand how the policies interact. See: