Showing results for 
Show  only  | Search instead for 
Did you mean: 
Former Member
Not applicable
Report Inappropriate Content
Message 1 of 4

Application Control: Trusted User does not work with .NET 4.8

Dear McAfee, I have two virtual machines in a domain (ePO 5.10 and AC Solidcore 8.2.1 on WS 2016, client  node with W10 LTSB 2016). Both the machines are solidified, AC is enabled, inventory fetched. I defined a Trusted User (in order to dynamically change the whitelist) and use it to run our main application to install a lot of (about 40) MSI packages (included 3rd-party). This app launches all the packages with such TU and all of them are successfully installed BUT the .NET 4.8. The error is related to the "DismCorePS.dll" which is "not on the corporate whitelist and not allowed to run". The .NET package as said runs with such TU, the same errors occurs if the package is manually installed ("run as that trusted user)". Note that such TU has admin privileges. Why does it happen? I've tried other documented ways to solve it (from the product guide), uselessly.

Regards, Andrea Ferro

PS the DLL appears to be copied many times in "C:\Users\<TU>\AppData\Local\Temp\<HEX number>"

3 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Application Control: Trusted User does not work with .NET 4.8


To answer this question we will require the Solidcore.log for checking on the reason why the dll is not whitelisted when extracted via  trusted user.



Was my reply helpful?
If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?
Former Member
Not applicable
Report Inappropriate Content
Message 3 of 4

Re: Application Control: Trusted User does not work with .NET 4.8

Hi thanks a lot for the quick reply, really appreciated. There are many errors inside the log actually, but not much helpful for me. If I search the "dismcoreps" keyword, it seems to be confirmed that the error is a deny error: the reason is because the file is not in the local whitelist... but of course it is not. But I also found a reference to a process that cannot be "marked" as updater... but I'm not able to come to a solution.

Please note that the "agent failed to send events" (red row in monitor) but it seems not related to this problem as it is refers only to the .NET DLL (not all the other packages successfully installed and then executed). I attached the compressed log and hope you can help me to solve it (or suggest which rule I need).

 BR, Andrea

Level 8
Report Inappropriate Content
Message 4 of 4

Re: Application Control: Trusted User does not work with .NET 4.8

I am encountering the same issue with this .dll

Was there any outcome that allowed this .dll to be whitelisted?

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community