Home | Site Map | Cisco How To Net How To | Wireless | Search | Forums | Services | Setup Guide | Careers | About Us | Contact Us|

Chicago Area Laptop for rent: $35 per day plus $10 for additional day
rental

 

Can't start Virtual Machine in Hyper-V after changing the drive letter
Event ID 3040, 4096, 3070 and 16410 - Microsoft-Windows-Hyper-V-Config
Hyper-Virtual machine error: The system cannot find the path specified. (0x80070003)
Hyper-Virtual machine error: could not initialize
Hyper-Virtual machine error: could not read or update virtual machine configuration: Unspecified error (0x80004005)
Hyper-Virtual machine error: cannot access the data folder of the virtual machine

Situation: The client is running a VM on Hyper-V and it is located in the E drive. After he changed the Drive letter fro E to F, he can't start the VM with these Event IDs.
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Event ID: 3040
Level: Error
Description:
'FE' could not initialize. (Virtual machine ID E67C4C23-1E2A-4974-A0DE-710D051B6A7A)

Source: Microsoft-Windows-Hyper-V-Config
Event ID: 4096
Level: Error

The Virtual Machines configuration E67C4C23-1E2A-4974-A0DE-710D051B6A7A at 'E:\ProgramData\Microsoft\Windows\Hyper-V\FE' is no longer accessible: The system cannot find the path specified. (0x80070003)

Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Event ID: 3070
Level: Error
Description:
'FE' could not read or update virtual machine configuration: Unspecified error (0x80004005) (Virtual machine ID E67C4C23-1E2A-4974-A0DE-710D051B6A7A)


Source: Microsoft-Windows-Hyper-V-VMMS
Event ID: 16410
Level: Error
Description:
'FE' cannot access the data folder of the virtual machine. (Virtual machine ID E67C4C23-1E2A-4974-A0DE-710D051B6A7A)

Case 1: after changing the VM located drive letter from E to F, you may receive this errors.

Case 2: when attempting to import VM exported from other server, you may receive these Event IDs.

Resolution: 1. Deleted the VM and Re-create it. These posts may help:

Cannot connect to virtual machine configuration storage ...

3 posts - 2 authors - Last post: Jun 23
After removing Microsoft Failover Clustering and rebooting the Hyper-v server, we can't start the VM with Saved-Critical - Cannot connect to ...
chicagotech.net/netforums/viewtopic.php?f=3&t=14009

Move Vuirtual Hard disk to different drive - ChicagoTech.net

5 posts - 1 author
Move Vuirtual Hard disk to different drive. Post by guest » Sun May 01, 2011 3: 13 pm. I read the following post, but can't follow the instruction. ...
chicagotech.net/netforums/viewtopic.php?f=3&t=14677

2. 2008 R2 does not support AVX supported by Sandy bridge. Microsoft has a hotfix thatmay fix the problem:http://support.microsoft.com/kb/2517374

3. In other case, it is permission issue. The client has changed default D: drive permissions to only allow 'Full Access' for Administrators and SYSTEM group to root of the D: drive.

We solved my problem by adding 'Authenticated Users' group to the root of D: drive and allowed 'List' permission with a scope 'This folder only' (You should do this via Advanced permission management). .

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

 

 

 

Bob Lin Photography services

Real Estate Photography services 

 

  This web is provided "AS IS" with no warranties.
Copyright © 2002-2018 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.