# Nomad hangs on Windows with user interactions

**URL:** <https://discuss.hashicorp.com/t/nomad-hangs-on-windows-with-user-interactions/17183>\
**Category:** Nomad\
**Created:** [November 4, 2020, 9:12pm UTC](https://discuss.hashicorp.com/t/nomad-hangs-on-windows-with-user-interactions/17183 "2020-11-04T21:12:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dylanmcsweeney](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/dylanmcsweeney/32/14305_2.png) [@dylanmcsweeney](https://discuss.hashicorp.com/u/dylanmcsweeney)\
**Post date:** [November 4, 2020, 9:12pm UTC](https://discuss.hashicorp.com/t/nomad-hangs-on-windows-with-user-interactions/17183/1 "2020-11-04T21:12:25Z")

</div>

Hi, I am brand new to Nomad and I’m trying to get it to work with a very simple bunch of Windows 10 machines for simple raw\_exec batch processing of some executables.

I’ve got it working with 3 machines using example material from the tutorials, nothing too complicated, but occasionally when I do something like “nomad server members”, it will just hang until I provide input to the Powershell window I was running the server from. I notice even the web UI will hang sometimes until I hit Enter or provide a Ctr-C to the server window and I’ve also seen it hang when submitting a Hello World job - it wouldn’t start processing the job or distribute it to a client until I hit Enter on the server window.

Any idea what could be causing this?

---

<div class="post-metadata">

**Author:** ![angrycub](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/angrycub/32/925_2.png) [@angrycub](https://discuss.hashicorp.com/u/angrycub)\
**Post date:** [November 6, 2020, 8:27pm UTC](https://discuss.hashicorp.com/t/nomad-hangs-on-windows-with-user-interactions/17183/2 "2020-11-06T20:27:21Z")

</div>

@dylanmcsweeney,

One of the most common things I’ve run into with regard to Nomad hanging when running interactively is when I accidentally have clicked in the powershell window and ended up in select mode.

 ![Screen Shot 2020-11-06 at 3.23.21 PM](https://global.discourse-cdn.com/hashicorp/original/2X/a/ae685b14d475490edb3ffa3084009d451e8778fe.png)

You can tell if you are in this state by a visible selection (even if it’s one character) and the title of the Powershell window starts with **Select**. If you hit escape, it will leave select mode and the application will resume.

I always turn off Quick Edit Mode in the Defaults and current window properties for Powershell to prevent this.

 ![Screen Shot 2020-11-06 at 3.19.41 PM](https://global.discourse-cdn.com/hashicorp/original/2X/8/89839240ceaabfa6fe6376d709746792a646b1c5.png)

[Running Nomad as a service](https://learn.hashicorp.com/tutorials/nomad/windows-agent) also helps to prevent this particular issue.

Hope this helps you out!

**Charlie Voiselle**  
Product Education, Nomad

---

<div class="post-metadata">

**Author:** ![dylanmcsweeney](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/dylanmcsweeney/32/14305_2.png) [@dylanmcsweeney](https://discuss.hashicorp.com/u/dylanmcsweeney)\
**Post date:** [November 6, 2020, 10:31pm UTC](https://discuss.hashicorp.com/t/nomad-hangs-on-windows-with-user-interactions/17183/3 "2020-11-06T22:31:48Z")

</div>

Wow, thanks! I have seen that before, but I totally forgot (I spend most of my day on Linux machines). I don’t have access to the lab right now, but I’ll check that out on Monday.

Thanks a lot for the tip, I’m all but certain that’s what happened.