the virus is seen as bagle.km by Nod32...but it didn't catch it when it got installed...:S

I'm trying to run a removal utility from eset but it's too slow...coz winlogon.exe uses up 99% cpu..

any manual removal?

Click to expand...

Well , there are some variant of Bagle with rootkit behaviour which can disabled NOD32 if it is uninstalled before the malware appears . But I know for NOD32 v2 . This doesn't apply for v3 products ,AFAIK.