Jump to content

Archived

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

Gourcuff

Virus Scanner Initialization Failed

Recommended Posts

Hi. I keep getting this message, see pictures. I have nod32 running on XP. I'm running windows firewall alongside the Anti-Virus. There are no other programs it could conflict with. I have tried Google results, re-installing Nod32 with no joy. Please help

post-2724-0-91916700-1389450775_thumb.gif

Share this post


Link to post
Share on other sites

Make sure the date and time are correct on your computer and try running the Uninstaller from safe mode and then reinstall.

 

How do I manually uninstall my Windows ESET product?

 

Please make sure your services are running too. The following should be running : How do i open Services ?

ESET Service

Security Center

Background Intelligient Transfer Service

Windows Management Instrumentation

 

Let us know if the Uninstaller works ? :)

Share this post


Link to post
Share on other sites

Hi Arakasi,

 

I didn't have Background Intelligent Transfer Service on. I have now turned that on and will let you know if it happens again. I didn't uninstall/install the product again.

 

Thanks

 

Gourcuff

Share this post


Link to post
Share on other sites

Sounds great.

I would restart and then check if the service turns itself back on after you log in.

:)

Share this post


Link to post
Share on other sites

Done. I've set it to start up automatically. No problem so far :)

Share this post


Link to post
Share on other sites

bad news :( the message is back, same as the attached image in the first post. Restarting the computer gets rid of the message, all is running well after a restart but it does come back up after a while

Share this post


Link to post
Share on other sites

Will the message appear if you close egui via Shift+click on X and start it again from the Start menu? Does the error occur every time you start Windows? Are you able to start an on-demand scan without getting an error?

Share this post


Link to post
Share on other sites

Hello Marcos

 

I just shut down nod32 via your instruction shift+X and yes the message remains there when starting up again via start menu.

 

The error does not occur from the get go every time I start windows, its a real hit and miss sort of thing, it happens whenever it wants to, it has a mind of its own.

 

I can start an on-demand scan, smart scan without being told I cannot. the error message on the main page still remains there though

 

Thanks

 

Gourcuff

Share this post


Link to post
Share on other sites

Hello. Theres been a development today... The same thing has happened BUT when I click on update manually and it updates the error goes away, maximum protection is back but again after a while the error comes back

 

Thanks

 

Gourcuff

Share this post


Link to post
Share on other sites

Hello. Just an update. Everytime the error appears I click on update then update now and the program updates then the error disappears. Please can ESET fix this.

Share this post


Link to post
Share on other sites

This is still happening. I've not got a response from ESET Support neither. Whats going on ?

Share this post


Link to post
Share on other sites

Hi Gourcuff,

 

Yesterday i saw the same issue happening to my Sysrescue on 2 different systems.

They both had a rootkit. Removing it solved the issue and allowed the scanner initialization to complete.

 

I doubt that is what is going on here, because ESET detects rootkits, but if you would like to humor me, try this:

hxxp://usa.kaspersky.com/downloads/tdsskiller

I use that tool religiously at work removing rootkits.

 

Try this tool as well :

hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3035

 

If that doesn't help then it is probably what we originally thought, configuration issues. :)

Share this post


Link to post
Share on other sites

I'd suggest contacting Customer care who will instruct you how to create the necessary logs and will pass them to engineers for analysis.

Share this post


Link to post
Share on other sites

Hi Gourcuff,

 

Yesterday i saw the same issue happening to my Sysrescue on 2 different systems.

They both had a rootkit. Removing it solved the issue and allowed the scanner initialization to complete.

 

I doubt that is what is going on here, because ESET detects rootkits, but if you would like to humor me, try this:

hxxp://usa.kaspersky.com/downloads/tdsskiller

I use that tool religiously at work removing rootkits.

 

Try this tool as well :

hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3035

 

If that doesn't help then it is probably what we originally thought, configuration issues. :)

 

Run both tools. Kaspersky found nothing. ESET done its thing and found no rogue.

 

I'd suggest contacting Customer care who will instruct you how to create the necessary logs and will pass them to engineers for analysis.

 

I did email them but I've had no response. I emailed when I created this thread.

Share this post


Link to post
Share on other sites

I did email them but I've had no response. I emailed when I created this thread.

 

Did you receive an automatic response that a ticket with a specific ID was created? Please pm me your email address so that I can ask the UK distributor if they received your query and a ticket was created in their system.

Share this post


Link to post
Share on other sites

Hello Marcos. I've PM'd you the ticket number and my email address.

Share this post


Link to post
Share on other sites

I think I found the problem. I found a problematic RAM module which has been replaced. There has been no problems since then.

Share this post


Link to post
Share on other sites

Oh so it was hardware related even, great job  :)

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...