We've noticed that hung/disconnected sessions impede the USERS console command from running. Killing the session will allow >USERS to run properly. We can confirm that the hung session cannot be connected to via DBG. (Windows Environment). Is it possible to adjust the USERS Console Command to not hang when it encounters a session that it cannot connect to? We can see the session listed via Task Manager, but no obvious visual queues indicate that it's hung.