Not avoiding the problem, but curious about your use of SET. I can't think of a single script where I have ever used it. How/Why are you using those. Maybe we can suggest a better method.
I was thinking the same thing, Allen...
we use environment variables in our software (we are a software development company). These environment variables are needed for our legacy software to run correctly. So, while you might not use them, we do, and not using them should not be a reason why we notice a performance different from one OS to another on the same network/domain running the exact same script.
Dang auto correct. I can assure you "fun" was not the word written on this windows device.
Anywho. You can dig deeper by testing directly from the command line and from kix during and after logon process. If it has something to do with API kixtart calls, all of these will most likely give you different times.
If command line set takes forever too, then we are back to it is by design.
Windows command SetX is also very slow (6 seconds to run). I have done some digging on the web, to no avail for a solution.
