Windows Defender Antivirus Network Inspection Service issues since Windows 10 2004 update

Anonymous
2020-08-06T08:15:09+00:00

I got the 2004 update yesterday and that went well enough otherwise but I am having a problem with the Windows Defender Antivirus Network Inspection Service that I did not have previously. 

  1. I noticed in Event Viewer several Errors that began immediately upon completion of the update last night: 

The Microsoft Defender Antivirus Network Inspection Service service depends on the Microsoft Defender Antivirus Network Inspection System Driver service which failed to start because of the following error: 

The supplied user buffer is not valid for the requested operation.

  1. Further inspection has revealed that there is now a problem with Real Time Updates. 

Microsoft Defender Antivirus Real-Time Protection feature has encountered an error and failed.

  Feature: Network Inspection System

Error Code: 0x8007042c

Error description: The dependency service or group failed to start. 

Reason: The system is missing updates that are required for running Network Inspection System.  Install the required updates and restart the device.

I've got this error repeatedly (3002). 

  1. I went into security and maintenance to see what was going on with my security settings. That is not showing anything "wrong." 
  2. The Network Inspection Service is configured to manual, not automatic. I can't change this. 
  3. Real-time protection is on, and has been on. On Virus & threat protection settings, all of those are still toggled on, and those settings are the same before and after the upgrade. I haven't tried turning them on and off again yet. 
  4. I already did the August Safety scan, but I downloaded a fresh copy and am re-running it. 
  5. I did dism and sfc checks and they showed no problems that needed repair. 

Something is definitely wrong with the install of Windows Defender tho... Help? How do I fix this and stop the errors and get it reconfigured properly. Do I have to reinstall it?

Windows for home | Windows 10 | Security and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

95 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-08-17T14:24:04+00:00

    That sequence you described does not fix the Network Inspection Service not running, and I never claimed plugging the drive in sets memory integrity to off.  

    In fact I stated the exact opposite of that. 

    As long as memory integrity is set to on BEFORE plugging the drive in then it's all good, except for the fact that on my system the Network Inspection Service not running had absolutely nothing to do with the WD SES Device drivers in the first place.

    Yes, these are two separate issues. I only described here how to turn the core isolation back "on"

    Again, back on the topic, as I said above, the errors stopped on my system after updating to Platform 4.18.2008.4, alongside with KB 4566782. No re-install was required

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-17T14:59:16+00:00

    Then your reinstall just happened to circumvent the bad version of the Defender Platform being discussed in this thread. Either it hasnt updated to the bad version yet or it updated directly past it to the fixed version.

    The SES driver is a separate issue.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-08-17T15:08:29+00:00

    Then your reinstall just happened to circumvent the bad version of the Defender Platform being discussed in this thread. Either it hasnt updated to the bad version yet or it updated directly past it to the fixed version.

    The SES driver is a separate issue.

    I have multiple Windows 10 machines running on the so-called "bad version" of Defender Platform and the NIS runs perfectly.

    It isn't as black and white as you're making it sound.  It's a combination of things causing NIS to fail.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-08-17T15:38:31+00:00

    Interesting.

    I, too, have multiple Windows 10 machines and on every single one of them NIS failed with Memory Integrity on when on 4.18.2007.whateveritwas and resumed normal functioning upon upgrading to 4.18.2008.4. No reinstalls were necessary for any of them.

    Their hardware and software configurations vary wildly with some having little to nothing in common. Different CPU makers, mobile vs desktop platforms, etc. Only one of them has ever had a WD external attached.

    The only common cause I could find was that version of Defender. They were on different security intelligence versions as well when experiencing the problem.

    In every case, toggling off Memory Integrity with Defender 2007 allowed NIS to run and in every case updating Defender to 2008 allowed NIS to run with Memory Integrity enabled. For one machine that I had to force to pull down 2008, I verified that the issue still existed (so no other changes or updates had fixed it to that point) and then updated only Defender Platform and verified the issue had resolved.

    To be clear, I'm not saying that I doubt your experience. I legitimately find it interesting that your experience with this issue has been so different than mine and wanted to expand some on my experience.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-08-17T16:24:14+00:00

    I wonder if it's possible and/or safe to pull 4.18.2008.4 on Windows 10 1903 (Pro 64-bit).  I had planned to wait until EOL before upgrading OS version.   I'd prefer not being the first to try it, in case it means re-installing the OS.  I'd prefer to run with both NIS and MI working, like they did before.  I can boot linux instead;-)

    Was this answer helpful?

    0 comments