Application encountered an error when starting a VM in Hyper-V

If you recently made a change to the Boot Configuration Data store, you may see this error when starting a VM in Hyper-V

First, verify that virtualization support is turned on in your BIOS. If it is and a power cycle of the server does not resolve the problem, you may not have the Hypervisor loading during the boot sequence. To check for this problem, open a command prompt with administrative privileges.

Type bcdedit and press Enter.

Tyhe output in red is the currently loaded boot configuration The output in blue is a boot configuration that will allow Hyper-V to run. Notice the data in green is missing from the current boot configuration.

Type bcdedit /set {current} hypervisorlaunchtype auto and press Enter. You should get a response The operation completed successfully.

Type bcdedit to see the new results.

Now, restart the server and give it a try.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog