Sounds like the tunnel that is created automatically by the desktop app is being blocked by your IT department.
When you first start n8n, a hidden file is created that contains the tunnel information so inbound calls can go directly to your n8n desktop. It sounds like this first step is not happening and that is why the app is not deploying.
Your best bet maybe to run docker for windows and run it in docker, as you are able to set those proxy values manually in the setup, but it maybe more complicated than you want to deploy.
I wish I knew more about the desktop version, but I typically use the docker version so my knowledge on it is limited. Someone like @Jon may know better about this.
Ah I missed this one, So I suspect it could be the proxy blocking the tunnel creation. It could be worth checking with the IT team although I did think that we fixed an issue with Desktop where it wouldn’t start if it couldn’t create the tunnel.
Would you be able to open a command prompt window and run the app from there? You can do this by changing into the directory that contains the exe and just typing the name in.
That is a good question, I can’t see an option so it could be a hard coded option. I noticed you added a start in there if you drop that does it change anything? I am wondering if the issue isn’t with not using a proxy at all but more that the proxy is blocking the tunnel.
My two cents.
In this page : Desktop app - n8n Documentation, you could add a message on how to disable tunnel for environnements where it is not possible to create it.