WMF 5.0 Production Preview -- Extreme console startup times on Windows 8.1/2012R2
when starting console first time, i.e. powershell.exe or powershell_ise.exe, after installing wmf 5.0 takes several minutes before can input commands. during time, console uses 100% cpu single logical processor
there few different behaviors, it's pretty same. either prompt never appears, commands queued , there no output console, or every command fails error "the number of waithandles must less or equal 64." it's not 10 seconds or thirty seconds either. on main development workstation, pretty new with ssd storage, can take 20-30 minutes before console usable. on fresh vm install nothing unconfigured os, 5 minutes has typically been minimum.
if log in same machine new user, behavior repeat again. behavior repeat on 32-bit version of console well. once console unblocked, starting console works expected, @ least until os update or other configuration resets behavior. windows updates re-triggers whatever happening in console. so, it's not reproducible, it's 1 time install background operation.
looking @ console exe doing procmon, appears looking powershell configuration files everwhere in psmodulepath , other system locations, not once. goes on each directory several times, resulting in literally millions of operations each console/user login.
slow console startup blocking sort of adoption of wmf 4 or 5 technologies us. blocking usage of the primary local management console while hammering resources amount of time on production server problematic least.
has else been able deal or know going on?
\_(ツ)_/
Windows Server > Windows PowerShell
Comments
Post a Comment