Did you review the Windows Event (Application ) logs for any events generated by Solidcore? Also it my pay to review the `Solidcore.log` diagnostic log in the path C:\ProgramData\McAfee\Solidcore\Logs\.
For what it is worth my understanding of the Trusted User privilege is that is allows the user to make dynamic changes to the local whitelist, I don't believe its a mechanism to implement granular access to execute a binary based on user. I wouldn't expect Solidcore to treat execution of a binary as a modification attempt therefore the Trusted User rule would not be applicable and I would expect the Banned Binary rule to be the next match hence the Execution Denied behaviour.
Thanks Mick, I agree with you and I am going to implement this in change control to give read access to a particular executable.
I haven't tested this myself, but a possible workaround is could be using the `skiplist -s C:\Program Files (x86)\Internet Explorer\iexplore.exe` command to prevent Internet Explorer from being added to the local system whitelist. Remove your Banned Binary rule for `iexplore.exe` and then attempt to execute as a standard user and then as a Trusted User; can you launch Internet Explorer? Note that if this workaround is successful the `iexplorer.exe` wouldn't have any write protection, therefore malicious code could potentially be injected into Internet Explorer that a Trusted User could execute. I'd be interested to know if this does work.