McAfee Stinger is also clean.
I am increasingly suspicious that this is a software conflict...maybe with an Adobe product as mentioned above.
I am disappointed that geoperkins problem has come back despite the 'scrubbing' of the user profiles etc.
Come on McAfee sort this out!!
I've been away from his thread for awhile (that pesky Christmas thing .....)
I haven't gone thru everything, but I see some notes about "registry cleaners"
For what it is worth, about three weeks ago, in desperation I went to Microsoft, and used their scrubber on the Registry. It reported many things, and I let it do its thing. I was desperate.
Immediately afterwards, the number of Not Protecteds dropped dramatically, but did not go away completely.
About a week aftewards, they stopped compleletly.
I hvae not had ANY Not Protecteds for 2-3 weeks.
I cannot really point to anything else
I would throw the computer in a landfill before I contacted Tech Support, oh the pain ...............Message was edited by: saty on 12/28/09 2:39:52 PM CST
Hmmm. Yes the pattern on my system is that McAfee always stalls while real-time scanner is (apparently) stuck whilest "Object being scanned = \Device\HarddiskVolume3\Program Files\NOS\bin\getPlus_Helper.dll by C:\Windows\system32\services.exe" (according to the message contained in the application log). Thanks for the tip in this thread, I uninstalled the Adobe Download Manager (which uses the NOS\bin\getPlus_Helper.dll). This will have a consequence of requiring I manually download my updates to Adobe Acrobat Reader. I don't know yet if Adobe will automatically re-install this component...
I also went to Microsoft's OneCare site and did the free "CleanUp" scan. No viruses or other malware detected. OneCare did complain about 317 unnecessary registry entries (these apparently not removed by McAfee's own QuickClean utility, which I have used previously, nor removed by the McAfee paid service). I took the recommended action and am rid of the registry deadwood.
Now the question is, will the above two steps eliminate McAfee's real time scanner service from stalling out for 90000ms and being terminated by Windows? I shall monitor this and report back to this thread what I learn.
Meanwhile, it would be interesting to know McAfee can explain why the real time service is (apparently) incompatible with the Adobe download manager program NOS\bin\getPlus_Helper.dll ????
I repeat can any of the other users that have this issue confirm
1 they have the file mentioned above and
2. The event log says the scanner locks on the same file
This is urgent as we are having a call tomorrow and I would like to enlarge on what we have found so far.
geoperkins can you show the others how you got the log please. My Win 7 event log is slightly differentMessage was edited by: Peacekeeper on 30/12/09 8:53:42 PM
I am just stupid or am I looking in the wrong place for the logs?
I am looking in SC - View Recent Events - View Log
But most of my logs report "No Log Exists"
Which log should I be looking in? ScriptStopper log?
It is I think the windows event viewer That is why I reasked geoperkins .
Right click on My computer or computer on desktop and choose manage and event viewer and check the logs there. I am not an expert in event viewer so I will await a post explaining where the error is detailed.Message was edited by: Peacekeeper on 30/12/09 9:01:37 PM
The Windows "Event Log" is indeed the location you need. Windows Vista and XP should have similar access. No ideas for Windows 7, although it also should be similar.
For Windows XP, the sequence to access is:
1. Right-click on "My Computer" (or, "Start ---> Administrative Tools", if in your "Start Menu")
2. Click "Manage"
3. Expand "Event Viewer" (click on the "+")
4. The log entries needed are in two (2) locations: "Application" and "System"
5. The entries under "Application" will have a source of "McLogEvent", and should be proximate to and "Error" entries.
6. The "System" log entries are created by the Windows Services management. Locate entries with a source of "eventlog" (these are created at Windows shutdown and boot-up. The failing service entries should follow (actually, precede, since the order is recent to first ).
7. To view any entry in either of these logs, right-click on the entry and click "Properties".