In answer to your question, there was nothing plugged into the USB port and the printer was off.
Yes , the error was the exact same one as all along. It came near the end of shutdown.
This begs me to ask the techs whether the fix was for all the 10 known causes. Will get back to youMessage was edited by: Peacekeeper on 16/08/10 4:33:59 PM
Since installing the "fix" about a fortnight ago I've had no errors but this morning I again had the McAfee error ON STARTUP!
It seems obvious that this problem is yet to be finally fixed. For god's sake let's go back to the previous version until McAfee finally debug this properly!
This is getting way beyond a joke!Message was edited by: davideo0 on 16/08/10 16:10:49 CDT
Stopping my e-mail notifications on this thread. Becoming beyond belief to just read all of this.
Computer Assoiciates Security Suite is great. I even like their site advisor better!!
Good luck all.
Those who are reporting a reoccurrance, please private message me your email addresses. I'm escalating you right away.
After installing the patch, I stopped getting the error. Yesterday I got an automatic update, and afterward I got the error message again.
After yesterday's update, the current builds are:
Security Center 195
This is kind of discouraging. Actually, that's an understatement.
I did receive an email from Dinesh with a request for contact info for someone to get in touch about the issue. I should hear something in the next day or so.
Actually your update did not update fully firewall should be 135 that is why the fix was not fixed. Why not fully is any1s guess see what the next upadte shows.
That was a result of the mod call. They want to figure why you still have it.
Remember Security centre 195 build firewall 135 build is required.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: