This problem was driving me nuts. I did read at least 50 articles on how to debug firewall problems. I did all the stuff like “sfc scannow”, the microsoft fixit, tech articles, service repair programs, and still a nonworking firewall.
Just when i was giving up, and made a prepare for a full system reinstall, I got it fixed.
Problem description:
When typing net start MpsSvc you see the following info
The Windows Firewall service is starting.
The Windows Firewall service could not be started.A service specific error occurred: 13.
If you don’t have a error 13, just skip the complete article. This article is only for people with a error 13. Also its a last resort. Don’t blame me, if your computer is not working after my suggestion’s.
If you have a error 5, I suggest to read the following link
With the software serviwin from nirsoft you will see the following message on the service
Here are the steps:
This solution is for Windows Firewall error in Vista. In the Event Log you will find the following message.: “The Windows Firewall service terminated with service-specific error 13 (0xD).”
The way i fixed this was to delete the complete regkeys under
HKLM\System\CurrentControlSet\Sevices\SharedAccess\Parameters\FirewallPolicy
So, open Registry Editor (Start->Run->regedit). Navigate to the key, and delete from the key “FirewallPolicy” but DONT delete the FirewallPolicy itself
you should have
Open a command prompt with admin rights and type
net start MpsSvc
If you have the firewall running you need to restore de default set of rules
Click on Start->Type Windows Firewall in the search box. Click on “Windows Firewall”
Click on “Allow a program through Windows Firewall”. Click on Advanced Tab->Restore Defaults.
You can also type in the following command in a dosbox (admin mode)
Muito obrigado resolveu meu problema 😀
Parabens!!!!!1
Thank you!!
Thank a lot , i spend a lot of time for solving this and finally landed in your site ,and it worked for win 7.
Thanks for letting me know it can also work for win7.
solution to the problem
http://www.tweaking.com/content/page/repair_windows_firewall.html
Hey this really helped me out too.
THANK YOU! WOW. How simple. I was just about up to here in PowerShell commands, got from Errror 13 (“service-specific”) to net svc error 1066 and was trying to enumerate the properties of the CimInstance ClassName Filter MpsSvc and pull out the ExitCode definition… RIDICULOUS! The last error I was trying to work through was this:
Set-CimInstance : Cannot bind parameter ‘Property’. Cannot convert the “ExitCode” value of type “System.String” to type “System.Collections.IDictionary”.
Then I got to your post. THANK YOU!
Thanks a lot.
It saved my windows and a lot of time.
Good boy
Υou are AWESOME!! I had tried everything for 2 weeks and i was about to reinstall win7 64 bit to my laptop when i noticed your topic. Thank you very mutch.
You saved the day !!!
thanks its works for me
Works with Windows 10. Deleted subfolders only.
Thank you so much. Spent a week pulling my hair out over this nonsense.
Guy, you rock!
Thanks 😀
Thank you so much, it solved the problem like a charm.
Thank you! This is the only so called “solution” that worked.
thanks you very much. this is very useful for me. Now firewall started.
This also works in Win 10. Many thanks!
Super Super,
I have this problem after a fresh install…………
Thanks Microsoft for crapy software…..
Thank you!
after searching hundreds of blogs and posts and what not, finally stumbled upon something that works. thanks man.
Thank You very much, im working to solve this problem for 2 days allready
i tryed it on WINDOWS 10 and it works perfectly !!!!
well thanks man, u made my day !!!!!
bravo~
I was having the same issue on a Windows Server 2016 machine.
The solution for me was inspired by this article, but I wasn’t able to start MpsSvc after deleting the data values in the FirewallPolicy key, so the fix for me was slightly different.
Luckily, I had exported the entire FirewallPolicy key earlier. I imported that again, and then tried starting MpsSvc again. SUCCESS! It started. Not sure why exporting and importing the very same data fixed it, but maybe it caused the permissions to get refreshed.
Thanks!