Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently bought an Asus laptop equipped with i5-3317u 1.70GHz and Windows 8. Upgraded to Windows 8 Pro and added the hyper-v feature.

Creating a VM goes OK but trying to start it, it fails with a message "could not initialize" and event id 3040.

I have searched all over and can't see what's wrong.

share|improve this question

migrated from Mar 2 '13 at 18:02

This question came from our site for professional and enthusiast programmers.

Did you verify that Virtualization is activated in bios? Did you restart your computer after installing the hyper-v feature? Check this microsoft article on the subject: – OakNinja Mar 2 '13 at 23:16
verified the bios settings and restarted after adding the hyper-v feature. I don't understand this MS article: 1. it relates to Win 2008 rather than Win 8 2. access? the service runs under the localservice account. this should be sufficient, right? – Uri Mar 3 '13 at 21:20
Regardless of windows version, the feature/application throws the same error(3040). Could you start the event viewer and post the full hyper-v error here? You could also try unistalling hyper-v and install the application VMware Player(freeware) just to check that your virtualization works at all. – OakNinja Mar 3 '13 at 23:00
I tried removing hyper-v, installed VMware player. result: VMware player works. After that I removed VMware player and reinstalled Hyper-V and I get the same error: 'New Virtual Machine2' could not initialize. (Virtual machine ID DE5F9FC4-6A82-4039-85E3-18A82A938FEE) Log name: Microsoft-Windows-Hyper-V-Worker/Admin Source: Hyper-V-Worker Event ID: 3040 – Uri Mar 4 '13 at 20:56
Try setting up a new user with admin rights, and set up a new machine from that account. Report back after that. – OakNinja Mar 6 '13 at 19:17

I'm running 8.1 Pro and this error came long with zero effective fixes. Finally I came across this:

The fix:

From an elevated command prompt:

net localgroup administrators LOCAL /delete

net localgroup administrators SERVICE /delete

Afterwards, you'll get a "could not create or access saved state file" error along with the initialize error. When trying to run a VM.

Note the VM ID, goto C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines and in the folder with the same name as the VM ID, delete the .bin and .vsv file. - No VM's should be running at this point.

Launching the VM you'll see that your VM will be back up.

In my case, Hyper-V had been running fine all along and then after month or two of it not being used, I got the inexplicable error. This fixed it.

share|improve this answer

Same error, Same disappointing "Fixes". I found that the system created a virtual drive in a location that required elevation to access. I created a new virtual drive under my profile and afterwards had a successful start

share|improve this answer
this looks like a a comment than an answer... – Francisco Tapia Jul 9 '15 at 18:56

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.