Daniel, et al. It seems a "simple" answer to the Force logoff question may have been overlooked.
Could it be the software was "less sensitive" to whether the incoming connection (that's you) is Local [i.e. connecting to the VM on your Local Host] or Remotely [i.e. connecting in from another computer either on the Local network -or- across the Internet]?
Virtual Machines (VMs) once they have established a User profile for any given session WILL (I believe) work to maintain that "session" until commanded to logoff and 'end session' by the User.
Why the VM simply couldn't 'connect to' the already established session IS the big mystery! ~ Asking which "bit" such as a Cookie, local soft "token" or temporary O.S. Registry setting are what identifies YOU (your incoming session) from the previous 'connect' would have been my next question to ask?
So, it seems you asked a good question but that this "behavior" may have been entirely normal in nature, unless since the time you posted the question (in April 2021), you managed to identify and confirm another-choice [option, setting or preference] that caused the Force logoff message to stop happening?
I hope this reply helps a little bit. (If nothing else, it confirms the issue "lives on" still, from the time you asked it.)