Result

On Windows Vista computers, you find that the Windows Firewall service is not running. When you try to manually start the service, you get the error mentioned below. This problem may also occur for the DHCP Client service, or the "Diagnostic Policy Service" service.

Here are the errors for the "Windows Firewall" service: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.

In the System event log, you see the following event:
Source: Service Control manager Eventlog Provider.
Event ID: 7024
The Windows Firewall service terminated with service-specific error 5 (0x5)
Back to the top

Cause

The error means "Access is denied". This may happen if the "MpsSvc" account doesn't have the necessary permissions for the related registry keys.

For the NT Service\MpsSvc account, it needs permissions for the following keys:

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Epoch
  permission needed: Query Value;Set Value
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy
  permission needed: Full Control;Read
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Defaults\FirewallPolicy
  permission needed: Full Control;Read

For the DHCP Client service, the issue may occur if the "NT Service\DHCP" account does not have the necessary permissions for the following keys:

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp
  permission needed: Query value, Create value, Enumerate Subkeys, Notify, Read Control
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp\Configurations
  permission needed: Full Control, Read

For the "Diagnostic Policy Service" service, the issue may occur when the account Trustedinstaller is missing the permissions for the key below:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DPS\Parameters
permission needed: Full Control, Read
Back to the top

Resolution

Automatically diagnose and fix common Windows Firewall, such as the following:

• 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

To download and run this automated troubleshooter, click the Fix this problem link: Fix this problem
Microsoft Automated Troubleshooting Services: Diagnose and fix Windows Firewall service problems automatically

If you would prefer to fix this problem yourself rather than using the above automated troubleshooter, add the permission for the account on these registry keys. For example, here are the steps for the Windows Firewall service:

1. In Registry Editor, browse to the key for which you need to add permission.
2. Right click the key, and click Permissions.
3. Make sure Locations is selected to be the local computer.
4. In the "Enter the object names to select field, type "NT SERVICE\mpssvc". Then click "Check name."
5. Click OK.
6. Then select the account which appears in the list, and add the appropriate permission for it.
7. When this is done, click OK.

Back to the top Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.
Back to the top

APPLIES TO

• Windows Vista Business
• Windows Vista Enterprise
• Windows Vista Ultimate

Back to the top

Article ID:
943996

Last Review:
August 20, 2010 - Revision: 2.0