Jump to content


  • Posts

  • Joined

  • Last visited

About steveshank

  • Rank

Profile Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm still having this issue. It is in an infinite loop trying to update to 14.0.22 from the useless 14.0.21. I've tried clearing the update cache. I've tried to return to earlier version. It just keeps asking me to update to 14.0.22 then asking me to approve (UAC) and then asking me to install update again. Windows 10 1909
  2. I posted to this forum because this is the product those clients are using. Anyone can check this issue for themselves. Put nod32 antivirus (any version for the last 2 years), on a computer. Don't worry about the Windows version, it doesn't matter. Schedule a scan say at 2am on Tuesdays. Only access that computer via network. Do not touch the mouse or keyboard. Check it a month later. The scheduler will report that the scans ran. The logs will not show that any scans were done. The computer does not sleep or hibernate, I always turn those off. Usually these computers are very busy as file servers and running accounting software, but they are not Windows servers, just peer to peer attached file servers. So far, I've been unable to get an answer from Eset on whether the logs or the scheduler was correct or how we find out if malware was found. Other scheduled software runs, backup software, imaging software, off-site backup etc. This issue is reproducible and has been for a couple of years.
  3. I have noticed on multiple clients that when I go into their computers to check, despite weekly scans being turned on and the Windows 10 computers being left on, no record is made in the scan log. This has been occurring for years with all computers which do not have someone sitting at them moving a mouse or typing. So, all peer to peer file servers do not record a scan log. This also occurs if a client leaves on a vacation for a month or two and leaves their computer on. I used to think it didn't scan, however, when I check the scheduler, it gives a correct time for the last scan. So the scheduler says it runs, but the logs say nothing was done. Again, this is absolutely consistent and reproducible. Will Eset ever deal with this long lasting issue and is a scan being run or not? If it is being run, how do I determine if the client is getting viruses and they are being cleaned with no log recording?
  4. I setup weekly full drive scans. When I look at scan logs, It shows the last run was on July 23, with log records for many previous weeks. It is set to run every Tuesday at 3AM. However, there is no log for July 30, Aug 6 or Aug 13. Prior to that there were logs for every week. I never turn the computer off. When I look at the scheduler, it says the last scan was on Aug 13. So, was it run then and no log made? or was it run and failed? The event log doesn't seem to record scans. I can find no log of a failed run. So what is happening? Is the scan not getting run, and a log not being recorded, or is the scan not getting run, or started and failing?
  5. I had the same issue, but will simply live with the flashing alert until (if) Eset figures out what they did wrong. Uninstalling can create really big issues with the network stack etc. Usually it works, but uninstalling an antivirus is not like uninstalling a regular program.
  6. Exactly what information do they need? Is it the same in USA? I managed to find a phone number in North America and will collect the necessary information from the very old rather senile lady and call for her, but want to make sure I have all the necessary information before I call.
  7. Sadly, this is not always true. I have 30 or 40 there and have turned off those autorenews, but just ran into 2 instances in the last month where it didn't function: 1. I renewed a client's license from their computer, but this renewal didn't get posted to my account. so I couldn't turn off auto-renew. 2. An elderly client purchased the product on my recommendation and doesn't have any idea what if anything her "other sales purchasing" account might be. I'm thinking she did something like a guest account purchase. Last week I requested explicit instructions for how to turn it off when you don't have it posted to an account. I have not heard back. What I want - short of Eset fixing what I consider unethical practices, is something that says, Send this information to this email address and we will take care of it and let you know it is done. It will be reflected in your program.
  8. I agree with chelseaboy. The fact that you are on the Eset staff and do not know what auto renew is, is illuminating. The suggestion you give that I should give you a screen shot of what does not exist (a way to turn off auto renew) is also illuminating. I submitted a support ticket and was told they turned it off for me on the account I renewed. The other client who recently purchased the product, is still stuck. I replied back to the tech support person asking exactly what information needed to be on a support ticket to turn off auto renew. I will then submit another support ticket for the client who recently purchased the product. Will post the answer here so people know what to put into support tickets to turn off auto renew. I've got over 100 clients in nod32, but will be switching to some company that doesn't require a phone call or tech support ticket to hopefully stop them from continuing to charge a credit card if the client dies or switches products.
  9. I recently renewed nod32 for a client. It turned on autorenew by default. I don't want it on. It is not showing up in my account with about 40 other licenses. How do I get it off? Another client recently purchased nod32. Auto renew is on. She wants it off. She didn't create an account. How does she get auto renew off? It should not be so difficult to stop you from taking money from us when we don't want you to. It feels unethical. There should be a button to cancel auto renew in the program or a right click or something simple. At least you should have made it opt in. Turning it on by default and not making a clear simple way to turn it off is very bad.
  10. This problem has surfaced on another computer. I have about 100 computers I manage with nod32. 2 of them are file servers. Not actual real servers, just file servers that are not used by a local person, but rather by a few users who save files on it. Of the 100 regular computers, none have a problem running weekly deep scans. Both of the file servers will not run weekly scans. One of them has mirrored ssd but the other is just like the regular computers I sell, except it has no local user. As soon as I login remotely, it begins to update and work. Otherwise, when people only save files to it, both of them fail to scan or update. This is a fairly new problem. Hopefully this can get forwarded to programmers so they can fix it. Does anyone have nod32 on a file server computer and have it working?
  11. Thanks. I'll pursue that. It actually makes the most sense, better than anything I thought of.
  12. When client goes to ESPN.com in Chrome nod32 pops up with this: ?Time;Scanner;Object type;Object;Threat;Action;User;Information;Hash;First seen here 8/11/2018 2:27:33 PM;Real-time file system protection;file;C:\Users\tgera\AppData\Local\Temp\scoped_dir3176_28404\CRX_INSTALL\contentscript.js;JS/Spigot.B potentially unwanted application;;;Event occurred on a newly created file.;D20F48CCD77BF42AB6E8FA3532DDF7F70951275C;8/11/2018 2:27:15 PM When I look in the temp folder with all files and system files showing, the offending file and folder is not there. Closing rebooting etc. does nothing. Cleaning does nothing. The pop repeats 3 times. The issue does not occur with Edge, or Cliqz (a Firefox derivative). We have removed all but the simplest Chrome extensions (google docs and sheets). We have rebooted. Client is retrieving his key, so we can uninstall and re-install. Is that the answer? It seems to me that when Chrome hits that site it triggers something that didn't get turned off, so after the first protection, it continues despite having removed the threat.
  13. I submitted this to tech support, and linked to here so they can see what we've tried. An odd thing occurred though. I wanted to give log files, and I chose All files, but it was 43 meg with a 30 day limit. Eset refuses uploads above 8 meg, so I tried 5 days. It was also 43 meg and couldn't be accepted. I'm thinking that is pretty large for 5 days of log files, and why would there be an 8 meg limit if that was normal? This makes me think something is wrong with the log files which you had originally hypothesized. I'm going to investigate clearing the log files, but which ones? Where? time is ok in Windows. Haven't gone to client office to check BIOS, but everything else seems to run fine including other scheduled tasks.
  14. Tried to uninstall before doing a re-install, but program suggested I do a repair. It "repaired" Nod32 and I made a brand new scheduled task to scan late last night. Once again, no even was recorded for 24 hours from yesterday afternoon when I did this to when I re-entered this afternoon. No checks or updates or anything, until I checked back in, then it did the updates. Does anyone have any idea how this could happen?
  15. The filtering isn't the issue as filtering is not on and the items show when I check. I'll re-install. Running a scan manually now. The clients have this computer running as a file server in the basement in a locked room and really never go down there.
  • Create New...