Hyper-V: "Object was not found" but the vmms service is working

Alvin Chipmunk 0 Reputation points
2025-02-01T02:35:49.9333333+00:00

I cannot connect to my local Hyper-V with Hyper-V Manager. I get error:

Hyper-V encountered an error trying to access an object on computer 'XXXXX' because the object was not`` ``found. The object might have been deleted, or you might not have permission to perform the task. Verify that the`` ``Virtual Machine Management service on the computer is running.

Running Get-VMHost or Get-VM in the PowerShell console gives the same error.

VMMS is working.

MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof didn't help.

Reinstalling Hyper-V (removing it from the Windows Features, then deleting folder C:\ProgramData\Microsoft\Windows\Hyper-V, then adding the Hyper-V feature back) didn't help.

Windows 11 Enterprise build 27774.

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,806 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Tom F 0 Reputation points
    2025-02-04T15:14:15.3333333+00:00

    Just run into this again, which we regularly do.

    MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof normally fixes it, but this time has not.

    Edit: 20 minutes later this has randomly started working again

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.