Windows 8 HyperV fails with different Errors

I have windows 8 with Hyper-V, HyperV can create new virtual machines and assign resources to them but whenever I double click on Virtual machine to open it's window nothing happens .. 

in the eventviewer I checked if there are any logs and found various of them but no reference on the internet. I tried creating some crashdumps as well using Windows debug application but i couldn't get what's the issue.

I have attached those Crashdumps as well

Here are the errors i'm getting: 

Error      11.12.2012 15:18:57        .NET Runtime    1026      None

Application: vmconnect.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ArgumentException

Stack:

   at Microsoft.Virtualization.Client.Interop.IMsRdpClientNonScriptable3.set_NegotiateSecurityLayer(Boolean)

   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl.SetSecureModeOn()

   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl..ctor(Microsoft.Virtualization.Client.InteractiveSession.RdpConnectionInfo)

   at Microsoft.Virtualization.Client.InteractiveSession.InteractiveSessionForm..ctor(Microsoft.Virtualization.Client.InteractiveSession.RdpConnectionInfo)

   at Microsoft.Virtualization.Client.InteractiveSession.VmisApplicationContext.TryParseCommandLine(System.String[])

   at Microsoft.Virtualization.Client.InteractiveSession.Program.Main(System.String[])

 

Error      11.12.2012 15:18:57        Application Error             1000      (100)

Faulting application name: vmconnect.exe, version: 6.2.9200.16384, time stamp: 0x50107744

Faulting module name: KERNELBASE.dll, version: 6.2.9200.16384, time stamp: 0x5010ab2d

Exception code: 0xe0434352

Fault offset: 0x00000000000189cc

Faulting process id: 0x199c

Faulting application start time: 0x01cdd7a2133d765b

Faulting application path: C:\Windows\system32\vmconnect.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 512a4673-4395-11e2-be87-506313e50cb5

Faulting package full name:

Faulting package-relative application ID:


Warning              11.12.2012 15:11:19        disk        153         None

The IO operation at logical block address e17e3c0 for Disk 0 was retried.

Error      11.12.2012 15:11:45        volsnap                14           None

The shadow copies of volume C: were aborted because of an IO failure on volume C:.

Any advise would be highly appreciated 

thanks

December 11th, 2012 5:29pm

Hi ,

From the information you provided it seems that the policy or some configuration does not allow RDP to negotiate security layer. 

at Microsoft.Virtualization.Client.Interop.IMsRdpClientNonScriptable3.set_NegotiateSecurityLayer(Boolean)

Please check those settings and compare with default settings to see any difference.

Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security

Please also check the following registry key with a working Windows 8 and see if any differences. (Especially credssp.dll in SecurityProviders value)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Lsa
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SecurityProviders

I would like to know if the vm can be connected before. Is there anything changed before the issue occurs? 

Thanks. 

Free Windows Admin Tool Kit Click here and download it now
December 12th, 2012 2:48pm

There are 7 options in security and all of them are not configured. One has got my attention in relation to what you have mentioned Require use of specific security layer for remote (RDP) connections.

 

I changed this to Enable, disable and not configured. And tried to connect to VMachines but non responded and same errors shown on the event viewer.

 

 

 

 In the registry as you can see below the value which you've mentioned doesn't exist! not sure if it's a bug but it has been like this since Windows 8 was installed and I don't have a second machine to compare with. 

 

 

 

 

 

 

Any ideas ?

Thanks for your help

December 12th, 2012 3:32pm

Hi,

Exactly the same problem, at least same error in event viewer.

Hyper-v will create Virtual Machine - but cannot connect. Just a silent fail and exception recorded in event viewer when trying to connect.

I have windows 8 pro - VS12 pro -  phone 8 SDK.

The problem became apparent  from not being to start the Windows Phone 8 emulator.

I have this same problem on both my win8 machines.

Reluctant to do a clean install form OS upward, esp if there is a simpler solution.

Have tried deleting and recreating the internal switch.

Removed AV -webroot - problem persists.

Tried Vmconnect from command line - same problem.

Reinstalled VS12 & phone 8 SDK- no success.

Cannot offer solutions - but you are not alone in this problem!

Free Windows Admin Tool Kit Click here and download it now
December 25th, 2012 10:04pm

I just created a Windows 8 VM on my server with Hyper-V and it works as expected

machine specs are useful in diagnosing problems

December 27th, 2012 3:59pm

Hi Vegan,

I have Sony Vaio Intel ICore7, 10 Gigs Ram, 320G HDD, Nvidia 512MB dedicated VGA ram.

I took some crashdumps from Windows Debug application, attached in link below

https://skydrive.live.com/redir?resid=82488EABA4ACDB15!2422&authkey=!AL_NC9Us_WFUdAw

Thanks a lot

Free Windows Admin Tool Kit Click here and download it now
December 27th, 2012 6:00pm

I suspect as Aaron Hu notes that this is a configuration problem.
This problem was not present on either of my machines 3 weeks ago i.e. they both worked with connecting to a Hyper-V vm instance.
Trying to think what I've loaded since it worked.

Webroot -AV - seems likely candidate . I've uninstalled but problem persisits. Of course that does not rule it out!
Acronis True Image -  possible.
Adobe Digital Editions - epub reader - don't think so.
Windows update?
My machines are AMD processored home built mongrels.

Both vmconnect.exe and xde.exe (from vs) generate the same exception in kernelbase.dl.

December 27th, 2012 8:53pm

