Skip to main content

I am running Hyper-V on a Windows 11 laptop. I have installed VBR on the same laptop. I cannot connect to the “server”. I get the following message: 

The validation information class requested was invalid.
Failed to logon user uxxx\xxx]

Check the format of the user being used in the connection - hostname\username is what you need to use -- laptop\administrator as an example.

 
 
 

There are many posts in the community on this issue.  Just do a quick search and you should find them.


Check the format of the user being used in the connection - hostname\username is what you need to use -- laptop\administrator as an example.

 
 
 

The format is correct.


There are many posts in the community on this issue.  Just do a quick search and you should find them.

When I search for this error message, the only message that it finds is mine.


There are many posts in the community on this issue.  Just do a quick search and you should find them.

When I search for this error message, the only message that it finds is mine.

Do a general search for hyper-v not the specific message.


Not even sure you're setup will work...running HV & VBR on same device. 

But, try disabling the f/w & UAC (in windows & registry) 


Please also note, HyperV on Windows client OS is not supported „for taking backups“. There should be an error message in a backup job session which will tell you so.

But you can use HyperV on Windows 11 as a target for Instant Recovery or SureBackup Jobs.

 

Best,

Fabian


Not even sure you're setup will work...running HV & VBR on same device. 

But, try disabling the f/w & UAC (in windows & registry) 

But I can install VBR on another Windows 11 machine and access Hyper-V on this machine?


@Djurden - according to the Platform/Systems support section of the HV Guide, Win10/11 is not supported for HV backup, but only for targets for Instant Recovery and Surebackup Jobs (see subscript 1 under the Platform Support table)


Hyper-V on windows workstation is different than Hyper-V on windows server, and VBR can’t connect to Hyper-V on windows workstation.


Comment