alissa914

I had this just happen to me. Mine said "95%" instead of "100%". It was compiled in NET 3.5 in Windows 10, so I switched it to NET 4.0 to see if that did it too. Turns out that didn't throw an error. After that worked, I switched back to 3.5 and the error stopped showing up. I didn't whitelist anything in the app and have no external components in my app either. Not sure why it threw this warning though.

I had this just happen too which is why it was odd. It never threw up a detection before. All I did after that was to switch to .NET 4.0 in Visual Studio, compile/run it to confirm there was no infection, and then switch back to .NET 3.5 like it was (some people there still use XP against my wishes)..... But it stopped prompting this as an error though.