# Pipeline not created during setup of packetbeat 8.15.1 on windows **URL:** \ **Category:** Beats\ **Tags:** packetbeat\ **Created:** [September 17, 2024, 7:46am UTC](https://discuss.elastic.co/t/pipeline-not-created-during-setup-of-packetbeat-8-15-1-on-windows/366656 "2024-09-17T07:46:50Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![jimB100](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@jimB100](https://discuss.elastic.co/u/jimB100)\ **Post date:** [October 11, 2024, 2:28pm UTC](https://discuss.elastic.co/t/pipeline-not-created-during-setup-of-packetbeat-8-15-1-on-windows/366656/4 "2024-10-11T14:28:06Z")
turns out it's a bug in the windows version during the initial implementation. if you run the setup from a linux platform it creates all the pipelines and works a treat. as it only needs to do this once to set everything up, that's what we did, we now have windows clients reporting into elastic. don't know if that helps, or whether you've already found an alternate way of doing what you were looking at, just thought i'd mention it > [@Pipeline with id \[packetbeat-8.15.2-routing\] does not exist, dropping event!](https://discuss.elastic.co/t/pipeline-with-id-packetbeat-8-15-2-routing-does-not-exist-dropping-event/368135/12): > > packetbeat installed on linux and all working great! --- _[View the full topic](https://discuss.elastic.co/t/pipeline-not-created-during-setup-of-packetbeat-8-15-1-on-windows/366656)._