Checking some of the links that were posted during the 6809 issue seems to show that there's a 6811 DAT out today, well, since this afternoon. My next auto-update was scheduled like 20 minutes ago but I'm still at 6809. I tried a manual update and was told I was up to date. Rebooted and tried another manual update (that was how I'd gotten to 6809) and still seem to be up to date, according to Security Center. The Event Viewer showed me McAfee started at DAT 6802 (my boot dat version) and then I think after I tried to update, another event was posted saying the service had started at 6809.
Is there anything going on here? Is 6811 only for enterprise customers?
Thanks in advance.
I tried the MVT and saw the same message wwwringer saw after 6809...
In the Diagnostic Log under Health Check Details:
Top Issue: iDispatch Top issue Detection
Top Issue: Core Components Failed to install
I also had a "content issue" which the MVT tried to fix but reported it could not. Security Center is still green and I appear to still be at 6809. Manually attempting to update results in me being told I'm current.
I am worried something's going on, especially with those errors comments from the MVT and what not. I really don't want to reinstall and I would very much like to know what's happened to cause all this, especially if I end up having TO reinstall. Up to last weekend, I really haven't had any real problems with this version of McAfee and had even renewed my subscription not too long ago.
Any help, thoughts, advice, or suggestions would be greatly appreciated.
You can always check the details of the latest DAT from vil.nai.com website or click on the link below:
Kindly try the manual update from this and let me know the status of the update.
I wonder what happened to 6810? I'm not doing any manual updates anymore until dats stop skipping numbering again. The only problem is that I don't keep my computer on 24 hrs a day so automatic doesn't always find me on line, which is the reason I was doing manual updates.
Dont panic maybe some internal server issues , coz i encountered the same issue from morning and it got updated now without any troubleshooting ...