After updating to version 2.29.7 last night, the cmd / powershell commands from the Execute Command node are now briefly visible. Not fundamentally problematic, but when I’m working directly on the server, focus is lost every time (e.g. in Notepad or browser). Does anyone else have this issue? Is it something on my end or did it come with the new stable? Thanks.
Information on your n8n setup
n8n version: 2.29.7
Database (default: SQLite): SQLite
n8n EXECUTIONS_PROCESS setting (default: own, main): main
Running n8n via (Docker, npm, n8n cloud, desktop app): npm
Operating system: Windows Server 2019 Datacenter 1809
Hi @Pmayer Welcome!
That is coming from the new build, not your setup: on Windows the Execute Command node no longer launches the shell hidden in 2.29.7, so the cmd/powershell window flashes visibly and pulls focus off whatever you’re working in. There’s no node option or env var to toggle window visibility, so until it’s patched the only reliable way to get the hidden behavior back is to pin to the version you were on before last night’s update:
npm install -g n8n@<previous-version>
Then start it again with n8n. Since this is a regression rather than a config, it’s worth logging it at Issues · n8n-io/n8n · GitHub so the hidden-window behavior gets restored in a release.
Thanks for sharing the update. It’s always helpful when someone explains whether an issue is a bug or just a configuration change after an update. I probably would have spent a lot of time checking my own setup first, so this clarification is useful. Hopefully the next release makes the behavior a bit clearer for everyone.
Hi Anshul, unfortunately downgrading to an older version is not a quick and easy solution.
I tested versions 2.29.X, none of them work because of the Node.js update. If you install 2.29.7 / .8, you would also have to downgrade node.js to a lower version, for example node.js 22.
So I’m sticking with version 2.29.8 (released yesterday) and waiting for 2.29.9 or higher.
Here’s a quick list, maybe it will help someone:
2.29.1 → Error: Command “start” not found → Cause: node.js 24
2.29.2 → Error: Command “start” not found → Cause: node.js 24
2.29.3 → Error: Command “start” not found → Cause: node.js 24
2.29.4 → Error: Command “start” not found → Cause: node.js 24
2.29.5 → Error: Command “start” not found → Cause: node.js 24
2.29.6 → Error: Command “start” not found → Cause: node.js 24
2.29.7 → works
2.29.8 → works
I have created NODE-5407 as the internal dev ticket to fix this, I think the older versions may also fail on older Node versions but luckily we have fixed that part already.