This content has been marked as final. Show 4 replies
I've seen the same issue on XP sp3 and HIPS 7 p2. I ended up having to go into the adapter settings of each network interface and manually remove the feature from the general tab.
I also talked to a acquaintance at another large local company. He said that roughly have of their test deployment ended up having this issue. The got around it by deploying HIPS through active directory, but I'm not sure what they did to fix the broken clients. I'm currently investigating the same option.
I'd be very interested if anyone else has found a solution to this issue.
Could you share me the information of the company or at least the email to contact them and ask what they do?
Because McAfee support as always closed my case without a concret answer they took days to take care of the case and we were force to format the computer
thank you for your help
I'm sorry, but I honestly wouldn'y feel comfortable sharing that information. However if I make any headway on this issue or hear anything more from my contact I will post it to this thread.
My contact at the other company did say that after moving to the active directory installation process they haven't had anymore of the miniport driver issues.
I would fully uninstall and reinstall with HIP 7.0 patch 4, available on McAfee downloads.
Search the McAfeeHip7_Install.log for 'firehk driver installation'.
If there are no errors in the next couple lines, you should see a 'installfirehk.bat completed'.
If not, you would look in the McAfeeHip7_NdisInstall.log and the setupapi.log for clues as to why this is failing. Search the logs for FireHk and try to match up the timestamps.
The HIP agent installer calls Microsoft SetupAPI to install the NDIS adapter.