This morning on starting up my MS XP computer, I got the McSvHost.exe error.
In addition, co-incident with the usual password request the following MS notice appeared:
"McAfee Service Host encountered a problem and needed to close"
I have never seen this before nor have I heard of anyone else getting it.
What's going on?
Message was edited by: davideo0 on 7/16/10 1:46:27 AM CDTMessage was edited by: davideo0 on 7/16/10 2:15:51 AM CDT
I recently moved to McAfee. One -- and certainly not the most serious -- of the reasons was that I couldn't find a straight answer to a problem I was having at shutdown: often -- but not always -- the service SVCHOST.exe can't read memory and pops up an error.
Now that I've moved to McAfee, I get an error on shutodow: often -- but not always -- the service McVsHost.exe can't read memory and pops up an error.
You say tomato, I say tomahto.
Anybody know a reliable product?
You've brought up an interesting point, that multiple vendors run into this same issue. Unfortunately, while I do know a couple that have this (or similar) issues, I can't be 100% certain that *any* vendor won't have this issue.
Re similar cross-product problems, yup, it's just a fact of life: the questions was more or less sarcastic and rhetorical.
What I do find interesting is that neither vendor has yet nailed its problem: each prolem is long standing despite what I believe are sincere efforts to correct the situation.
I admit that I haven't read all 67 pages worth of posts (only the first two and the last three), so if this has been mentioned before, please forgive my ignorance.
The real problem with my installation is not that the error occurs on shutdown, but that it also occurs on restarts. Additionally, it breaks the restart; the screen looks just like an old DOS screen without a prompt: all black, with a blinking cursor in the upper left hand corner. I must physically power the machine down and reboot. If I'm in the room with the machine, it's inconvenient, but its a workaround. However, I will soon need to provide remote administration support to some machines in a "lights out" environment.
I'm worried that a lot more light might be needed to get things back up and running.
Well, I'm not a developer, so I can't answer why it hasn't been resolved yet. Because I'm constantly requesting status updates on the issue, I've seen some of the developers testing fixes though, so I know they're working on this issue at top priority.
Yes, in the previous pages we updated everyone with the info that this issue has multiple causes. We've identified 10 at this point (in addition to the 2 or 3 we've already released fixes for). The cause of the error is that a service is not closing in a timely fashion, causing the Windows shutdown to generate the error. The cause of that untimely closing is the issue we're working to resolve.
I also know we have 1 more cause fix in the bag. We were hoping it would be released at the end of June, but it's been held back just a bit for additional testing. On the upside, when it does go out, it's possible we'll have fixes for the other issues to release with it. Either way, each one we find and fix helps another 10-20% of the people affected (less than 1% of users).
Your issue on restart, however, is NOT what we're used to seeing. In fact, I've only had one other person report that to me, and they'd only had the issue once. Are you able to reproduce that? If so, we'd like to get some information from your computer. Better to be proactive with this sort of thing. Send me a private message, if you wouldn't mind, so I can get more detail.
Just to let you know that I have had one of your techs on the phone who appeared to do a very thorough job of downloading the relevant files for examination.
He also, I believe, carried out an adjustment or two, and on three restarts had, so far, no further errors either on start-up or close-down but I will, of course, be keeping a careful watch to see if it reappears.
I must say, I was impressed by the apparent determination to sort this problem out once and for all.
FYI since our last contact my prog has updated to Build. 10.5.194
You don't HAVE to download and reinstall, sorry if that wasn't clear. What Peacekeeper means is that when an updated version comes out, it can't go out to 40 million people at once. So what we do is stagger the download. A percentage of users will get the download each week, upgrading the entire customer base over time. Usually we upload the newest version to the account site so that new users get the newest version (no point in putting more people into the queue). By uninstalling/reinstalling, you can usually "force" the newest version to download.