Hyper-V - cannot create new VM

[Alistair J R Young]

As soon as I get to the point of hitting "Finish" on the new virtual machine
wizard, I get this error:

[Window Title]
New Virtual Machine Wizard

[Main Instruction]
The server encountered an error while creating HERA (Intranet).

[Content]
Failed to create a new virtual machine.

An unexpected error occurred: A required privilege is not held by the
client. (0x80070522)

[Expanded Information]
Failed to create a new virtual machine.

'HERA (Intranet)' encountered an unexpected error: A required privilege is
not held by the client. (0x80070522) (Virtual machine ID
316E5E77-BC4D-401F-B81D-7F5E28B7BDBE)

[^] Hide details [Close]

...this happens no matter the name of the VM, and even when stripped to the
bone by not trying to connect it to a network or add a virtual hard drive at
the same time. The same error is logged in the event log simultaneously,
source and ID as below:

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Event ID: 16020
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: Olympus.arkane-systems.lan

Anyone seen this one before, and hopefully know how to fix it?

Thanks in advance,

Alistair

[Bret]

I had this issues also. It appeared to be a software conflict with Intel
Management Tools. I found a similiar post on the web. The only resolve was
to reinstall the OS. After reinstalling the OS and only installing the
chipset drivers I was able to setup my VM. I have not attempted to update
any other drivers on the current install.

Hope it helps

Bret

"Alistair J R Young" <ava...@arkane-systems.net> wrote in message
news:58A868D1-3EAF-4893...@microsoft.com...

[Alistair J R Young]

Unfortunately, it's a Dell server with no third-party drivers installed on
it, and specifically not Intel Management Tools, so I have to presume it's
something different.

Thanks, though,

Alistair

"Bret" <tech...@newsgroup.nospam> wrote in message
news:ObHR8AeF...@TK2MSFTNGP03.phx.gbl...

[Chris]

I had the exact same problem and was able to fix it by changing the default
folder to store the virtual hard disk files and machine configuration files.