Okay, got it working by forcing a working directory of null like so:
This works as expected against a Windows host:
So as suspected initially, this would appear to be caused by the specific network you are operating in, perhaps something specific to the Synology NAS (I don’t have such a device available, so won’t be able to test this myself unfortunately).
Perhaps you can narrow down the cause by running n8n outside of your Synology NAS (using something like docker run -it --rm -p 5678:5678 --name n8n n8nio/n8n:0.190.0 should fire up a temporary docker container allowing you to test this).