Any suggestions how to proceed without wiping the disk clean and re-installing everything? Which may or may not help.
For now I'm running fs_usage on the file in question, 882650.txt, that while it got put back is in another directory since I rebuild the whole Spotliogh cache.
Thank you for being patient, Majkel.
We are improving the removal mechanism coming in the 18.3 and after the release, these issues should get fixed.
Your patience is much appreciated.
Update: I removed the file manually with "sudo rm" and after a few days now it has not been recreated nor does AVG find any JS:ScriptIP-inf anywhere. I'm still running fs_isage to see which process creates this file, if and when it's recreated.
I still wonder why AVG can't move this file. Can't I elevate its permissions as I did with "rm"? Or is this not adviseable?
Hello Majkel,
I understand the inconvenience caused, let's work together to fix this issue.
Could you share a screenshot of the AVG detection to assist you further?
You can post the screenshot here on your topic. Click on 'Answer' & then click on the 'Image' [mountain symbol] & follow the instructions.
Best regards,
Alok.
AVG keeps finding JS:ScriptIP-inf in my ".Spotlight-V100" folder on a macOS 10.12.6 "Sierra" machine.
It fails to remove it. I got rid of it yesterday by adding my root disk to "places to ignore" in Spotlight preferences and changing the permissions of the ".Spotlight-V100" folder, then deleting it. Then restarting.
After this I removed my disk and let the Spotlight index be rebuilt. After this it was gone for repeated scans of the ".Spotlight-V100" folder. Today it's back!
If AVG can detect "JS:ScriptIP-inf", then why can't it remove this menace?
Majkel, thank you for uploading the screenshots.
I would request you to move the file to a temporary folder and try removing it from there.
Update: I removed the file manually with "sudo rm" and after a few days now it has not been recreated nor does AVG find any JS:ScriptIP-inf anywhere. I'm still running fs_isage to see which process creates this file, if and when it's recreated.
I still wonder why AVG can't move this file. Can't I elevate its permissions as I did with "rm"? Or is this not adviseable?
Any suggestions how to proceed without wiping the disk clean and re-installing everything? Which may or may not help.
For now I'm running fs_usage on the file in question, 882650.txt, that while it got put back is in another directory since I rebuild the whole Spotliogh cache.
Thank you for being patient, Majkel.
We are improving the removal mechanism coming in the 18.3 and after the release, these issues should get fixed.
Your patience is much appreciated.