Windows Defender Firewall error 0x800706d9: how to fix it

Published Sources checked By helps.wiki editorial team

Error 0x800706d9 is a generic RPC error ("There are no more endpoints available from the endpoint mapper"). It usually means the Windows Defender Firewall service is stopped or disabled. Setting that service to Automatic and starting it is the first thing to try. Microsoft's own page covers only that service, and only on Windows Server 2008, so the Windows 10 and 11 steps rest on community reports.

Applies to:Windows 11Windows 10Windows Server 2008with the Remote Desktop Services role
On this page

What it means

The code 0x800706d9 translates to "There are no more endpoints available from the endpoint mapper". Despite what the search results suggest, it is not really a Defender problem. Windows components talk to each other through RPC, and this error means one of them called a service that wasn't there to answer.

In practice the missing service is usually Windows Defender Firewall (service name MpsSvc) or the Base Filtering Engine (BFE). It may be disabled, stopped, stuck in "Start Pending", or damaged.

Microsoft documents this code officially only for Windows Server 2008, where a Remote Desktop Services role install fails because the firewall service is off. Reports for Windows 10 and 11 come from community threads, so the client-side fixes below rest on that kind of evidence and on the same underlying mechanism.

Symptoms and causes

You are likely dealing with this problem if:

  • In Windows Security, under Firewall & network protection, clicking Use recommended settings returns 0x800706d9.
  • The firewall keeps failing again after you thought it was fixed.
  • On Windows Server 2008, adding the Remote Desktop Services role fails with "Attempt to configure Terminal Server failed with error code 0x800706D9."

The usual causes, most common first:

Windows Defender Firewall service is stopped or disabled
The MpsSvc service is set to Disabled or isn't running. Microsoft's Server 2008 article describes exactly this: a setup step needs to add a firewall exception and fails when the service is off.
Service stuck or damaged
The firewall service or Base Filtering Engine may be stuck in "Start Pending" or have a damaged configuration, so the RPC call still finds nothing to answer it.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Start the firewall and Base Filtering Engine services

Easy

If the firewall service is off, the RPC call has nothing to reach. Microsoft's official page (KB 2027551) backs only the Windows Firewall service, and only on Windows Server 2008. Checking Base Filtering Engine is a reasonable dependency check, not an officially documented step.

  1. Press WinR, type services.msc and press Enter.
  2. Find Windows Defender Firewall, double-click it, set Startup type to Automatic, click Start, then OK.
  3. Also look at Base Filtering Engine. If it is not running, set Startup type to Automatic and click Start.
  4. On Windows Server 2008, do this before installing the Remote Desktop Services role, then run the install again.
  5. Repeat the action that failed (for example Use recommended settings in Windows Security).

2.Restart the PC and try again

Easy

If a service is stuck in "Start Pending", a reboot clears it and lets it start normally.

  1. Save your work and restart Windows from the Start menu.
  2. After sign-in, check in services.msc that Windows Defender Firewall shows Running, then retry.

3.Reset Windows Firewall to defaults

ModerateChanges settings

This returns the firewall policy to its default state. In a Microsoft Q&A thread about this error on Windows 11, a moderator suggested a firewall reset and the person asking said it seemed to fix the problem. The thread does not show the exact method, so the steps below are the standard ways to do it, not a confirmed copy of what was used there.

Before you start: A reset removes custom firewall rules, including rules added by apps and games. Note down any rules you rely on first.

  1. GUI option: open Control Panel, go to Windows Defender Firewall, click Restore defaults in the left pane, and confirm.
  2. Command option: open Terminal (Admin) or Command Prompt as administrator and run the reset command.
    Command Promptrun as administrator
    netsh advfirewall reset
  3. Restart the PC, check that the firewall service is running and retry.

Check that it worked

  • In services.msc, Windows Defender Firewall shows Running with Startup type Automatic (and Base Filtering Engine too, if you changed it).
  • The action that failed (for example Use recommended settings in Windows Security) completes without 0x800706d9.
  • The firewall still works after a restart.

If it still fails

  • If the error returns after every restart, the cause is likely deeper than a stopped service. I found no official Microsoft guidance for this on Windows 10 or 11, so contact Microsoft Support at support.microsoft.com and back up your files first.
  • For managed or work PCs, contact your IT administrator.

Questions

Is 0x800706d9 a Defender virus problem?

No. It is a generic RPC error that normally points to a stopped or broken firewall service, not malware.

Will a firewall reset delete my files?

No, but it removes custom firewall rules, so some apps may ask for network permission again.

Sources

  1. RDS fails to install with error 0x800706D9 - Windows ServerOfficial · Microsoft Learn
  2. Microsoft Q&A answer on recurring Windows Firewall failure with 0x800706d9 on Windows 11 · Microsoft Q&A (community)

Browse