cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

@kylekatso yeah, it looks like your "newer" ENS entry is 393232, in other words, "off and out of date..."

So it's like you're right back to where you started... as the OP, no progress for you...

If you're brave enough, I'd clear the AV classes from WMI using the VB script I mentioned previously, let WDA and ENS re-register, and see if your issue is resolved.

@chealey, this issue is definitely not resolved.  Even if my suggestion above works, enterprise IT managers can't be expected to go to every client endpoint and run random VB scripts to clean up McAfee's mess...

anti8.PNG

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

Shot myself in the food trying to clean my AV providers in WMI to get rid of the duplicate...

ENS and WDA both re-registered upon reboot (and no duplicates), but ENS is now 393232 even though it's on and up to date...

Entire issue has returned... wiping all McAfee out of this computer and starting over...

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

Definitely still broken...

  • Wiped McAfee (all ENS and Agent) from my computer with Endpoint Removal Tool
  • cleared AV providers in WMI
  • Rebooted, WSC/WDA start like normal, everything is fine without McAfee
  • Reinstalled McAfee Agent
  • Reinstalled ENS
  • 2 AV providers registered
  • ENS productState = 397328 (On-Access scanning ON, but NOT up to date)
  • Forced an update
  • ENS productState = 397312 (On-Access scanning ON, up to date)
  • All was working peacefully and coexisting
  • ...Rebooted...
  • ~3 minutes after computer boots, ENS AV object is updated to productState = 393232 (On-Access Scan OFF, NOT UP TO DATE)
  • Still just the 2 AV providers
  • Forced another ENS update, no change

WSC/WDA & ENS coexistence completely broken again.

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

@chealey, I'm beginning to think this was never working and still isn't fixed, which is probably why there is no release note about it.  My earlier success today could be due to anything, including the simple act of updating ENS, which set the productState to 397312.  But turning Debug logging on did that for a time as well...

Can you double check that this issue has actually been fixed in the October release build so we don't keep chasing our tails?!  If there's no release note about it, and everyone here who has posted recently is still having issues with it, then it's not fixed.

Please re-open SR: 4-20058973171.  When I try to, by responding to an email for it, it replies to me, indicating,


This is a system-generated message in response to your email about SR # <4-20058973171>. This service request is currently closed and this e-mail is not being monitored.
Please do not reply to this email.

If you believe that this service request was closed in error and need further assistance, please contact our Technical Support team using one of the methods listed below.

I'm done jumping through hoops.

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

Also, please un-mark this as "Solved..."

JayMan
Level 10
Report Inappropriate Content
Message 146 of 259

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

Just deployed the update to my own system & can confirm also still having the issue after reboot.

 

Will update my support case with the same... Or not, as the case is closed & can't be updated...

McAfee Employee chealey
McAfee Employee
Report Inappropriate Content
Message 147 of 259

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

All - please reach out to the owners of your cases with this feedback. Please collect the same data you have previously been supplied with and we can ask engineering to review this again. Based on your feedback now it would indeed seem the issue is not resolved.

As I mentioned before, we handed out the Early Access Release to customers who raised this issue with us and all responses we got from those tests we successful. This exact same build has since been released GA, so I'm surprised to hear that it doesn't work.

I can't comment on why it never made the release notes, what goes in them is a decision made by the Engineering and Content Team themselves. Based on the feedback of the EA Release and our internal testing, we had considered this resolved.

Was my reply helpful?
If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?
Reliable Contributor SWISS
Reliable Contributor
Report Inappropriate Content
Message 148 of 259

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

@billmoller 

Thank you for Drilling down into this and all your Debug testing which took Hours when not days that nobody will pay.

And i absolute agree that Closing your case is not what they should have done. That immense pressure they have in Sophia and India to close all tickets is immense AND it does not relay help customers.

You can allwyas reopen the case (Mean Nothing esle then you can spend another 3 Hours witrh Sophia on the phone)

The issue is not taking serious we think. We understand that it's a MIX between Microsoft and Mcafee and nobody want to be responssible.

@Mcafee is this where it should be? At development?

 

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

October release fixed problems for us on Windows 1903. No more alerts that McAfee is turned off.

JayMan
Level 10
Report Inappropriate Content
Message 150 of 259

Re: Windows Defender problem reported by MICROSOFT

Jump to solution

Perhaps the POC fix was only tested on 1903 users & not those on 1809 reporting the issue? (Since we were told earlier in the thread it was only an issue with 1903)

Had a remote support session today under my new case number (4-20380411771) and repeated all the same checks. Support rep said it's only a cosmetic issue, which I pointed out it's really not since Defender is actually running & scanning along with ENS.

 

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator
  • Community Help Hub

      New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

    • Find Forum FAQs
    • Learn How to Earn Badges
    • Ask for Help
    Go to Community Help

    Join the Community

      Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

    • Get helpful solutions from McAfee experts.
    • Stay connected to product conversations that matter to you.
    • Participate in product groups led by McAfee employees.
    Join the Community
    Join the Community