It seems like a bad idea to just use Windows like nothing is wrong. It told me that the only way to remove it is to restart (see attached screenshot) I have scanned the file at virus total and it is clean on every test, even Avast. No idea how or if I should go about putting the file back. Dobrý den, dnes, jsem si z nejnovjího cd z asopisu SCORE nainstaloval hru Minimal Raider a kdy jsem ji chtl spustit, tak mi to Avast zablokoval, kvli hrozb IDP.Generic etl jsem e je to vtinou jen planý poplach, ale i tak jsem to hodil to truhly a chtl to jít. After running Windows Update last night, today Avast told me that printconfig.dll is infected (IDP Generic) and moved it (or a copy) to the chest. The system isn't hanging or anything and apparently I can print okay. If no threat was found, it means that Avast/AVG had a false positive, and you’re now fully protected. If the antivirus software identifies any files or programs as IDP.Generic, you can quarantine or remove the threat. Once the scan is complete, review the scan results. This is the version of the file in question (from the MS Update file list): Step 2: Quarantine or Remove Detected Threats. The file it removed is in an archive in the system folder nearby. It seems pretty unlikely that Windows shipped a file with a problem. If ‘IDP.Generic’ Avast blocks a download, and if you’re sure it’s not. I managed to reinstall the software and ran it again. The first time this occurred, the file had been put in the Virus chest, but I didn't know what to do with it. It didn't flag it before running the application. I tried digital signatures from two publishers. Differences in PowerShell commands used in the application. After investigating the cause, it was found that IDP.Generic has two condition. To avoid such instances, you should use the latest version of Avast. Avast flagged a recently installed application as having IDP.generic shortly after starting the application. My application was detected as IDP.Generic. Some more information: the update install log I received yesterday contains many references to print services and the file itself. Doing so prevents Avast from blocking the files. I deleted scan history and rescanned the system and the file itself before restarting (as well as backing up some data and creating a restore point) but it didn't make a difference. Well, it seems that it removed the file on restart.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |