Fix Windows Defender Firewall Error 0x6d9 (Step-by-Step)

Windows Defender Firewall error 0x6d9 usually appears when you try to open the firewall settings or run a command like netsh advfirewall, and it means the Windows Firewall service (or its dependent services) isn’t running or can’t be accessed. This guide walks you through the most common fixes, from restarting the service to repairing corrupted system files, so you can get the firewall working again.

What You’ll Need

Administrator access to the Windows PC (you’ll need to approve User Account Control prompts).
An internet connection (for the System File Checker to download missing files if needed).
Patience – some steps require a restart.

Step-by-Step

Restart the Windows Defender Firewall Service.

Press Windows + R, type services.msc, and press Enter. Scroll down to Windows Defender Firewall. Right-click it and select Restart. If the service is stopped, right-click and choose Start. Set its Startup type to Automatic by double-clicking it and choosing that from the drop-down.

Also make sure these two dependency services are running (right-click → Start if they aren’t):
- Base Filtering Engine
- Windows Defender Security Center Service (if present)
Run the firewall troubleshooter.

Open Settings (Win + I), go to System → Troubleshoot → Other troubleshooters. Find Windows Firewall (or “Network and Internet” on older builds) and click Run. Follow the prompts. This often resets the firewall rules and service state automatically.
Reset the firewall policy via Command Prompt.

Right-click the Start button and choose Terminal (Admin) or Command Prompt (Admin). Type the following and press Enter:
```
netsh advfirewall reset
```
This restores the default firewall policy. If it succeeds, you’ll see “Ok.” Then reboot and test again.
Run System File Checker and DISM.

Corrupted system files can cause this error. In the same admin terminal, run:
```
sfc /scannow
```
Wait for it to finish (it can take 10–20 minutes). If it reports errors it couldn’t fix, run:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Then reboot and run sfc /scannow again.
Check for third-party security software conflicts.

Some antivirus or VPN programs disable the Windows Firewall service. Temporarily uninstall (not just disable) any third-party firewall or antivirus suite, then restart the PC and check if error 0x6d9 is gone. If it is, reinstall the software or switch to Windows Defender only.
Repair the firewall registry keys.

If the above fails, the firewall registry entries may be damaged. Open an admin command prompt and run:
```
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess" /v Start /f
```
Then restart the PC. Windows will recreate the missing value with the default. Note: this is a safe command, but back up your registry first (right-click the key → Export) if you’re cautious.
Perform a clean boot.

Press Win + R, type msconfig, and go to the Services tab. Check Hide all Microsoft services, then click Disable all. Go to the Startup tab and open Task Manager, disable every startup item. Reboot and try the firewall again. If it works, re-enable services one by one to find the culprit.

Common Mistakes

Only restarting the firewall service and not the Base Filtering Engine. The firewall depends on this service; if it’s stopped, the firewall still fails.
Running commands without admin rights. netsh and sfc will fail silently or give access denied errors if you don’t use an elevated prompt.
Skipping the reboot. Many of these fixes only take effect after a full restart, not just a logoff.
Leaving third-party security software installed while testing. Some suites re-enable their own firewall hooks on startup, so you must uninstall them to truly test.

Tips

Keep Windows fully updated. Many 0x6d9 occurrences are fixed by cumulative updates that repair the firewall service.
If you recently changed the firewall service’s logon account, set it back to Local System (in services.msc → Properties → Log On tab).
Use the Windows Security app (not the old Control Panel) to check firewall status after fixing – it shows a green shield when healthy.
Create a restore point before making registry changes, so you can roll back if anything goes wrong.

Troubleshooting

If the error persists after all steps:

Check the Event Viewer. Press Win + X → Event Viewer → Windows Logs → System. Look for errors from SharedAccess or BFE around the time of the failure. The details often mention a specific DLL or service that’s failing.
Try the “Windows Firewall” standalone installer. Download the latest Windows 10/11 ISO from Microsoft, mount it, and run setup.exe to do an in-place upgrade repair. This reinstalls all Windows components without deleting your files.
Use the “Reset this PC” option. In Settings → System → Recovery, choose Reset PC but select Keep my files. This reinstalls Windows while preserving personal data (though installed apps will be removed).
If you’re on a domain network, the policy may be enforced by your organization. Check with your IT admin before making changes.

Frequently Asked Questions

What exactly does error 0x6d9 mean?

It’s a Windows error code that translates to “The Windows Firewall service cannot be started” or “The service is not responding.” It typically occurs when the service is disabled, corrupted, or blocked by another program.

Will I lose my firewall rules if I run `netsh advfirewall reset`?

Yes, that command restores the default out-of-the-box rules. Any custom inbound/outbound rules you created will be deleted. You can export them first with netsh advfirewall export "C:\backup.wfw".

Can I fix this without admin rights?

No. All the meaningful fixes require administrator privileges because they modify services, system files, or registry keys. If you don’t have admin rights, contact your IT department.

Is it safe to delete the SharedAccess registry key’s Start value?

Yes, that specific value is recreated automatically at boot. Deleting it forces Windows to use the default start type (Automatic). It’s a standard troubleshooting step and won’t harm other settings.

Why does this error appear after a Windows update?

Occasionally a cumulative update can change service permissions or leave a service in a transitional state. Running sfc /scannow and the DISM command usually resolves this.

Does this error mean my computer is unprotected?

Yes, if the firewall service is down, Windows Firewall is not actively filtering traffic. You should fix it promptly, especially if you’re on a public network. Until then, avoid downloading or running unknown files.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →