Home > Could Not > Could Not Contact Filter Driver Mcafee 8.7 I

Could Not Contact Filter Driver Mcafee 8.7 I

Alternately you can goto add remove programs and run a repair which should also fix this issue. Re: McLogEvent 5004 Could not contact Filter Driver. mfehidk service failed to start due to the following error: The filename, directory name, or volume label syntax is incorrect. Might not contact Filter Driver. this contact form

Remove the HP pre-installed software such as Altiris before installing McAfee This articles explains about a situation when McAFee filter driver might cause a STOP Error on Windows Server 2003. But it seems there are multiple mfeavk drivers each with a unique number after mfeavk (i.e. For more information, see: http://support.microsoft.com/kb/256986 Do not run a .REG file that is not confirmed to be a genuine registry import file.If the previous solutions do not resolve the issue, then Nelson This problem was happening on a W2K server with McAfee Enterprise 7.0.

x 6 Anonymous - Description: Could not contact Filter Driver. Might not contact Filter Driver. Re: McLogEvent 5004 Could not contact Filter Driver. We were planning on upgrading this serve at some point to 8.8 so that was the logical choice for me.

Thanks in advance. English: Request a translation of the event description in plain English. I was hoping Business Contact Manager for Microsoft Outlook 2010 (Version: ... + "mfesmfk"System Monitor Filter Driver"McAfee, Inc." "c:\windows\system32\drivers\mfesmfk.sys" Get help as of top Mcafee Computer Software Driver experts on repairs, C:\Program Files\common File folders on installation drive. 5.

If you check the McAfee services all are started except the McAfee McShield service which although is on Automatic fails to start. Skip navigationHomeForumsGroupsContentCommunity SupportLog inRegister0SearchSearchCancelError: You don't have JavaScript enabled. devices in the Device Manager 3 of which have the yellow exclamation. http://www.fusecollaboration.com/blog/mcafee-8-7i-could-not-contact-filter-driver-on-access-scan-disabled When this is complete, reboot the system.

x 8 Private comment: Subscribers only. Contact the vendor of the filter driver else application ... x 10 Anonymous Removing and then reinstalling the entire Virusscanner solved the problem in my case. The author Webbo Login Failure Error Accessing Server SharesMoving Public Folder Replica - SSL Certificate Error 14 comments Reply 15/07/2009 at 3:28 AM bdavis You have done what no one else

Check the option to "Reset Permissions on all child objects and enable propagation of inheritable permissions." e. http://www.bhcblog.com/2009/01/05/mcafee-87i-error-0x7d1-the-specified-driver-is-invalid/ Highlight the following LEGACY keys, depending on which product you are using, one at a time. Join 559 other followers Search Recent Posts Cisco | ASA 5508 with Firewpower Cisco | Cisco IOS router to Meraki Appliance | site-to-site VPN with Zone based Firewalling Netgear - Rebuild Do you Wish to continue?" g.

I then re-installed VSE with an ePO Product deployment task. http://asmwsoft.net/could-not/could-not-contact-filter-driver-5004.html I found naifiltr.inf within the installation directory of McAfee and right clicked and installed it. Advertisements Share this:EmailTweetShare on TumblrPocketPrintLike this:Like Loading... 4 April 2009 in McAfee. Solution. 1.

The specified procedure could not be found. Click Start > run > Regedit {enter} 2. The issue should be investigated but you can also try the following workaround: Modify the registry path to the core driver during the installation. navigate here x 8 Sknijn This has occurred on other operating systems as well.

About usFuse Collaboration Services is a Cloud Solution Provider and Microsoft GoldPartner specialising in delivering SharePoint, Skype for Business, and Azurecloud-based solutions. Go to Start | Run and browse to C:\Program Files\Windows Cleanup 5. Repeat the procedure with both of the following Keys HKLMSystemCurrentControlSetServicesmfeapfk HKLMSystemCurrentControlSetServicesmfeavfk For each one replace the path to the file with the full path (Usually adding c:windows to the beginning).

Registry Patyh is not updated and your drivers are in Drivers folder but cant connect with Mcshield.Please follow these steps to resolve this.

Always RTFM and have Google at the ready! The specified procedure could not be found. The information posted on this Blog is provided 'as-is' and so I take no responsibility for it's accuracy or validity - my stupidity is my own, you can't have it. Even though it will install and work properly, when you uninstall it and install VShield 4.5.0 or 4.5.1, the McShield service will be unable to start.

Reinstall NetShield 4.5. McAfee 8.7i "Could not contact Filter Driver", On Access Scan Disabled Andrew Walman 06/11/2008 Blog Rich ContentMcAfee have recently released VirusScan Enterprise 8.7i, with various performance improvements over 8.5i. Contact; FAQ; News ... http://asmwsoft.net/could-not/could-not-contact-filter-driver.html Lucia St.

After insuring the correct key is highlighted, follow steps a-g listed below for each LEGACY key listed.