I have now restarted and right clicked on the M in the system tray and checked for updates. It reported that no updates were available, and then the same sort of error message I've been getting popped up...
Synchronization Application stopped working and was closed
A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
When I close the error message, I get another notification to run the McAfee Anti Spam update tool for a solution to the problem.
I downloaded mcutil-patch.zip to my desktop and double clicked on it to see the files within it. At the top of the window there is a button to "Extract all files".
I click on that and a dialogue opens to "Extract Compressed (Zipped) Folders". It allows me to specify the destination I want to extract them to, so I browse to C:\Program Files\Common Files\McAfee\MSC and click the "Extract" button.
When I go to that folder I can see copymcutil.bat, mcutil.dl_, and Instructions-McUtil.txt
Click the Start Button Search for cmd (command prompt) Right click cmd and Run as Administrator
type the following commands and press enter after each one cd\ cd /d "C:\Program Files\Common Files\McAfee\MSC" regsvr32 /u McUtil.dll REN mcutil.dll mcutil.old REN McUtil.dl_ McUtil.dll regsvr32 McUtil.dll
Sorry McAfee but when I purchase a product that includes automatic up-date I expect just that. Not some need to:
Extract the contents of zip file to %programfiles%\Common Files\McAfee\MSC\ Run copymcutil.bat Note: If you are using vista >right click copydriver.bat and select Run-As Administrator Actions of bat file - check if files are present - rename current dll from .dll to .old - rename new dll from .dl_ to .dll - register new dll Reboot
That was a patch for an issue that is seen only on a select set of machines( mostly DELL). It will be duly pushed as an upgrade to you via automatic updates soon. The automatic updates are delayed mostly for products from DELL as they have there set of tests that needs to be done before releasing a new version of our product.
As of now if you experience the issue you may run that patch or wait for the update to be pushed to you ( remember this is not a critical issue as the functionality of the product is not compromised due to this error which occures on a non-critical backend process only!)