when a Session was disconnected, WVD will not assign the previous host for a new connection

Copper Contributor

Hey there,


related to:




We have a host pool with 2 Windows 10 Multi User hosts running fine. Profiles are shared via FSLogix and Azure File Storage. So far everything is working great. But:


When a user loses his session for whatever reason - network problems, inactivity or RD App closed - and he tries to reconnect, the WVD broker sometimes assigns him the other host and not the one with the existing session. As we are using profile containers the login is denied because the container is locked by the other session. (The denial is expected behavior. We don't want to have temporary profiles.)


Is there any update on this issue, or may we have a configuration problem?

Shouldn't this be a supported scenario?


Greetings from Hamburg,

Valentin Beller

1 Reply