Hello

Since last week I have an old-ish application that no longer runs and I get the below error. If I remove endpoint it runs. If I install endpoint and put in an older definition file (1.199.2103) it still runs. If I run anything from end of last week it fails(testing 1.201.478)

The error relates to us not having dotnet installed. which we do

Testing on Endpoint 4.7.213 and also the latest 4.8.

Win8/8.1

Anyone got any ideas?

To narrow this down further it looks like the network inspection is to be causing the problem

OK now this is weird. one a few machines it is fine, not on others. definitively turning off monitor file and program activity and (turn off)enable behaviour monitoring fix's the problem with the app. but leaves me open to vulnerabilities.

The app is a dotnet based application.

In the end added exceptions and all now ok.

exceptions only take effect after the machine is rebooted despite them displaying in the console window

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator 1 hour 22 minutes ago

In the end added exceptions and all now ok.

exceptions only take effect after the machine is rebooted despite them displaying in the console window

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Wednesday, July 01, 2015 6:02 AM

In the end added exceptions and all now ok.

exceptions only take effect after the machine is rebooted despite them displaying in the console window

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Wednesday, July 01, 2015 6:02 AM

In the end added exceptions and all now ok.

exceptions only take effect after the machine is rebooted despite them displaying in the console window

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Wednesday, July 01, 2015 6:02 AM
• Marked as answer by Joyce LMicrosoft contingent staff, Moderator 23 hours 24 minutes ago

In the end added exceptions and all now ok.

exceptions only take effect after the machine is rebooted despite them displaying in the console window

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Wednesday, July 01, 2015 6:02 AM
• Marked as answer by Joyce LMicrosoft contingent staff, Moderator Tuesday, July 07, 2015 8:01 AM

Report this issue to the application owner and let them know , so they could fix it.

Also , try run application in compatibility mode (just for test) and see if it makes any different.