Tweaking.com Support Forums

Main Forum => Tweaking.com Support & Help => Topic started by: nickrad on July 01, 2016, 03:59:46 pm

Title: Windows Repair AIO breaks Hyper-V - Solved
Post by: nickrad on July 01, 2016, 03:59:46 pm

I had a problem today with Hyper-v on Windows 10 Pro that I eventually traced back to Windows Repair AIO.

Steps to reproduce:

1. Run the "repair wmi" option on a Windows 10 pro system with the optional hyper-v feature enabled.

2. Run the "hyper-v manager" program.

Result: Hyper-v manager will fail to start with error "invalid class". Also logs 3 errors in the event log:

Code: [Select]

The latest class definitions for the WMI namespace 'root\virtualization\v2' are not registered in the CIM repository.

Source: Hyper-V-VMMS
EventID: 19010

Code: [Select]

Virtual Machine Management service failed to start.

Source: Hyper-V-VMMS
EventID: 14096

Code: [Select]

The Hyper-V Virtual Machine Management service terminated with the following error:
Not enough storage is available to complete this operation.

Source: Service Control Manager
EventID: 7023
Resolution: Run the following commands from an elevated command prompt:

Code: [Select]

mofcomp  %systemroot%\system32\WindowsVirtualization.v2.mof

Code: [Select]

Mofcomp %systemroot%\system32\en-US\WindowsVirtualization.v2.mfl

Title: Re: Windows Repair AIO Bug Report - Hyper-V - Solved
Post by: nickrad on July 01, 2016, 04:16:07 pm

Just to be clear, I solved the issue myself. This is just a bug report so the developers can figure out what's causing the problem and prevent it from happening.

Unfortunately I can't help explain why it's happening. The log file for your program clearly says that it's registering those 2 files, but I guess it's not taking? I have no idea, I just know that I can reliably reproduce and solve the issue using the steps above.

Anyway, I attached the log file in case it helps.