This content has been marked as final. Show 6 replies
Tried changing the settings in the McAfee "Access Protection" section? For example:
RIGHT click on the McAfee icon in the lower right corner, choose "VirusScan Console", then double click on the "Access Protection" section, then UNCHECK the box in the lower left corner which says: "Prevent McAfee services from being stopped".. Once that's done, you should be able to temporarily disable it using a RIGHT click on the McAfee icon.
There are also other lines in "Access Protection" which could be UNCHECKED if the error still shows up.
Unfortunately, you've not told us which version of the corporate McAfee ViruScan you have installed. the above instructions should help if you're using either VS 8.5i or 8.7i.
Hope this helps.
Thanks for your reply. You were right. After I disabled Access Protection, the problem solved. But I think this is not the solution, as disabling "Access Protection" is a security risk. Does McAfee has any solution to this problem?
Well, although it's clear your machine is having the issue, I've not seen the problem listed on these forums before.. I've got about 30 Windows XP SP3 machines here running a variety of different VS versions, including Vs 8.5i and 8.7i.. None of them exhibit a problem with "msconfig" when "Access Protection" is enabled with the default settings. Maybe you've got different settings in your Access Protection.. Instead of disabling it as a whole, have you tried disabling one item at a time, maybe in the "Standard Protection" area?
Hope this helps.
Confirmed, I have this problem in my environment.
Even if I disable access protection completely, I still get the error message.
Message does not occur before installing VSE, install it, you get message.
XPSP3 running VSE8.7 Patch 1 on most systems.
Tested with 8.7 Patch 2 today, no difference there.
Actually just did a quick web search but found nothing except this thread :)
Am just about to call McAfee and see if they have a quick tip.
It's not much of an "issue" as settings are still applied, but still an annoyance.
Won't be long before techs start complaining about happy
Thanks a lot happy