# Kibana showing 'WHERE' is not an int or ext command on start up

**URL:** <https://discuss.elastic.co/t/kibana-showing-where-is-not-an-int-or-ext-command-on-start-up/36544>\
**Category:** Kibana\
**Created:** [December 7, 2015, 3:05pm UTC](https://discuss.elastic.co/t/kibana-showing-where-is-not-an-int-or-ext-command-on-start-up/36544 "2015-12-07T15:05:33Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [December 14, 2015, 10:13pm UTC](https://discuss.elastic.co/t/kibana-showing-where-is-not-an-int-or-ext-command-on-start-up/36544/5 "2015-12-14T22:13:05Z")

</div>

Apparently WHERE should just be part of cmd.exe. Why you don't have it on your system, I do not know. Why the bat script stops I also do not know, as I don't see the same thing happening on my end.

The bottom line is, we should be shipping different script files with the build that don't try to fall back to any system-installed node version anyway.

---

_[View the full topic](https://discuss.elastic.co/t/kibana-showing-where-is-not-an-int-or-ext-command-on-start-up/36544)._