Windows Firewall Error 0x800706D9 “The snap-in failed to load”

When you open the Windows Firewall (with Advanced Security) applet, the following error may show up:

There was an error opening the Windows Defender Firewall with Advanced Security snap-in

The Windows Defender Firewall with Advanced Security snap-in failed to load. Restart the Windows Defender Firewall service on the computer that you are managing. Error code: 0x6D9.

windows firewall error Error 0x6d9 - There are no more endpoints available from the endpoint mapper

The Win32 error code 0x6D9 (“0x800706D9” or EPT_S_NOT_REGISTERED) means “There are no more endpoints available from the endpoint mapper.”

Attempting to start the Windows Firewall service (“mpssvc“) may show that the service gets stuck in the “Start Pending” state. Or, the service may throw the following error:

Windows could not start the Windows Defender Firewall service on Local Computer. 
The service did not return an error. This could be an internal Windows error or an internal service error.
If the problem persists, contact your system administrator.

windows defender firewall service start error - the service did not return an error

Also, the Windows Security UI may show the following error:

Microsoft Defender Firewall is using settings that may make your device unsafe.

Restoring default settings will remove all Windows Defender Firewall settings that you have configured for all network locations. This might cause some apps to stop working.

windows firewall unsafe settings - reset

The classic Control Panel may show the following error:

Update your Firewall settings

Windows Defender Firewall is not using the recommended settings to protect your computer.

windows firewall unsafe settings - reset

However, clicking on the “Restore settings”, “Use recommended settings”, or restoring default settings by resetting the Windows Firewall using any other method may not help.

RELATED: The Windows Firewall issue may prevent the installation and updating of the Store apps. Some Store apps can’t be installed or updated unless Windows Firewall is fixed. For more information, check out the article: Windows Store Error 0x800706D9


The Windows Firewall error 0x6D9 may occur if one or both of the following service registry keys are corrupted, or their permissions are incorrect.




The mpssvc service (NT Service\mpssvc) must have write access to the following keys:


and mpssvc must have special permissions (or Full control permissions) for the following key:


firewallpolicy permissions mpssvc

These are the special permissions assigned for mpssvc by default.

firewallpolicy permissions mpssvc


To resolve the issue, follow these steps to replace the SharedAccess, BFE, and MpsSvc registry keys from another computer. The following steps should restore the missing keys/values and fix the incorrect registry permissions automatically.

  1. In the C:\ drive, create a folder named “Registry” — C:\Registry.
  2. Download or
  3. Extract the four files from the Zip file to C:\Registry.
  4. From the C:\Registry folder, right-click “Run.bat” and choose “Run as administrator.”
    bfe firewall sharedaccess hives - Firewall Error 0x6D9
    (Note: You should see the output “The operation completed successfully” for each command.)
    bfe firewall 0x6D9 fix
  5. Restart Windows.

windows firewall error Error 0x6d9 resolved

The Base Filtering Service, Internet Connection Sharing (ICS), and Windows Firewall services should now be fixed.

One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded in 2005.

Leave a Comment