# Help making system.util.execute work on Windows **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [June 5, 2024, 9:12am UTC](https://forum.inductiveautomation.com/t/help-making-system-util-execute-work-on-windows/91396 "2024-06-05T09:12:38Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 5, 2024, 11:45am UTC](https://forum.inductiveautomation.com/t/help-making-system-util-execute-work-on-windows/91396/2 "2024-06-05T11:45:02Z")
> [@diamond](#): > > Permission problems does not make sense to me because, if so, Ignition would not run either. Simply not true. Ignition only needs local privileges to run, and that is all it gets when running as the default LOCAL SYSTEM user. The service also has no connection to what you do on the desktop **as far as networks are concerned** , so your testing in the terminal is insufficient. Instead of using `system.util.execute()`, which is fire-and-forget, use java's [ProcessBuilder](https://forum.inductiveautomation.com/search?q=ProcessBuilder%20order%3Alatest) so you can collect the output and error streams from your batch file's execution. --- _[View the full topic](https://forum.inductiveautomation.com/t/help-making-system-util-execute-work-on-windows/91396)._