07-23-2023, 10:41 AM
I'm having some trouble with a `.bat`->`.ps1` call in my build process after moving from Win7 to Win10 (1607 LTSB) - the call to PowerShell, that took less than 100msec on Win7 now takes 10sec+ on Win10 on certain hosts :-(
The call looks like this: `powershell -ExecutionPolicy Bypass -NonInteractive %scriptfile%`
Startup-performance of ISE and PowerShell.exe from start-menu is good.
I wasn't able to dig up anything helpful so far...
* PoSh 5.1 on both, Win7 and Win10, PSProfile is clean apart from a couple of aliases
* $env:PATH is "clean" apart from a couple of folders that have been added on purpose - removing those didn't improve the situation.
* already did "ngen update" - problem still occurs.
I've create a little helper script that measures startup-performance of PowerShell from different starting points: no luck with this either, on Win7 and most of my Win10 machines startup-time is way below 1sec.
anybody here who has already solved this riddle?
The call looks like this: `powershell -ExecutionPolicy Bypass -NonInteractive %scriptfile%`
Startup-performance of ISE and PowerShell.exe from start-menu is good.
I wasn't able to dig up anything helpful so far...
* PoSh 5.1 on both, Win7 and Win10, PSProfile is clean apart from a couple of aliases
* $env:PATH is "clean" apart from a couple of folders that have been added on purpose - removing those didn't improve the situation.
* already did "ngen update" - problem still occurs.
I've create a little helper script that measures startup-performance of PowerShell from different starting points: no luck with this either, on Win7 and most of my Win10 machines startup-time is way below 1sec.
anybody here who has already solved this riddle?