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

2 answers

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

  2. Ian Xue 39,281 Reputation points Microsoft Vendor
    2025-02-05T00:08:53.5733333+00:00

    Hi Alvin Chipmunk,

    Thanks for your post. Before moving on, to narrow down the issue, please see the related logs at first. Below are the current event log channels for Hyper-V. Using "Event Viewer" you can find them under "Applications and Services Logs", "Microsoft", "Windows".

    Reference. https://techcommunity.microsoft.com/blog/virtualization/looking-at-the-hyper-v-event-log-january-2018-edition/382411

    Also, please try the following methods.

    1. Ensure that the account you are using to connect to the Hyper-V server has the necessary permissions. Verify that you are a member of the Hyper-V Administrators group or have the required rights to manage virtual machines.
    2. If you went to HyperV VMMS log and checked the error. It Identified the problem being a VM that no longer exited. Try the following steps.
      1. Shut down VMMS service.
      2. Went to the %systemdrive%\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines directory and deleted that link file.
      3. Restarted VMMS

    Best Regards,

    Ian Xue


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    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.