Case 2: after you installed Configuration Manager 2007 on Hyper-V host computer, we can’t start VM. It is not recommended to run any other features/applications on Hyper-V host.

Case 3: In my case, the BCD settings in the hypervisor automatic startup type is disabled. Re-enabling auto-startup of hypervisor and rebooted the system by running this command: bcdedit /set hypervisorlaunchtype auto.

Case 4: Whenever rebooting the Hyper-V host, we loss all VM. The problem is Officescan antivirus from Trendmicro. Un-installing Trendmicro fix the problem.

Case 5: After migrating a VM from Windows 2008 to Windows 2008 r2, I can’t start the VM with these errors:

Event ID 3040: Symantec AV Manager' could not initialize. (Virtual machine ID 9C99D5D2-34A1-45A5-814D-30F9145D3D6D)

Event ID 3080: Symantec AV Manager' could not create or access saved state file F:\Hyper-V\Symantec AV Manager\Virtual Machines\9C99D5D2-34A1-45A5-814D-30F9145D3D6D\9C99D5D2-34A1-45A5-814D-30F9145D3D6D.vsv. (Virtual machine ID 9C99D5D2-34A1-45A5-814D-30F9145D3D6D).

It was NTFS permissions problem. Previously, I have changed default D: drive permissions to only allow 'Full Access' for Administrators and SYSTEM group to root of the D: drive. I 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).

Also check these links: