I do have autoupdates for Windows. I also check periodically on my own and run the Custom...to select what else I want...for a whole day after the new McAfee came, I couldn't connect. It went away. So it wasn't a McAfee problem ...since I can't make a cause and effect relationship just because the other problems started at same time.
It was the Windows tech that found this forum for me and identified it through my giving him the error message.
I run my Bridge website on a free-standing Windows version, but even if I play through IE, the BBO online version, full-screen play slows down as soon as McAfee starts to download updates.
I know that more frequent updates means less likely to have trouble.
I am still waiting....as I said.
I believe it was the McAfee tutorial that popped up that said...faster downloads, less interference...maybe not exact words, but I thought...Great!! I won't get slowed down during bridge play.
Not AS bad as it was, but I always hope I don't have a download during a tournament.
Glad to see others notice how slowly the scan goes. Mine gets "stuck" in the low percentages as well...
I still have the shutdown error.
I have no intention of messing with anything to work around this error.
When Dinesh removed my shortcut, even he couldn't find McAfee in Start/Programs....Found it in Add/Remove List and added it, but until I uninstalled and reinstalled it, I didn't see it at startup.
terriMessage was edited by: tmgrl4 on 4/21/10 8:35:06 AM CDT
I'm with you on this. Why should we be forced into the role of beta testers? I suppose McAfee will be willing to pay us for our efforts and for our wasted time and for selling us malfunctioning software?
I'm with you on this. Why should we be forced into the role of beta
testers? I suppose McAfee will be willing to pay us for our efforts and
for our wasted time and for selling us malfunctioning software?
and who thinks we are paid we do it to try to help users. Without a user "in the wild" trying the beta how can Mcafee be sure the fix works all they have I assume is in house PCs. The beta is stable it has been on my PC for the past 2 weeks in the 10.5 version and in beta for 4 years without major issues. If we had beta users reporting this we mods would not need help here. Any1 got 20 mins to install the beta?
Yes, I have 20 minutes but after the Events of Todays Fiasco with McAfee, I have told my Firewall to NOT let McAfee connect to the internet until it is solved.
I am VERY disapponted in McAfee for not being able to even fix their own Code.
FYI - here's the posting referred to on the CNet website:
McAfee's popular antivirus software broke down on Wednesday, causing Windows XP computers to have networking problems or repeatedly reboot.
By midday Wednesday, reports began to indicate just how widespread and damaging the McAfee update was.
The University of Michigan's medical school reported that 8,000 of its 25,000 computers crashed. Police in Lexington, Ky., resorted to hand-writing reports, and turned off their patrol terminals as a precaution. Some jails cancelled visitation.
Early reports attributed the widespread problems to a routine McAfee update that caused computers with Microsoft's Service Pack 3 installed to incorrectly identify a legitimate operating system component as containing a virus.
The update effectively confused the PC's immune system, causing it to attack legitimate operating system processes in the same way that some diseases can cause the human immune system to turn inward.
A McAfee representative confirmed the problem to CNET, and said the buggy update code had been removed from the company's servers and that a fixed version would be made available shortly.
"McAfee is aware that a number of customers have incurred a false-positive error due to incorrect malware alerts on Wednesday, April 21. The problem occurs with the 5958 virus definition file (DAT) that was released on April 21" at 6 a.m. PT, the company said in a statement.
A report at the Internet Storm Center said the McAfee update registered a false positive and flagged the Windows file svchost.exe as a virus.
The update did not seem to cripple computers running Windows Vista or Windows 7.
Compounding what seems to be a day of snafus for the Santa Clara, Calif.-based company was that it initially directed affected users to download a file from its support site. But after tens of thousands of irate users flooded into the forums, the site abruptly went offline, and began to return an error message.
McAfee has posted a Web page on a separate site with detailed instructions on how to fix XP computers that have been crashing because of Wednesday's update. It recommends manually downloading and installing an "EXTRA.DAT" file, and then restore files that have been incorrectly quarantined.
But that option requires a least a modest amount of technical ability, and as of 1 p.m. PDT, the company had not offered a better way. "McAfee is continuing to work on an automated solution," the page said. (In the meantime, click here for our guide on how to fix it.)
Updated at 1 p.m. PDT and 2:45 p.m. PDT with additional details.
Wow, Major setback for McAfee. lets use some random numbers here. Let's say that the University of Michigan has 100 IT techs that each take care of 250 computers.
But, since only 8,000 Computers are affected, SO FAR, each tech will have to fix 80 Computers. Now say it takes 30 minutes to get to and fix each of those 80 computers, now you are looking at 40 hours PER tech. Now multiply that times the 10 techs and you have the salaries of 10 techs for a full week, just for one compoany/School alone. Now multiply that times all the thousands of companies affected by McAfee.
I sure hope McAfee has a BIG check book to re-imburse these Companies.
OUCH! Can you say " Major Screw Up"?