After downloading 2010 on that fateful Wednesday, my pc crashed during a virus scan the same evening. In the end had to get my PC looked at, reformat and re-installed windows advised and then carried out. When PC returned I reinstalled wireless internet connections then McAfee. After the reinstall I was occasionally getting the message on closedown BUT not for the last seven days now (TOUCH WOOD). I seem to be okay now, I have submitted a claim and waiting for a response (thanks for letting me know peacekeeper - appreciated).
Hopefully this matter will be resolved soon for all.
Regards to all
Am I missing something,
I had to have a complete reinstall I then downloaded the Beta version so I had a fresh windows xp and the latest McAfee but I still get the close down error,
also How do I get my repar bill refunded ??? as no comunication has come from McAfee.
Beta still has the issue Steer_pike said they are working on it. BTW he is our Tech we talk to daily and he has been updated on this thread daily as well. Re refund/costs form on main site but atm US/ Canada only. Will take a while but they will honor their commitmentMessage was edited by: Peacekeeper on 13/05/10 6:54:03 AM
Currently I have had no major problem with the shutdown error other than its annoying. for 3 days it did not appear, then reappeared lastnight. When this all started at first I blamed the Beta testers for Total Protection 2010. This is why we beta test software and if issues are not presented, then the developers can not address the issue. After Peacekeepers post on it still being in Beta, I now hold Mcafee totally responsible for this cause. Macfee better seriously consider reinbursting customers with some sort of free year or something. It is a criminal act to Knowingly and willingly sell or distribute a harmful product to a consumer. Mcafee should have never released the 2010 version to XP with a known issue in beta. What they have released is and can be considered a virus for the fact that it has/is doing the same thing to peoples computers that viruses do.
No disrespect to you peacekeeper, but personally it may have not been a wise decision to disclose that this issue in known in the Beta Software. If you think I'm wrong, talk to any Civil Lawyer and you'll see different.
Both my laptops were completely out of commission for almost the entire last 2-3 weeks. I was finally able to restore them to the last backup, unfortunately one of them was last backed up 9/9/2009. My fear is if I stay with McAfee what is to stop this from happening again. I think McAfee, after much angst, is finally stepping up to the plate by formally stating they will reimburse me for my repairs and I have 2 years of free virus protection. It is just a sad deal that one must claw and fight in order for the BIG companies to do what is morally right and play like good corporate citizens. I would have felt more secure and had the warm fuzzies if McAfee had sent out an email indicating WARNING in the subject line - warning one not to do certain things that would further compromise their systems. Instead, I had to search the Internet on my Macbook, find the issue and the support numbers. My wireless is still out, which leaves me having to make more calls to them and/or Netgear (the router manufacturer).
McAfee wasted money by sending the 5958 fix it CD to me via FedEx. I appreciate the effort, but nothing like throwing things at a problem knowing and admiting it was not the fix. I found their action to be rather strange and counterproductive!
However, their recent email made me feel a little better. Perhaps there is hope...even though I am still limping along with my laptops that won't recognize my wireless network.
Good luck!Message was edited by: bengaile on 5/13/10 8:18:09 AM CDT
This is not correct. Maybe I can help clear this up. You're talking about 2 different issues. The issue this thread refers to is that some users are getting a mcsvchost error when they shut down their computer. To give you the technical information on this first issue:
The other issue was very different, but involved a similarly named file. The 5958 DAT issue affected the svchost file on Windows XP SP3 computers ONLY.