Individual File Scanning Doesn't Work Anymore

[qwerty123]

I don't know when this started*, but I just noticed that right-click scanning individual files doesn't work anymore. Nothing happens, whether the Immunet client is visible on screen or not.

I then updated to 7.0.2.11454 and rebooted.

No change, individual file scanning doesn't work.

A workaround is to go to Scan Now, Custom Scan, and find the folder or file you want to scan. This still works.

I'm running on Windows 10 Enterprise 2016 LTSB. My system has not changed in a long time so there shouldn't be any interference. I also very rarely install anything new that might have interfered.

*I scan individual files relatively frequently, maybe ever few weeks/monthly. So the issue is relatively recent.

Edited December 26, 2019 by qwerty123

[ritchie58]

Hello qwerty123,

I just checked the right-click Context Menu Scanner and it seems to work just fine for my copy of Immunet. I scanned my Firefox add-on settings backup folder and some of the individual files in the folder with no problem (see images).

There is a "minor bug" with the Context Menu Scanner though. It doesn't display the elapsed time it took for the scan to complete. That bug has been around for some time.

Have you tried to do a clean uninstall & reinstall to see if that corrects the issue? If not, give that a try. When asked by the uninstaller if you plan to install Immunet again choose the "NO" option and proceed with the remainder of the uninstall.

After reinstalling you will have to reconfigure the Settings to what you had and re-add any Exclusions you may have been using.

Let us know if a reinstall doesn't correct the issue. We may have to dig a little deeper to see what's going on.

Regards, Ritchie...

 

[ritchie58]

I can think of another question. Are the files that seem to not be able to initiate a Context Menu Scan located in a different drive other than your OS C:\ drive?

[Rob.T]

IN  7.0.2.1454 you'll only see  a popup detection message if anything malicious  is actually detected.   So nO news is good news.

 

If you open the main immunet dialog on screen and then right click ->  scan a directory with a lot of files in  it:   the "Scan now" button  in the main Immunet dialog will change to just "Scanning" while the scan is in progress.    And if you click on it at this time it'll open up the scan progress window. 

This also happens when you scan just a single file but often the button text changes so quickly it's hard to see.  It goes from "Scan now" to "scanning" and back to "scan now"  in ~half a second or so.

 

[qwerty123]

On 12/27/2019 at 6:25 PM, ritchie58 said:

I can think of another question. Are the files that seem to not be able to initiate a Context Menu Scan located in a different drive other than your OS C:\ drive?

You nailed it, it's not working on my D drive. Files on my C drive Context Menu Scan just fine.

Since I have a workaround I can't be arsed to reinstall, if that turns out to be the only solution.

Edited January 23, 2020 by qwerty123

[ritchie58]

Hello again qwerty123,

A uninstall & reinstall is not a fix-all solution for everything of course, lol! I just wanted to make sure your copy of Immunet wasn't corrupted some how.

Is your D:\ drive physically connected to your motherboard via SATA cable or is it an external drive connected to a FireWire, USB port or perhaps a SD (or other) card reader?

Hi Rob,

Perhaps I should have been more articulate.

If you scan a folder with enough files using the right-click Context Menu Scanner the elapsed time will be displayed but it reverts back to 0:00 after the scan has completed. The elapsed time shouldn't just disappear like that after the scan is done In my opinion. I still consider this a not mission critical "minor bug" that I hope can be fixed in a future build.

Cheers, Ritchie...

[qwerty123]

On 1/23/2020 at 6:14 PM, ritchie58 said:

Is your D:\ drive physically connected to your motherboard via SATA cable or is it an external drive connected to a FireWire, USB port or perhaps a SD (or other) card reader?

It was the first PC I built so details are a little fuzzy, but whatever the typical setup is. So surely connected to the MB via SATA.

C drive is a SSD (Immunet is installed here)

D drive is a regular HD

Edited January 28, 2020 by qwerty123

[ritchie58]

Thanks for the additional feedback qwerty123!

I'm not unfamiliar with building a rig from scratch.

Letting me know that the D:\ drive is a HDD & not a SSD was very helpful! That would have been my next question.

I think I have a good extrapolation what may be causing this behavior as I was able to reproduce it after some experimentation.

I have a couple of HDD drives connected via SATA to the MoBo besides the C:\ drive on my current rig. I also use the Windows energy saver settings. If, after boot-up, a drive is not accessed within the specified time Windows will automatically turn off that drive to save power & needless wear & tear. Some MoBos have similar hardware based BIOS settings too.

If you attempt to conduct a Context Menu Scan with Immunet and that particular HD disk is not already spinning at normal speed then it is possible that Immunet cannot access that drive before the disk has a chance to spin up to speed. If the drive is already spinning at normal speed then a CM scan will take place regardless of the drive letter has been my observation.

P.S. - With your 10th post you are our newest official forum "member" and no longer a newbie! Congrats on that bro!

Regards, Ritchie...

 

[qwerty123]

On 1/28/2020 at 6:39 PM, ritchie58 said:

I think I have a good extrapolation what may be causing this behavior as I was able to reproduce it after some experimentation.

I have a couple of HDD drives connected via SATA to the MoBo besides the C:\ drive on my current rig. I also use the Windows energy saver settings. If, after boot-up, a drive is not accessed within the specified time Windows will automatically turn off that drive to save power & needless wear & tear. Some MoBos have similar hardware based BIOS settings too.

If you attempt to conduct a Context Menu Scan with Immunet and that particular HD disk is not already spinning at normal speed then it is possible that Immunet cannot access that drive before the disk has a chance to spin up to speed. If the drive is already spinning at normal speed then a CM scan will take place regardless of the drive letter has been my observation.

Thanks! That sounds very likely to be what's going on. My D:\ indeed has some sort of energy saving/sleep thing. I hear it spin up every time I access it (which is pretty rarely, it's just my data drive).

I guess there's nothing Immunet can do about that?

[ritchie58]

Something you could do is just click on a file or folder (that you know is safe) in that particular drive to get the disk up to speed and then run the CM scan of the file you're interested in.

Immunet needs to adjust the time it takes to recognize if an error has actually occurred or not concerning a Context Menu Scan with different drives. That would definitely get my vote if that was looked into & included in a future build!
 

Cheers, Ritchie...