Jump to content

Scheduled Scan Failure


Recommended Posts

I am using Immunet Protect 3.0.8 Pro on Windows 8 Pro 64-bit, and I currently have no other antivirus programs running. Before I purchased immunet, I was running a free trial of Kaspersky, and before that, Windows Defender. I try to schedule a scan and a windows pops up that says "Error creating scheduled scan. An unknown error has occured.". I have attached a screenshot of the aformentioned window. I have tried scheduling the scan only to run when logged on, and to run whether I'm logged on or not. Any thoughts?

post-15300-0-49961000-1355524945_thumb.png

Link to comment
Share on other sites

Hi paul, there has been no input from an Administrator or Development as to if the 3.0.8.9025 version of Immunet was made compatible with Win 8. There was talk of making 3.0.8 compatible but if that was actually done I do not know for sure. I'm left in the dark about a lot of things. Here's something you can try though. Are you logged in and using your Administrator account when trying to create a scheduled scan? Also, Immunet does not support Fast User Switching so a re-boot is necessary if you change user accounts on your machine. Give that a try and let me know if this issue persists. Regards, Ritchie...

Link to comment
Share on other sites

Ritchie,

 

I'm currently the only user on this machine, and I do have administrator priveleges. I tried rebooting and attempting the schedule again, but it did not work. This seems to be the only feature not working with Windows 8. I had problems running a rootkit scan during my free trial, but that problem went away when I upgraded. If there is no way to set up a scheduled scan with Win8, I will just have to go in manually and run one weekly. Thank you for replying, and if you can, suggest to the devs that they add support for scheduled scans in Win8.

Link to comment
Share on other sites

Glad to hear you submitted a SDT Report and your future input will be apreciated. :-) Sorry to hear you had problems with agent.exe stopping. This seems to be an ongoing problem with a few folks as other forum members have reported the same behavior. Some people have reported the same thing, that uninstalling and reinstalling seemed to correct the problem. Mmm.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...