How to fix "Windows could not start the Hyper-V Virtual Machine Management service on Local Computer."

Status Name DisplayName

Stopped vmms Hyper-V Virtual Machine Management

Start-Service : Service 'Hyper-V Virtual Machine Management (vmms)' cannot be started due to the following error:

Cannot open vmms service on computer '.'.

At line:2 char:1

• Start-Service vmms

• 
      + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
  
     ServiceCommandException
  
      + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand
  
  

Stopped vmms Hyper-V Virtual Machine Management

FreePhysicalMemory : 782743668

TotalVirtualMemorySize : 814279820

FreeVirtualMemory : 793251828

Hola Jerico,

Thanks for sharing the error details and PowerShell output. I can see that the Hyper-V Virtual Machine Management service (vmms) is stopped, and that attempting to start it results in an error. Although error 0x8007000e indicates insufficient memory resources, it doesn't necessarily mean your computer is running out of physical RAM. The failure could also involve virtual memory or another resource needed by the service.

I'd start by checking a few things.

• First, open Task Manager, select Performance, and check the Memory section. Pay particular attention to the available memory and committed memory values. This will help determine whether Windows is experiencing memory pressure.
• Next, check that Windows is automatically managing the paging file. Press Windows + R, type sysdm.cpl, and press Enter. Under Advanced, select Settings in the Performance section. Select Advanced again, then Change under Virtual memory. Check whether "Automatically manage paging file size for all drives" is enabled. If it isn't, enabling it and restarting Windows may help, although we should first determine whether the paging file configuration is contributing to the problem. Microsoft discusses insufficient memory resources and paging file configuration here.
• I'd also recommend checking Event Viewer because the service failure may have generated a more specific error. Open Event Viewer and navigate to Applications and Services Logs > Microsoft > Windows > Hyper-V-VMMS > Admin. Look for errors recorded when you attempted to start the service. Check Windows Logs > System for related Service Control Manager errors as well. Microsoft's Hyper-V troubleshooting documentation recommends reviewing these logs to identify the underlying cause.

Also, could you clarify a few things?

• Are you running Windows 10, Windows 11, or Windows Server? Which version and build?
• Did Hyper-V previously work on this computer, or is this a new installation?
• When you ran Start-Service vmms, was PowerShell opened using Run as administrator?
• Could you also share any errors from the Hyper-V-VMMS Admin log that correspond to the failed startup?

Those details should help us narrow down whether we're dealing with a memory configuration problem, a permissions issue, or another Hyper-V service failure.

Thanks,

James