wkiess01

Sorry, but the problem appears to have subsided with the exclusion I've entered, so I'm not able to provide a screenshot. I'll have to wait for the next change(s) to the .NET apps or for another user to try and use the apps. I'll be sure to get screendumps from them if it happens again.

Thanks for your reply Dyllon. I do not know the path of the file in advance. I've only discovered the path based on the Malwarebytes quarantine log. Perhaps in hindsight I should have titled my question "How to exclude .NET ClickOnce installation files". I am not in control of the path or filename of these .NET ClickOnce installation files, so I cannot predict their path or name to include in the exclusions list. Is there another way to allow the ClickOnce installation files to execute? It would be nice to just click on Detection Details in the dashboard and click on an "Add to Exclusions List" button to whitelist the program.

Thanks for your suggestion Dyllon. I'm a bit concerned this may be too generic though, basically excluding everything in that path (and with a wildcard!). I would prefer to exclude just the filename itself. The documentation for excluding a file states: It is not clear if specifying just the filename will exclude it no matter what path it is in or whether the path to the file must also be specified. I therefore entered just the filename and extension which oddly seems to work for one PC but not another. Furthermore, there is no Browse button as suggested in the text (see screenshot below).

Thanks for your replies. I did read the Admin Guide but wasn't clear on the way to add the exclusions since the file can be located anywhere on the user's pc. The file in question is generated and download by .NET ClickOnce which checks if there's a new version of (my) software available and downloads and installs it if so. I have no control over where the file is located on the user's pc. I only know the name. I added this name in the exclusions list and oddly it appears to work fine, i.e. is excluded, on one PC, but not another, hence my request for help. The Malwarebytes log shows a path like C:\User\user_id\AppData\Local\Apps\2.0\some_long_path_name\some_other_long_pathname\filename.exe. Should I change the exception to read: C:\User\*\AppData\Local\Apps\2.0\*\*\filename.exe?

I've recently installed MB Endpoint Protection and shortly after users started complaining some programs would no longer work and a MB message would pop up saying the program was not allowed. I added the program name into the exclusions list, but it's still happening. I added just the filename xxxxx.exe as it lives in a different place on each PC's user folder. What am I missing?