# Kibana.bat errors on Windows 10 **URL:** \ **Category:** Kibana\ **Created:** [November 10, 2015, 11:27am UTC](https://discuss.elastic.co/t/kibana-bat-errors-on-windows-10/34233 "2015-11-10T11:27:35Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![PaulBrown](https://avatars.discourse-cdn.com/v4/letter/p/e19adc/32.png) [@PaulBrown](https://discuss.elastic.co/u/PaulBrown)\ **Post date:** [November 10, 2015, 11:27am UTC](https://discuss.elastic.co/t/kibana-bat-errors-on-windows-10/34233/1 "2015-11-10T11:27:35Z")
HI, I'm new to all this Elastic Search and Kibana technology but have started to look at it. I've downloaded and installed ElasticSearch-2.0.0 and that's working fine. To go with this I've downloaded Kibana-4.2.0-windows but when I try to run Kibana.bat I get the error message \nodejs\node.exe was unexpected at this time. and nothing runs. Any help would be much aprreciated ---
**Author:** ![brnkrygs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brnkrygs/32/5890_2.png) [@brnkrygs](https://discuss.elastic.co/u/brnkrygs)\ **Post date:** [November 13, 2015, 3:49am UTC](https://discuss.elastic.co/t/kibana-bat-errors-on-windows-10/34233/2 "2015-11-13T03:49:05Z")
Hi Paul, I've been trying out the new Elasticsearch 2.0 stuff on windows as well, and ran into this error. I don't know what the source of the problem is - but I know in my case I already had nodejs installed. Wondering if it is a path conflict or something... Anyway, I was able to bypass /bin/kibana.bat and run node directly against what the .bat file sets up. Basically it boils down to: > path\_to\_nodejs.exe /path/to/kibana/src/cli/index.js so I ran that with my system instance of node like this: > cd kibana-4.2.0-windows\src\cli > node index.js and it started just fine! ---
**Author:** ![PaulBrown](https://avatars.discourse-cdn.com/v4/letter/p/e19adc/32.png) [@PaulBrown](https://discuss.elastic.co/u/PaulBrown)\ **Post date:** [November 16, 2015, 10:21am UTC](https://discuss.elastic.co/t/kibana-bat-errors-on-windows-10/34233/3 "2015-11-16T10:21:59Z")
Thanks for that, that's exactly what I had ended up doing myself. Would be nice to know what the underlying cause is! ---
**Author:** ![ronwest99](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@ronwest99](https://discuss.elastic.co/u/ronwest99)\ **Post date:** [December 4, 2015, 5:16pm UTC](https://discuss.elastic.co/t/kibana-bat-errors-on-windows-10/34233/4 "2015-12-04T17:16:26Z")
I figured out how to resolve . Even if you have node already installed, you have to add the node directory to your windows path. on my machine I added: C:\Elastic\kibana\node to the path and everything works now. ---
**Author:** ![mweber](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@mweber](https://discuss.elastic.co/u/mweber)\ **Post date:** [December 17, 2015, 6:18am UTC](https://discuss.elastic.co/t/kibana-bat-errors-on-windows-10/34233/5 "2015-12-17T06:18:42Z")
There is a problem with spaces in the path. Just add quotes around %SYS\_NODE% where you set the NODE variable on the line 14 of kibana.bat : _old:_ set NODE=%SYS\_NODE% _new:_ set NODE= **"** %SYS\_NODE% **"** After that fix, it works on my WIndows 10 machine. ---
**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 17, 2015, 5:37pm UTC](https://discuss.elastic.co/t/kibana-bat-errors-on-windows-10/34233/6 "2015-12-17T17:37:34Z")
Thanks for the fix. We're planning to remove the whole system node fallback stuff from the build in the near future as well, so this code won't even be there anymore. See [https://github.com/elastic/kibana/issues/5673](https://github.com/elastic/kibana/issues/5673) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:06pm UTC](https://discuss.elastic.co/t/kibana-bat-errors-on-windows-10/34233/7 "2017-07-06T14:06:22Z")