![]() (I do have a backup copy, but data loss is not a good feature). What's more, it is not in the virus chest either. I decided to restart, but the restart process runs a batch file which stalled because the script that is always first to be reported didn't exist in its usual place. ![]() I waited a while, but the dialog never expanded size. Observation 6: When the report happened a few minutes ago, the Avast dialog popped up but only very tiny, with the word Avast. I was looking for one (actually two, one for each script) of the first form and found them. I'm not sure I noticed the 2nd entry before, but I can''t guarantee it wasn''t there, either. Your files will be flagged by this whenever the file does something identical to malware that triggers the flag. Just now I noticed that the exceptions are recorded both as d:\path-to-script and \\computername\d\path-to-script. IDP generic means that the detection was detected by an Identity Protection detection component of your antivirus and it is a generalized file that got detected. Observaction 5: I noticed the exceptions were intact upon restart, and before Avast reports them again. Observation 4: The location of the script is on a network share that actually points to a folder on my local hard drive: net use d: \\computername\d where d is a sharename pointing to a folder on one of my local hard drives (which is drive b:, but not is an SSD not a floppy drive). Once per restart seems to be guaranteed, although it may be some hours between restart and first report. This can either be a false positive as well which happened due to an outdated definitions and got fixed after updating avast. Observation 3: Although I make an exception, and Avast records the exception, the next time I restart, the reports will happen again. IDP generic means that the detection was detected by a Identity Protection detection component of your Avast AV-solution and it is a generalized file that got detected. I don't think the scripts are interconnected, they do different things, but there is always this one, two sequence. ![]() Observation 2: While telling Avast to make an exception for one of the scripts, it reports the other one. Observation 1: During the harrassments, I note that the mouse motion is extremely slow on-screen, making it easy to overshoot the target location (the Avast popup) and thus hard to quickly deal with the problem. although this started on a new computer, having a somewhat different configuration than former ones. So I have been harrassed by Avast reporting IDP.GENERIC for a couple AHK (autohotkey) scripts that I have been using for years. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |