Scheduled Scans Not Occurring - Not Getting Any Error Messages Either

[josh@diversakore.com]

Hello, I am running the free version, 5.0.2.10301, on 4 different servers, all running Windows 2012 R2.  The program installed fine, and manual scans run fine.  I have never received any error messages.  I can also successfully create a scheduled scan with no errors.  However the scheduled scan that I create never runs.  It also does not appear in Windows Task Scheduler (I read somewhere in another post that Immunet utilizes Task Scheduler for scheduled scans.)  I have tried creating and recreating scheduled tasks a half dozen times on all four servers, but none of them ever run...and none of them show up in Task Scheduler.

 

I would have assumed this was just a random glitch, and that simply re-installing might fix it...except for the fact that it's happening on 100% of the servers I am running Immunet on (4 out of 4).  Doesn't seem like a random glitch.

 

Any ideas?

 

Thanks.

Edited September 1, 2017 by josh@diversakore.com

[bcouncil]

Hello, 

 

Can you please check your PM for a follow on this issue. 

 

Thanks, 

Christine

[josh@diversakore.com]

To any users having similar problems:  Immunet support never responded to with even an attempt at a solution to this issue, despite me directly emailing one of their support reps multiple times.  I took it upon my self to continue to troubleshoot to no avail.  I then removed version 5 and upgraded all my servers to 6.0.2 as soon as it was released, only to have even more problems.  The only problem I had with v5 was that the scheduling would not work.   Version 6.0.2 however crashes/freezes constantly on my Windows 2012 R2 servers.  Restarting the Immunet service doesn't fix the problem, you actually have to restart the whole server, or in some cases completely reinstall.  The hours/days of my wasted time trying to get make this free solution work could have easily paid for a solid commercial solution by now.  Lesson learned. Moving on.

 

To Immunet:  1) If you are serious about building a customer base, you need to do a much better job responding to your customers' support requests.  2) You need to do extensively more quality control testing on your major releases.  The fact that 6.0.2 crashed repeatedly (even after several uninstall/reinstall attempts) on 4 different newly installed 2012 R2 servers is ridiculous.  If you want to be taken seriously, stop releasing software that is not fully tested.

Edited September 20, 2017 by josh@diversakore.com

[bcouncil]

Hi, 

 

Could you please PM me if you're still interested in resolving your issue? I couldn't find any additional communication from you recently in our support inbox, but we're happy to further look into your issue.

 

-Christine 

[ericalj]

I have this issue as well and have had it since I've installed it, and it's very frustrating. \I've tried so many different things to try to ensure it runs...but it's never run. I've made sure it's updated, and had hoped an upgrade would fix it.

[ritchie58]

Happy New Year ericalj, have you updated to the newest 6.0.8 version yet?

If not could you uninstall the old version first, when asked by the uninstaller if you plan to reinstall Immunet choose the "NO" option and proceed with the remainder of the uninstall. This will delete all your old history files & settings configuration so you'll have to reconfigure your previous settings and add any exclusions you were using plus re-create a scheduled scan.

Even if you're using the newest version a clean uninstall & reinstall is still worth a try I think. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe

I did a clean install of 6.0.8 not long ago and the scheduled scan feature is functioning properly for me. I have it set up to do a daily flash scan.

[ericalj]

Yes, it's updated. I have previously tried the uninstall/reinstall in an attempt to resolve this but I guess I'll try that...again.

[ericalj]

And I still have this issue...despite having done the clean install yet again. I've never had automatic scans work at all. Additionally, now, I go to look and it regularly says that it's never been scanned.

[ritchie58]

There definitely seems to be a recurrent theme of issues with Server 2012 R2 and Immunet being reported of late.

[Guest]

It is July 20, 2018. I suffer from the same issue. Scheduled scans do not run leading to orange danger warning on main panel. Manuel quick scan clears it up. Manuel scans are all that have ever worked for me.

And, to be honest, I have zero faith in Cisco responding to this in any kind of a timely manner. I highly suspect the reported numbers of users is much smaller. A quick tour around the site here shows almost no activity. And by "responding" I MEAN FIXING/CORRECTING. NOT replying with chants, spells & black magic to try as a work around.

I still don't trust this software. It is STRICTLY backup only.

And there still is no way to edit the ever growing file history. I delete quarantined items after verification with other software and the red "X" changes to a green check but nothing changes with the file. There is a "Clean History" option that does nothing. The damned file is still there. I want to remove oldest entries (ALL OF THEM!) & keep the most recent ones.

The only choices we have are to develop work arounds on our own. I run a manual full scan at the end of my day. Scheduled scans are relegated to my other software that works.

Someday, I will hunt down the history file and use an editor to manually remove the crap collecting there.

Seems the only REAL purpose for this "freeware" is to collect & build the malware database for the paid version. I am sure the reporting function works perfectly.

Operating System
    Windows 7 Home Premium 64-bit SP1
CPU
    Intel Pentium P6200 @ 2.13GHz    49 °C
    Arrandale 32nm Technology
RAM
    4.00GB Dual-Channel DDR3 @ 532MHz (7-7-7-20)
Motherboard
    Acer Aspire 5733Z (CPU)
Graphics
    Generic PnP Monitor (1366x768@60Hz)
    Intel HD Graphics (Acer Incorporated [ALI])
Storage
    465GB Western Digital WDC WD5000BPVT-22HXZT1 (SATA)    35 °C
    232GB Seagate External Drive USB Device (USB)
Optical Drives
    HL-DT-ST DVDRAM GT32N
Audio
    Realtek High Definition Audio

 

[Guest Wookiee]

Hey,

 

I don't know any black magic, chants or spells- but there are a few things to check. Is your system date / time correct?
Has this ever worked for you?

I 100 percent agree, that the only work arounds that should be given are to temporarily fix an issue, before a patch comes out to actually remediate the problem. Since I am newer on the Immunet team, I will address all of your concerns. I apologize for this, as I wasn't aware this was still a problem for some folks, as this post was older and before I started.
No excuses though, I will run some tests on my end and see if I can't fix it in a timely fashion. I might PM you a few questions on the box, if I can't easily replicate the issue.

[Guest Wookiee]

I checked on Win 7 and 10. having no issues as long as the system clock is set. Though, if the computer is asleep, the scheduled scans will NOT run also.

Was the machine possibly asleep, when the scan should of kicked off ?
 

[ritchie58]

Wookiee is correct. In order for the scheduled scan to perform at the correct time you need to make sure that not only is your Windows date/time settings correct but also your "PC's BIOS date/time settings" are adjusted correctly as well. The BIOS date/time should correspond exactly with what Windows date/time is showing. If there is a deviation then something definitely needs adjusted.

[Guest]

Nothing out of date or wrong with my system. Clocks, calendars, etc all reading in this century. Better more up-to-date system than the mainframes used by the Dems & Repubs. Only one piece of software that I have had some kind of problem with from day one. I mean day one. Still have that first release on another computer in my backroom. 

I deleted my auto scans. Set it up to do the simplest thing possible. Daily quick scan at 6:00am. So far, it has managed to complete this. Just the one entry. There were 3 before to do a full scan of my "C:" drive every other day. Do that manually I guess when I remember before going to bed.

Another problem with the clean files option in history. It does seem to clean all but very last date but screws up the EOF. Every time I clean the files & scroll down to bottom of display to check for oldest date still left, it crashes. Attaching screen grab for you. Got the emails. None of the magic suggestions worked. Along the lines of those suggestions, it won't work when the computer is turned off either. Just say'n...

 

Edited July 29, 2018 by Guest
correction; addition...

[ritchie58]

Thanks for the update John. I also use the daily scheduled Flash scan and never tried to add another scheduled scan myself. Maybe there is a limitation on how many scheduled scans can be implemented that I'm not aware of.

I have also seen that behavior before too, where Immunet's GUI will crash if you scroll down the list of entries too quickly.

[Guest]

No limitations mentioned or enforced by the software. It allows the multiple creation of custom scans. It just does not execute them.

Where is the warning for this speed limit on scrolling?

Sounds like "problems" to me. Bugs. Means a lot to users when staff admit experiencing these long term problems and yet, they still exist.

Just say'n.

 

 

