McSvHost.exe causes error on Shutdown

[Peacekeeper]

Ok no usb printer still turned on when you shutdown?

Will pass this on tomorrow in our meeting call

Ajmitch

UK amd US only started throttling late last week. It will take a bit to get it.

[celtkub]

In answer to your question, there was nothing plugged into the USB port and the printer was off.

[jmckee]

Yes , the error was the exact same one as all along. It came near the end of shutdown.

[Peacekeeper]

This begs me to ask the techs whether the fix was for all the 10 known causes. Will get back to you

Message was edited by: Peacekeeper on 16/08/10 4:33:59 PM

[davideo0]

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

[tmgrl4]

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.

terri

[SPyron]

Those who are reporting a reoccurrance, please private message me your email addresses. I'm escalating you right away.

[jmckee]

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.

[Peacekeeper]

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.

[cburrows]

     When posting to this thread the last time I told myself that I was not going to bother posting to it again and just let all the geniuses at McAfee work their problems out.  Builds 191 & 131 that I am running now seems to eliminate the McSvHost.exe error most of the times (1 out of every 20 shutdowns) when I turn off my XP computer and I told myself that I can live with that. 

     Then back about 30 posts ago I got very excited after reading that they have got the fix and it was being tested and was going to be released to everyone as builds 195 & 135.  I still don't have the 195 & 135 builds that is suppose to eliminate the problem and from what I am reading I am not sure that I want it yet.  I am pretty happy compared to the way the problem used to be before builds 191 & 131 (McSvHost error almost at every shutdown) but was just curious as to why I still don't have the 195 & 135 builds yet?  You said many posts ago that everyone in the US should have the fix within the next couple of days.  I AM IN THE US AND STILL DON'T HAVE IT.  Thank you!