specifically i’m working with the simplysql module on github. if i import it with 64-bit powershell or ISE, it takes 1-2 seconds. if i import it with 32-bit powershell or ISE, it takes 30 seconds. i ran into this because i have a piece of purchased software that’s running a 32-bit powershell environment, but then found i could reproduce the issue outside of the software. the software vendor can’t reproduce the issue, and neither can the person who created the simplysql module. i’ve reproduced with multiple user accounts and machines, but all members of the same domain. i can’t reproduce the issue on my windows 10 home machine, which is free from the group policies and other influences of my organization. so i’m admitting this is probably environmental. the software vendor’s support suggested it might be antivirus or certificate revocation list checking. but i don’t get why either of those (or anything else i can think of) would only affect 32-bit. and disabling antivirus has no effect.
the -verbose switch says that the entire import-module delay is happening before any of the functions/cmdlets are imported, so picking specific cmdlets doesn’t help.
any ideas where else i should look?