Hyper-V: The Hyper-V Networking Management service should be configured to start automatically

Applies To: Windows Server 2008 R2

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Hyper-V Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

Operating System

Windows Server 2008 R2








The Hyper-V Networking Management Service is not configured to start automatically.


Virtual networks cannot be managed until the service is started.

When the service is not running, you cannot add, delete, or modify virtual networks. You also cannot modify the networking properties of any virtual machines on this server.


Use the Services snap-in or sc config command-line tool to reconfigure the service to start automatically.

By default, membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

To reconfigure the service to start automatically using the Windows interface

  1. Open the Services snap-in. (Click Start, click in the Start Search box, type services.msc, and then press ENTER.)

  2. In the details pane, right-click Hyper-V Networking Management Service, and then click Properties.

  3. On the General tab, in Startup type, click Automatic. To start the service, click Start.

To reconfigure the service to start automatically using the command line

  1. Open Command Prompt.

  2. Type:

    sc config nvspwmi start=auto
  3. To start the service, type:

    sc start nvspwmi