Strange I will bring this up with the techs at our call Monday and see what They say. I have been using 2010 since September beta and only mcsvhost error was in first 2 days which was fixed. Have you checked the event viewer and see what error is shown if any?( Haven't had time to go back through 3 pages so my apologies if said previously).Message was edited by: Peacekeeper on 28/02/10 7:47:38 PM
Ok have just done some playing .... booted up, used no software and closed down 3 times and no errors.
Booted up and used Outlook, used no other software, then closed Outlook then closed down and got the error.
Coincidence! Can anyone else replicate this on Office 2010 or other versions.
Have just tried Outlook 2007 on another machine which has never experienced the shutdown error. After running Outlook it gave the error on shutdown.
Seems like this is the direction to look McAfee.
Sorry Jason, but it's not just related to Microsoft Office or Outlook. I don't run either of these but prefer to use Open Office and Thunderbird. I can bring on the error by running (on their own) Firefox or Windows Explorer or msconfig and others besides. Msconfig is my "tool" of choice for provoking the error. I've also carried out repeated restarts without running any application in between and don't see the error.
Peacekeeper, I'm sorry but there's nothing in Event Viewer logs.
I doubt the problem is happening on all XP machines otherwise McAfee would have seen it on their test beds (I presume!). I suspect it will be down to particular configurations of H/W, S/W and drivers etc. Incidentally, I've disabled all my startups without any improvement. So I do have some sympathy with McAfee who will have to fix a problem that they probably can't replicate. I've contacted Rahul personally (login and click on his photo) and offered to help if required. If McAfee are to get a handle on this problem they will need as much evidence as possible and so some of you may feel inclined to contact Rahul as well.
Have just used McAfee removal tool and removed all programs on shut down no problems everything went as normal. Then re installed 2010 from McAfee site on completion of installation I went and turned off computer guess what I had to force close due to this error. This was done on my lap top.
On my other computer that is running XP I have not had any problems since installation.
So as previously stated it does not appear to be affecting everyone.
This is an issue 2 weeks old as far as I can see. Yes mcafee will need to remote into some PCs to see if they can ascertain what is the cause. We will be discussing this issue tomorrow as well.
Re System Guard issue yes I was with that issue the whole time and what we found with the issue when I arranged techs to contact the users (or at least 10 of them) is that most were affected by malware or rootkits. There have ben no posts re this issue since then. But that is another issue we will sort this 1 out asap I hope.
I’ve got this problem on two XP Home PC’s. Here’s the quick story:
Got hit this weekend with a Coreflood!mem virus running McAfee 2009 Anti-Virus Plus (with a current subscription). I couldn’t get rid of the thing no matter which cleaning tool I used (tried over six-including McAfee's-Safe Mode or no Safe Mode). Decided to do a clean format, repartition, and install of XP. After applying all Windows updates, I downloaded and installed McAfee AVP, no other software had been added. After noticing the new UI, I uninstalled 2009 on another XP Home machine and downloaded the new version. Both PC’s now have this error upon shutdown. One PC with a clean XP install, the other one a much used XP machine.
Never had this problem with the 2009 UI version.
I’m also looking forward to the desktop icon removal in the next update!Message was edited by: Slick91 on 3/1/10 2:43:37 PM CST
If you want to remove the icon yourself I found this on this site :-
It works. Scroll down to the entry by RRIPPER.
I’m wondering if anyone who has this problem is also experiencing issues with the My Network erasing custom descriptions.
See this thread:
I wonder if when this error happens, it erases the network description changes as well due to the memory write error.