First of all, don’t tell me what you will and will not do, young lady.

I was receiving the error below when trying to connect to a VM through Hyper-V Manager:

The fix was easily found in the TechNet Forums (in case that link isn’t active in the future, I’ve documented the fix for posterity below).

The fix:

Copy and paste the following into a text file and save it as a *.reg file:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowDefaultCredentials]
“Hyper-V”=”Microsoft Virtual Console Service/*”

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowDefaultCredentialsDomain]
“Hyper-V”=”Microsoft Virtual Console Service/*”

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentials]

“Hyper-V”=”Microsoft Virtual Console Service/*”

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsDomain]

“Hyper-V”=”Microsoft Virtual Console Service/*”

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsWhenNTLMOnly]

“Hyper-V”=”Microsoft Virtual Console Service/*”

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsWhenNTLMOnlyDomain]

“Hyper-V”=”Microsoft Virtual Console Service/*”

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowSavedCredentials]

“Hyper-V”=”Microsoft Virtual Console Service/*”

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowSavedCredentialsDomain]
“Hyper-V”=”Microsoft Virtual Console Service/*”

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowSavedCredentialsWhenNTLMOnly]
“Hyper-V”=”Microsoft Virtual Console Service/*”

Now import it into your registry and enjoy your new Credssp configuration.