- The Windows Firewall service terminated with service-specific error Access is denied..
- Windows Firewall service does not start in Windows 10
- Windows Firewall service does not start
- 1] Scan for malware
- 2] Run SFC and DISM
- 3] Check Firewall Services status
- 4] Check Firewall-related Driver status
- 5] Run Group Policy Result Tool
- 6] Run Windows Firewall Troubleshooter
- 7] Reset Windows Firewall settings
- Windows firewall service error
- Windows firewall service error
- Answered by:
- Question
- Answers
- All replies
The Windows Firewall service terminated with service-specific error Access is denied..
recently installed Windows 7 64-bit on my laptop after I got a new SSD drive. At some point, my firewall stopped working and won’t start.
- Windows Firewall set to Automatic startup
- I do not have another firewall installed
- I’m using Symantec Antivirus 10.2.0.298
- I’ve looked on the internet and haven’t been successful and finding issue.
thanks in advance for any help.
When you attempt to start the Windows 7 firewall service you receive the following error
Windows could not start the Windows Firewall on Local Computer. For more information, review the system event log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 5.
If you look in the System Event Log, you will see event 7024 from the Service Control Manager
The Windows Firewall service terminated with service-specific error Access is denied..
This may be caused because the “NT Service\MpsSvc” account does not have adequate permissions on the following registry key
Windows 7 (all versions) / Windows Vista (all versions)
Windows Firewall service does not start in Windows 10
Windows Firewall acts as the first layer of defense against malware, so it is always advisable to keep it turned ‘ON’ – unless you are using third-party firewall software. If for some unknown reason if you find your Windows Firewall does not start automatically at startup, then here are a few troubleshooting steps you may want to try out.
Windows Firewall service does not start
The error messages you could receive are:
- Windows Firewall is not the default firewall
- Windows Firewall does not start
- Windows could not start the Windows Firewall
If Windows Firewall fails to start, the other errors you could see on your Windows system are:
- The Windows Firewall service terminated with service-specific error 87 (0x57)
- Error 0x80004015: The class is configured to run as a security id different from the caller.
- The Windows Firewall service terminated with service-specific error 6801 (0x1A91).
- Event ID: 7024 – The Windows Firewall service terminated with service-specific error 5 (0x5)
- Windows could not start the Base Filtering Engine service on Local Computer. Error 5: Access is denied.
- Windows could not start the IPsec Policy Agent service on Local Computer. Error 1068: The dependency service or group failed to start.
- Windows could not start the Network Location Awareness on Local Computer.
- “net start mpssvc” in cmd.exe returns the system error 1297.
We suggest you try the following troubleshooting:
- Scan for malware
- Run SFC and DISM
- Check Firewall Services status
- Check Firewall-related Driver status
- Run Group Policy Result Tool
- Run Windows Firewall Troubleshooter
- Reset Windows Firewall settings.
1] Scan for malware
First, scan your machine for malware using good antivirus software. If you have installed a 3rd party firewall or a Security Suite, then that could also be the cause of the problem. Many times, third-party security software can disable the Windows Firewall and even prevent it from starting up.
2] Run SFC and DISM
Run System File Checker or sfc /scannow . You may also want to Run DISM and see if that helps.
3] Check Firewall Services status
Next, type services.msc in Windows Start Search and hit Enter to open up Services. Here ensure that the Windows Firewall Service is started and set on Automatic. You do this by clicking on the Start button. Also, ensure that the Remote Procedure Call Service & the Base Filtering Engine Service is started and set on Automatic.
4] Check Firewall-related Driver status
Now you also have to ensure that the Windows Firewall Authorization Driver (mdsdrv.sys) is running properly.
To do so, type devmgmt.msc in the search bar and hit enter to open Device Manager. In the Views tab, check on Show Hidden Devices and also show Devices By Connection.
Locate Windows Firewall Authorization Driver in the list and double-click on it to open its Properties box. Click on the Driver tab and ensure that the process is started, and the startup type is Demand. Click OK.
Reboot. Hopefully, your Windows Firewall should be working OK now.
5] Run Group Policy Result Tool
If it does not help then run the Group Policy Result Tool to check if there is a Firewall policy blocking it. Open an elevated command prompt window, type gpresult -z and hit Enter. Check under Resultant Set Of Policies For Computer, esp under Security Options.
6] Run Windows Firewall Troubleshooter
Run the Windows Firewall Troubleshooter and see if it helps you. This ATS from Microsoft will help you repair and fix Windows Firewall problems automatically. See if it is available for your Windows or if it is built-in.
7] Reset Windows Firewall settings
Incidentally, drifting a bit away from the main topic, should you need to access the following panels easily, you can type the following Run commands and hit Enter
- Firewall Settings: FirewallSettings
- Firewall Control Panel: FirewallControlPanel
- Windows Firewall with Advanced Security: wf.msc
TIP: How to Configure the Windows Firewall may also interest you.
Windows firewall service error
I had the same problem: Windows Firewall would not start.
If I clicked a button to start the firewall in dialog, it would just fail. If I tried from the command line, with net start mpssvc, it would give me Error 5.
To fix it, I followed the steps here — http://support.microsoft.com/kb/943996 . Mostly. I had to resort to some extra steps, which I will describe below.
First — The article says it applies to Windows Vista, but I have Windows 7 and it applied to Windows7 as well, at least in my case.
I found several problems with the article, described here:
- The article includes a link to a «Fix it» program which is intended to provide an automated way to apply the required fixup. It sounds like a good idea but it did not work for me. The fixit ran, but after 45 seconds it said «The problem is still present» or something like that. It was ineffective. This is a shame because the diagnosis of the problem in the article is EXACTLY RIGHT.
- I then went through the steps described for manually editing the security permissions on the registry keys associated to HKLM\CurrentControlSet\Services\SharedAccess as described in the article. The article provides enumerated steps to do this. The list of steps is missing one critical step, between step 2 and 3, which is , click Add. .
- The article says I need to modify the ACL for the Epoch key, and the ACL on 2 different Parameters keys. I did this, adding permissions for the MpsSvc user to the ACLs on these keys, remembering to perform the missing step I just described. Then I tried restarting the service with net start mpssvc. It failed once again with the same error — ENOACCESS, 0x5, Access is denied. I then examined a working Windows7 computer and checked the ACL for these keys. On the working computer the Epoch2 key also had access for the MpsSvc User. I modified that ACL as well, and then tried restarting — it worked.
The original scenario was a Windows 7 computer running McAfee Security Center, or whatever its called. I didn’t want that, because McAfee seemed to be interfering with multiple other programs that needed to download and install updates — Java, Flash, Zune. So my idea was to scrap McAfee and replace it with the free Microsoft Security Essentials. I stopped and uninstalled McAfee, and here I had to resort to a special Mcafee-provided tool to uninstall. (That McAfee requires a special install tool ought to be a crime).
After uninstalling McAfee and installing MSE, the Windows Firewall could not or would not start. I found that the registry keys in HKLM\CurrentcontrolSet\Services\MpsSvc were completely missing. Nice one, McAfee! So in order to fix THAT, I had to export the appropriate regkey tree from a working Windows7 computer, and then import it on the ailing computer.
I don’t actually know if that step was necessary, because when I tried net start mpssvc after importing the reg keys, the firewall still did not start. But it seemed that adding the missing regy keys was at least benign. It could be that the firewall once started would have created those keys anyway. I don’t know. In any case, try doing the copy/graft I described here if you still have the problem.
Good luck to everyone, and Happy Thanksgiving. This problem REALLY, REALLY should not be so complicated.
Windows firewall service error
This forum is closed. Thank you for your contributions.
Answered by:
Question
Answers
- Marked as answer by Magon Liu Moderator Tuesday, October 11, 2011 10:03 AM
All replies
Sir, Please try these steps it will be Started :
- Click Start, Run and typeServices.msc
- Double-click theNetwork Connectionsentry
- Set itsStartup typeto Manual
- ClickStartto start the service
- Double-clickWindows Management Instrumentation
- Set its Startup type toAutomatic
- ClickStartto start the service.
MCP | MCTS | MCITP
OK, try from CMD
Start —> CMD «Run As Administrator» —> netsh firewall set opmode enable
MCP | MCTS | MCITP
Thanks for the help its most appreciated this is the report
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Michael>netsh firewall set opmode enable
The service has not been started.
C:\Users\Michael>sc start DCOMLaunch
[SC] StartService FAILED 1056:
An instance of the service is already running.
C:\Users\Michael>sc start RpcSs
[SC] StartService FAILED 1056:
An instance of the service is already running.
C:\Users\Michael>sc start BFE
[SC] StartService FAILED 1058:
The service cannot be started, either because it is disabled or because it has n
o enabled devices associated with it.
C:\Users\Michael>sc start mpsdrv
[SC] StartService FAILED 1056:
An instance of the service is already running.
C:\Users\Michael>sc start MpsSvc
[SC] StartService FAILED 1068:
The dependency service or group failed to start.
- Windows Firewall is not the default firewall
- Windows Firewall does not start
- Windows Vista could not start Windows Firewall. Service-specific error 5 (0x5)
- Remote Assistance does not work
- You cannot access shared files and printers
MCP | MCTS | MCITP
I already tried «Microsoft fix it» it couldnt find the solution. This is the report
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Michael>sc config BFE start= auto
[SC] ChangeServiceConfig SUCCESS
C:\Users\Michael>sc start BFE
SERVICE_NAME: BFE
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 2 START_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x7d0
PID : 2040
FLAGS :
C:\Users\Michael>sc start MpsSvc
SERVICE_NAME: MpsSvc
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 2 START_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x7d0
PID : 2040
FLAGS :
- Marked as answer by Magon Liu Moderator Tuesday, October 11, 2011 10:03 AM
Really surprised me to see no-one start with a question, although MCP’s are all trained to do this..
The user has come back with an entirely different ‘solution’ to those launched into by our so-called professionals here, related directly to what was going on in his/her system at the time (in this case an update). Another example might be that some advice on stopping various other services to speed up XP ‘for free’ had just been followed — just fixed exactly this problem, with exactly the same error messages on another PC after a user had done this, simple by racking down the services menu and starting all the commonly running services.