Escalation required: MpsSvc RPC shutdown deadlock causes permanent STOP_PENDING and error 87

Question

Windows Defender Firewall MpsSvc becomes permanently stuck in STOP_PENDING shortly after startup.

Service-specific error: 87, "The parameter is incorrect"

Win32 exit code: 1066

Event Viewer: Service Control Manager event 7024

CheckNetIsolation error: 1753 / 0x6D9

netsh advfirewall reset cannot contact the firewall service.

I have already completed SFC, DISM, firewall rule reset testing, multiple Windows updates, third-party antivirus removal, dependency verification, and a Windows in-place repair installation.

BFE, mpsdrv, and NSI are running correctly. MpsSvc configuration, service SID, dependencies, Microsoft DLL signatures, firewall policies, and network components were verified. No third-party DLLs or network filters were found. Replacing the active firewall rules with the Windows default rules did not resolve the problem.

I captured a 46.8 MB dump of the affected svchost.exe process while MpsSvc was stuck.

WinDbg shows that MpsSvc is blocked internally during RPC interface shutdown:

MPSSVC!FwServiceShutdown

MPSSVC!FwComponentsShutdown

MPSSVC!FwRpcAPIsInterfaceDestroy

rpcrt4!RpcServerUnregisterIfEx

rpcrt4!RPC_SERVER::UnregisterIf

rpcrt4!WAITABLE_INTERLOCKED_INTEGER::WaitForValue

This is an internal MpsSvc/RPC shutdown deadlock, not a normal missing dependency or firewall rule issue.

Please escalate this case to the Windows Networking, Windows Filtering Platform, RPC, or MpsSvc engineering team and provide a secure method to upload MpsSvc-STOP_PENDING.dmp.

Please do not repeat SFC, DISM, firewall reset, new-user, in-place repair, or formatting instructions. These procedures have already been attempted.

Answer 1

I understand why you are asking specifically for escalation, Wistaria sinensis.

However, I must note that Microsoft Q&A is just a public user-to-user support. Moderators/community contributors here cannot open an engineering investigation or escalate this to the Windows internal teams. If you're looking for deeper diagnosis tools and procedures, I have two suggestions:

1 - Report the issue via Microsoft's official feedback channel

• Press Win + F to open Feedback Hub > report a problem
• Describe the issue, including the details you shared above
• Upload any screenshots, recordings, dumb files,... if available.

2 - Open a Microsoft Support case

• Visit Contact Us - Microsoft Support > sign in  
• Enter / choose an issue > Get Help to make request  
• Scroll down > click Contact Support to connect to an agent 
• Select a category > continue and you should reach the chat option. 
• If you don't see it, go through another category and request escalation.
• Describe this as a reproducible MpsSvc STOP_PENDING / RPC shutdown hang.

Note: The support contact team only works at certain times, so if the last window shows that it's unavailable, try opening it again the next day. If you prefer phone support, you can leave a phone number. This way, they can call you and help you.  

Because the stack involves RPC, it would also be worthwhile to collect Microsoft's TSS NET_RPC trace while reproducing the failure, if the support engineer requests additional diagnostics. You have already exhausted the normal repair path, even an in-place repair, so moving to deeper analysis is the reasonable next step.