[Guest Wookiee]

Every software has bugs, the point of reporting these issues is so that we can fix them.
Immunet bugs go through ME now, I have only been on this project for a short time. I am trying to FIX any and all problems reported. Though, this will obviously take time to find WHY something is not working right.

Now, if you want to enable debugging, and wait for the scheduled scan to not kick off again- then generate a support dump, and send it in- I can look at fixing it.

[Guest Wookiee]

Keep in mind, Flash scans (if that is what you are doing)-

Flash Scan - Scans registry and system process that are in memory to determine which files to scan on disk.

If you don't have anything in memory process wise, it will look like it doesn't scan. I DO see that the "last scan" date DOES NOT reflect a flash scan (i'll ask dev as to why this is, and or to fix it).

Though, I am testing FULL scheduled scans to make sure that  A) it is updating the time stamp for "last scan" and B ) doing a full scan.

[Guest Wookiee]

Now, the full scan DID launch (run) and I am waiting for it to finish to see If the "last scan" time stamp does indeed adjust.

[Guest Wookiee]

The scan completed, and the

DID update, just not to the correct time... I'll submit a bug for this.

[Guest]

3 hours ago, Wookiee said:

On 7/28/2018 at 9:49 PM, ritchie58 said:

Thanks for the update John. I also use the daily scheduled Flash scan and never tried to add another scheduled scan myself. Maybe there is a limitation on how many scheduled scans can be implemented that I'm not aware of.

I have also seen that behavior before too, where Immunet's GUI will crash if you scroll down the list of entries too quickly.

 

6 hours ago, John_3_16 said:

No limitations mentioned or enforced by the software. It allows the multiple creation of custom scans. It just does not execute them.

Where is the warning for this speed limit on scrolling?

Sounds like "problems" to me. Bugs. Means a lot to users when staff admit experiencing these long term problems and yet, they still exist.

Just say'n.

 

 

Every software has bugs, the point of reporting these issues is so that we can fix them.
Immunet bugs go through ME now, I have only been on this project for a short time. I am trying to FIX any and all problems reported. Though, this will obviously take time to find WHY something is not working right.

Now, if you want to enable debugging, and wait for the scheduled scan to not kick off again- then generate a support dump, and send it in- I can look at fixing it.

My last post was in answer to ritchie58's post. If you have a desire to get testy & get your panties in a knot, do it with him. He has been here for nearly 2,000 personal posts. And he stated he has experienced some of these "bugs".

My honest opinion, I don't give a damn either way. Fix it. Don't fix it. Life for all of us will go on till it doesn't. I will sleep & eat just fine.

I noticed the date of the 1st. post in this thread. Over the years one can certainly visualize the timeline of ownership changes with Immunet. Earliest years were the best for communication & cooperation. We were needed then as the 1st. release was in development. We helped test it & debug it. The feedback was appreciated. A couple of rungs later up the time ladder & we are, at best, a nuisance.

You need some more feedback, talk to ritchie58. You two have the answers. All I have are questions.

Goodnight.

[Guest]

2 hours ago, Wookiee said:

Keep in mind, Flash scans (if that is what you are doing)-

Flash Scan - Scans registry and system process that are in memory to determine which files to scan on disk.

If you don't have anything in memory process wise, it will look like it doesn't scan. I DO see that the "last scan" date DOES NOT reflect a flash scan (i'll ask dev as to why this is, and or to fix it).

Though, I am testing FULL scheduled scans to make sure that  A) it is updating the time stamp for "last scan" and B ) doing a full scan.

Sorry. I was under the impression that if the computer is on with the OS running then there are plenty of processes running as well & if it is up then the registry is ALWAYS available. At least based on my version of process hacker & Win7. And my computer is not set to sleep or hibernate. Screen goes dark after 15 minutes w/o a keystroke. Tap any key & the screen reappears as it was. Guess me & my computer MUST be doing something else wrong, huh?

[Guest Wookiee]

Again, I am trying to Fix and understand the issue. I cannot reproduce the issue as per you described. I am not saying that it is user error, I am just trying to re-create the issue so I can understand it better.
We will need debug enabled, and a support generated file- to troubleshoot.