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-14T17:14:57+00:00

    The inconsistency  of Antimalware Client Version: 4.18.2007.8 <> 4.18.2008.4 between W versions is being observed by other users and reported in other forums as well.

    Update Catalog still does not exhibit 4.18.2008.4 and neither does (not even mentions W 2004 ...)

    MS might have retracted it.

    dir "%programdata%\microsoft\windows defender\platform" will show installed versions and a rollback as stated

    , e.g. with

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

    to the previous version might solve the issue in the interim, until MS get it sorted.

    It is however astonishing that such grave bug has made into release and not being caught by MS's QA processes...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-14T17:33:45+00:00

    Interesting that defender was updated 8/5 and caused no issues (events 7000/7001) until the "forced" windows update on 8/9.  By forced, I mean my pause updates was timing out, and I didn't want whatever was in the Tuesday 8/11 update until other people tested it.

     Directory of C:\ProgramData\microsoft\windows defender\platform

    08/06/2020  02:39 PM    <DIR>          .

    08/06/2020  02:39 PM    <DIR>          ..

    07/01/2020  05:53 PM    <DIR>          4.18.2006.10-0

    08/05/2020  01:18 PM    <DIR>          4.18.2007.8-0

                   0 File(s)              0 bytes

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-08-14T17:44:09+00:00

    After rollback to 4.18.2006.10-0 there are no more such events 7000/7001 printed in the event log, least on a node with W 10 Pro x64 2004 b19041.450

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-08-14T17:45:54+00:00

    4.18.2008.4 has not been retracted. It seems to be early in a rollout-style release. I was just able to force Windows Update to pull it down via a registry entry on one of my systems that wasn't getting it a few minutes ago.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-08-14T18:24:45+00:00

    seems to be early in a rollout-style release.

    That seems a bit unlikely for the Antimalware Client, being at the core of WD and which would defeat the point of quickly superseding a botched version as it is the case now. Or is MS now gradually beta testing the Antimalware Client with some unsuspecting customers? 

    If so they should have done a better testing job with 4.18.2007.8-0.

    Was this answer helpful?

    0 comments