July 17, 2017 at 5:37 pm #75143
When opening either powershell or powershell ISE it take easily over a minute for either to be ready to use. I will also be very slow running commands. something as simple as Get-PSDrive takes at least a minute or more to run.
I am currently running Win 7 x64. PSshell version 5..0.10514.6
July 17, 2017 at 5:49 pm #75145
Check your $profile file. See if there's any functions trying to load at start up.
Also check $env:PSModulePath and see if you a network paths in there. That slows down PowerShell and intellisense a lot.
July 17, 2017 at 6:09 pm #75146
thank you for the response.
I checked my Profile file and there was nothing but a command to set dir to C:\. I just deleted it.
$env:PSModulePath returns C:\user\xxxxx\documents\WindowsPowershell\modules:C:\Windows\system32\windowspowershell\v1.0\modules
Power shell still running very slow.
Since I am running x64 bit should the path be windows\WOW64\Windowspowershell\v1.0\module ?
July 17, 2017 at 6:41 pm #75149
How many modules do you have installed?
July 17, 2017 at 7:00 pm #75152
get-module shows only 4 installed modules.
July 17, 2017 at 7:39 pm #75154
What about your .NET install? not sure but since PowerShell depends/uses the .NET framework maybe something is funky there.
July 17, 2017 at 7:39 pm #75157
Did you check all 4 profiles?
Current User, Current Host $Home\[My ]Documents\WindowsPowerShell\Profile.ps1
Current User, All Hosts $Home\[My ]Documents\Profile.ps1
All Users, Current Host $PsHome\Microsoft.PowerShell_profile.ps1
All Users, All Hosts $PsHome\Profile.ps1
July 17, 2017 at 8:01 pm #75158
What does Get-Module -ListAvailable show?
July 17, 2017 at 8:15 pm #75161
Ivan I am now running MS .net framework 4.6.2. Tried upgrading and it did not help.
Rob all modules are in C:\Windows\system32\windowspowershell\v1.0\modules
two are Manifest and one is Script
Will Get-Module -ListAvailable shows 2 modules in Directory: C:\Program Files\WindowsPowerShell\Modules
and 23 in Directory: C:\Windows\system32\WindowsPowerShell\v1.0\Modules
July 19, 2017 at 2:11 pm #75263
I was asking if you had looked at all the potential profile files. Not the modules.
August 2, 2017 at 5:03 am #76396
I had a similar issue. I used process monitor and determined it was because I was using PowerShell transcript logging and PowerShell wasn't able to reach the logging server. When I deactivated the logging, PowerShell returned to quick start up.
Removed a bit of output for clarity.
4:49:38.5598938 PM powershell.exe 10552 CreateFile C:\Windows\CSC\v2.0.6\namespace\SERVER NAME NOT FOUND 4:49:59.2770204 PM powershell.exe 10552 CreateFile C:\Windows\CSC\v2.0.6\namespace\SERVER NAME NOT FOUND 4:49:59.2770849 PM powershell.exe 10552 CreateFile \\SERVER\powershelllogging$\20170801\PowerShell_transcript.Computer.3Rk9SPVM.20170801164854.txt IO TIMEOUT 4:50:40.7241605 PM powershell.exe 10552 CreateFile C:\Windows\CSC\v2.0.6\namespace\SERVER NAME NOT FOUND 4:50:56.1804549 PM powershell.exe 10552 Thread Exit SUCCESS Thread ID: 8248, User Time: 0.0000000, Kernel Time: 0.0000000 4:51:22.1649146 PM powershell.exe 10552 CreateFile C:\Windows\CSC\v2.0.6\namespace\SERVER NAME NOT FOUND 4:51:22.1649745 PM powershell.exe 10552 CreateFile \\SERVER\powershelllogging$\20170801\ IO TIMEOUT 4:52:03.5742313 PM powershell.exe 10552 CreateFile C:\Windows\CSC\v2.0.6\namespace\SERVER NAME NOT FOUND
Can see if logging via
August 20, 2017 at 11:08 am #77689
I have the same issue.Hope I can solve it.
You must be logged in to reply to this topic.