We have a batch script (.cmd) that prepares a few files and then executes a large system (.exe). When running with profile on in credentials, the .exe runs and stops loading at 68Mb of memory in use. If I turn off the profile, it runs perfectly and can at times use 12GB of memory.

The batch script runs perfectly on the console logged in with the same user.

What is preventing it running when I turn the profile on?

Hard to say if you do not get any specific errors. But why do you need to run it "With profile" if you say it runs perfectly?

---

First you need to find out if this is process or Windows installation specific. Try the same Credential and use full path to cmd.exe and see if that works or not.

---