did your machine come with windows 7 preinstalled?
Free Windows Admin Tool Kit Click here and download it now
December 27th, 2012 11:48pm

Mine yes, it came with windows 7 Pre-installed however, I have done a clean installation with Windows 8 Professional and it was working in the begining but later on it stopped working.. 

I haven't installed any application during this time though, could it be an update that caused this? 

December 28th, 2012 10:28am

Hi & thanks for taking the time to reply.

I did a clean upgrade to Windows 8 Pro. Was hoping Mohammed had installed something matching me!

Weird, you'd think getting the VM instance running was the hard bit.

Mohammed :

Have you installed any of :

Visual Studio 2010 c++

Visual Studio 2012 pro

phone 8 SDK

DX11 SDK

CCleaner - does touch the registry.

I have these on both my faulting machines.

Free Windows Admin Tool Kit Click here and download it now
December 28th, 2012 1:51pm

generally a notebook machine is not designed to work like a server

i use a corporate rig for my server and hyper-v works perfectly

December 28th, 2012 3:21pm

@Hallenshaker

Yes, Just Visual Studio 2010 c++ is installed.. I will unistall it and let you know.

@Vegan, Yes you're right but nowadays some notebooks or desktop-laptops are designed to operate like desktops .

I have another laptop Dell Precision-M6500 which has 32G Ram and 2 TB HDD size and it works just fine with VMware.

Free Windows Admin Tool Kit Click here and download it now
December 28th, 2012 4:25pm

vmware is yet another hypervisor with different requirements

I use hyper-v as that is the standard corporate tool from Microsoft

hyper-v needs a suitable server, using it with 8 has the same system requirements as a server

8 will run fine without a server rig as long as you are not using hyper-v

December 28th, 2012 4:35pm

Found a working W8 machine. re Aaron Hu

 

registry differences / working & non working machines

 

Windows 8 machine with working vmconnect ---------------------------

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

 

SamConnectAccountsExist         KEY NOT PRESENT

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders

 

credssp.dll

 

Widows 8 Failing machine  1 & 2 ---------------------------------------------

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

 

SamConnectAccountsExist        01

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders

 

msapsspc.dll

schannel.dll

digest.dll

msnsspc.dll

 -------------------------------------------------------------------------------------------------

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

LsaPid    - different on each machine

---------------------------------------------------------------------------------------------------

Tried setting SamconnetAccountExist to 0 on a non working machine - no luck. Same problem.

The list of security providers (wtf) looks intresting?!

Free Windows Admin Tool Kit Click here and download it now
December 28th, 2012 4:51pm

fiddling with the registry is not going to help, if you box does not have the required CPU support (SLAT etc) and a properly configured BIOS (UEFI) then you are not going to be able to get Hyper-V to work.

I use AMD in the shop and AM3 or higher processors will support the SLAT, Intel is not standardized the same way at all.

In addition SLAT requires many BIOS options to be enabled.

December 28th, 2012 5:00pm

Vegan, Could you please these BIOS options ? I like to give that a shot.

Free Windows Admin Tool Kit Click here and download it now
December 28th, 2012 5:03pm

DEP and VXd are 2 that come to mind, servers have these enabled desktops don't.

December 28th, 2012 5:06pm

Thanks Vegan,

Editing the registry  is a bit last ditch.

Thing is the hardware virtualization is working. The image can be seen  booting up in Hyper-V manager.(postage stamp size image). 

I have been able to connect to it in the past and now cannot.

I enabled Hyper-V on my W8 home theatre PC - it works AND I can connect to the virtual machine. This is a similar speced machine - but with practically nothing installed.

In Hyper-V if I try and connect to an image that isn't started, on a working machine you get a window up saying Start the virtual machine. On my non working machines I just get nothing, with the error described above in event viewer.

Needs a clean install of W8 , and to rebuild system - checking Hyper_v at each stage.

Just hoping an answer turns up before having to go to all that work.

Free Windows Admin Tool Kit Click here and download it now
December 28th, 2012 6:00pm

Thanks for your help Vegan, but i'll just go with the most popular Microsoft Windows solution "FORMAT & Reinstallation"... this is so frustrating! 

December 29th, 2012 12:29pm

Enjoy!

Free Windows Admin Tool Kit Click here and download it now
December 29th, 2012 4:17pm

I realize this is an old thread, but since it is the only result that comes up in Google for this problem, I figure it is best to keep it in one place.

I had the exact problem, with the exact same Event log error. Adding credssp.dll to the list of SecurityProviders in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders fixed it for me. 

My full registry entry now reads "msapsspc.dll, schannel.dll, digest.dll, msnsspc.dll, credssp.dll"

July 11th, 2013 12:11pm

Hi Vegan,

I have Sony Vaio Intel ICore7, 10 Gigs Ram, 320G HDD, Nvidia 512MB dedicated VGA ram.

I took some crashdumps from Windows Debug application, attached in link below

https://skydrive.live.com/redir?resid=82488EABA4ACDB15!2422&authkey=!AL_NC9Us_WFUdAw

Thanks

Free Windows Admin Tool Kit Click here and download it now
July 11th, 2013 1:25pm

I realize this is an old thread, but since it is the only result that comes up in Google for this problem, I figure it is best to keep it in one place.

I had the exact problem, with the exact same Event log error. Adding credssp.dll to the list of SecurityProviders in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders fixed it for me. 

My full registry entry now reads "msapsspc.dll, schannel.dll, digest.dll, msnsspc.dll, credssp.dll"

start a new thread

July 11th, 2013 1:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics