Author Topic: Removed or Not  (Read 1371 times)

0 Members and 1 Guest are viewing this topic.

loadmaster

  • Guest
Removed or Not
« on: February 10, 2013, 03:48:46 AM »
Ran full scan JS:Scriptip-inf was found.  Scan log under actions could not be repaired.  Ran a boot scan in safe mode and found it again.  Started in normal mode avast log listed both finds and deleted the one under boot scan.  So is the problem fix in the normal mode or not

Offline Staticguy

  • Super Poster
  • ***
  • Posts: 1427
Re: Removed or Not
« Reply #1 on: February 10, 2013, 09:25:22 AM »
Rescan it in safe mode, boot scan, and in normal mode? If doesn't find anything, you are all good..
DELL Inspiron 15" 7000 Gaming, Windows 10 Home Version 21H1 (OS Build 19043.1237), Trend Micro Maximum Security 2021 (17.0.1333), Avast SecureLine VPN (5.12.5655), Windows Firewall, Unchecky 1.2

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88895
  • No support PMs thanks
Re: Removed or Not
« Reply #2 on: February 10, 2013, 01:22:49 PM »
Ran full scan JS:Scriptip-inf was found.  Scan log under actions could not be repaired.  Ran a boot scan in safe mode and found it again.  Started in normal mode avast log listed both finds and deleted the one under boot scan.  So is the problem fix in the normal mode or not

What was the file name and location of the detection ?

The boot-time and regular scans differ in what they scan and the depth of scan and that would account for the anomaly. You actually can't run a boot-time scan in safe mode, you might well be able to initiate it in safe mode, but it runs exactly the same as if it had been initiated from normal mode.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security