大网数据广告活动
账户与安全

Error 1079 when services fail to start

· 52CE 我爱测

Fixes error 1079 that occurs when some services fail to start on a computer that's running Windows 7.

This article helps fix error 1079 that occurs when some services fail to start on a computer that's running Windows 7.

Original KB number:   2478117

Symptoms

One or more of the following services may fail to start on a computer that's running Windows 7:

  • Windows Time (W32Time)
  • Windows Event Log (eventlog)
  • Windows Firewall (MpsSvc)

Additionally, when trying to start the service manually, you may receive the following error message:

Error 1079: The account specified for this service is different from the account specified for other services running in the same process

Cause

The service is started by the Local System account instead of the Local Service account (NT AUTHORITY\LocalService). The Local System account may have insufficient permissions to start the service.

Resolution

Set the service and any dependent services to run under the NT AUTHORITY\LocalService account.

For example, for the Windows Firewall service, follow the steps:

  1. Select Start, type Services.msc in the Search programs and files box, and then press Enter.
  2. Locate and double-click the Windows Firewall service.
  3. Select the Log On tab.
  4. In This account text box, type NT AUTHORITY\LocalService.
  5. Set both Password fields blank.
  6. Select Apply, and then select OK.
  7. Repeat these steps for the Base Filtering Engine service.
  8. Restart both services.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。