- Mcafee Agent 5.6 3 Download
- Mcafee Agent 5.6 3 Supported Platforms
- Mcafee Agent 5.6 1 Hotfix 3
- Mcafee Agent 5.6 Hotfix 3
- Mcafee Agent 5 6 3 0
Re: Memory leak with Agent 5.6.3.157 I used poolmon.exe to check for the memory leak and I think the leak is coming from the system pool tags SeTl an MFE0. We have a case open with both MS and Mcafee and are not getting anywhere and continuing to have to cancel our on demand scans or reboot our servers when they are run. Note: When McAfee Agent 5.6.0 is installed on Windows systems in unmanaged mode, the DXL client is automatically installed and is in idle state. Task Download and extract the McAfee Agent package (Example: MAxxxWIN.zip) to a temporary location.
The environment I manage uses McAfee EPO for its antivirus needs, and I ran across multiple events in the application log with ID 11714 and 1002 on one of the machines. The event description was 'Product: McAfee Agent -- Error 1714. The older version of McAfee Agent cannot be removed. Contact your technical support group. System Error 1610.' I tried to manually uninstall the Agent and it kept asking for the MFEAgent.msi installer file, but that file was already in the location it was looking in. This meant the something was corrupt, so a little digging through the McAfee support forums led me to a quick fix using a registry hack.Mcafee Agent 5.6 3 Download
1. Open up the Registry Editor (regedit.exe)
2. Navigate to HKEY_LOCAL_MACHINESOFTWAREClassesInstallerProducts4. Search for MFEAgent.msi
5. Delete the PackageName entry that is found with MFEAgent.msi as its value. It should be under something like HKEY_LOCAL_MACHINESOFTWAREClassesInstallerProducts2C12BAA2ADC498140ACEE56D6611F348SourceList. The
Mcafee Agent 5.6 3 Supported Platforms
2C12BAA2ADC498140ACEE56D6611F348 may vary between machines though, which is why you should search for itMcafee Agent 5.6 1 Hotfix 3
6. Restart your computer7. Reinstall the McAfee Agent
Mcafee Agent 5.6 Hotfix 3
An alternative to searching in steps 3 and 4 would be to look in the Application event log at your event ID 1002. This will give you the exact registry path to the PackageName key you need to delete.
Mcafee Agent 5 6 3 0
The McAfee forum post can be found here. Look on the second page for an entry by user SeaCat, who posted a long list of steps to fix the problem. Luckily, the first step of editing the registry was all that I needed to do, and from some of the other entries it looks like that also worked for some others.