As there was no reaction in my last post from german section, I try it once again in english.
I am currently having a major problem with the free version of Avast. This includes, among other things, to install files of older applications such as "Winamp 5.63", which I absolutely need. These have recently been recognized as adware files and are therefore not executed. The problem with this is that, despite the added exception approval, they can no longer be started, regardless of which settings are still made. I already deactivated all options that might have to do with it: PUP, file system protection, as well as the check options when executing, opening and writing files and several subsequent restarts. Unfortunately, it doesn't help! The error message reads as follows: "The specified device, path, or file cannot be accessed. You may not have sufficient permissions to access the item."
Even disabling the Avast protection feature completely does not solve the problem. Only the error message changes (NSIS Error - Error lauching Installer). In other words, once executed, the file can no longer be accessed, including copying and viewing the file. Only renaming and deleting still works, which unfortunately does not help if the file is on a burned data carrier such as a DVD-R. The corresponding file can only be executed again after Avast has been completely uninstalled and is displayed normally again with the corresponding icon.
The current Windows 10 (2H20) operating system is used and only the module for file protection is installed, as the remaining functions are not required. Virus and program libraries are also up to date and the UAC is completely deactivated or is set to "Never notify". The problem apparently also existed with earlier program versions, but has unfortunately gotten worse over time, especially with regard to the error detection of older installation files. Everything would be half as bad if at least the intended exception function would work correctly, but without this the program is completely useless to me.
The above problem apparently only occurs on Windows 10, tested with a laptop and desktop with the same build versions. This problem does not exist with an older Windows 7 PC. The files are not even recognized as a possible threat and can be started directly. It also doesn't seem to be due to the "Total Commander" with which all files are managed and executed on the PC, since the problem also occurs on both Windows 10 computers in connection with the built-in file explorer.
