Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Please add some screenshots of the error messages popups that you get.
    – harrymc
    Commented Apr 8, 2023 at 10:24
  • 1
    Look at Powershell /? options from command line. There are switches to pass to powershell.exe such as -NoProfile or -NonInteractive that may help make the powershell.exe footprint smaller. I would never process 100 processes at the same time concurrently and ensure whatever scripted processes I am launching is optimized for the system which is it running, throttle or queue the processes for x thread, etc. I don't see why you need 100 terminal sessions active anyway and you should log your processes and look at the logs for whatever you need the terminal open for output wise, etc. Commented Apr 8, 2023 at 14:10
  • So change your 'terminal sessions open per PHP CLI execution' and figure out whatever ultimate goal you have (reason you need 100 instances opened and minimized, tabs, etc.) and figure out a more optimized way to handle the task per whatever "requirement" constraints you have. PowerShell is not cmd so if you must use PowerShell, this is a downside, time to change strategy. Take that back to the powers that tell you any new requirements and let them know this is a downside to the technology and then brainstorm and test to optimize your processes on the system you run them with the tool you use. Commented Apr 8, 2023 at 14:13
  • We cannot tell you why different programs behave differently, we aren't the devs. I recommend you edit your question including the title, to remove this unanswerable part and focus on an specific question we CAN answer. Commented Apr 9, 2023 at 20:53