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 No comments

95 answers

Sort by: Newest
  1. Anonymous
    2020-08-18T09:17:52+00:00

    Got my 2004 _64 node to install 4.18.2008.4 via the registry hack a few days back and not experienced any inclement impact.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-08-18T09:07:57+00:00

    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 No comments
  3. Anonymous
    2020-08-18T09:06:12+00:00

    A reboot just brings back 4.18.2007.8-0

    That was mentioned in a previous post about the rollback

    ____

    Sorry, the revertplatform fails to help matters.  The events seemed to stop, but I cannot start network inspection service. 

    That you cannot restart the service is good sign since by design it should not be stopped when it works without the issue. Status can be checked from PS with

    Get-MpComputerStatus | Format-List -Property $Properties

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-08-18T00:05:40+00:00

    Sorry, the revertplatform fails to help matters.  The events seemed to stop, but I cannot start network inspection service.  A reboot just brings back 4.18.2007.8-0

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-08-17T20:01:16+00:00

    Trying "%programdata%\microsoft\windows defender\platform\4.18.2007.8-0\mpcmdrun.exe" -revertplatform

    Thanks to whoever suggested it (I'd post, but browser not letting me back in history to it).

    Windoz security version info reports the correct rollback.  Unknown how long the rollback lasts, or if events 7000/7001

    resolved.  Will post results.

    Was this answer helpful?

    0 comments No comments