PowerShell 64-bit hanging on new machineUsing Workflows In PowershellInvoke-WebRequest alterative in...
Critique vs nitpicking
Why is it that Bernie Sanders is always called a "socialist"?
Why do all the books in Game of Thrones library have their covers facing the back of the shelf?
Does Skippy chunky peanut butter contain trans fat?
How vim overwrites readonly mode?
Not a Long-Winded Riddle
What is the wife of a henpecked husband called?
Plausible reason to leave the Solar System?
What is the industry term for house wiring diagrams?
Why is the "Domain users" group missing from this Powershell AD Query?
A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?
Why does 0.-5 evaluate to -5?
How do I prevent a homebrew Grappling Hook feature from trivializing Tomb of Annihilation?
Why didn't the 2019 Oscars have a host?
Equivalent of "illegal" for violating civil law
The No-Straight Maze
Does the ditching switch allow an A320 to float indefinitely?
Article. The word "Respect"
In harmony: key or the flow?
Custom shape shows unwanted extra line
Calculate of total length of edges in Voronoi diagram
How big is a framed opening for a door relative to the finished door opening width?
Plausible reason for gold-digging ant
Crack the bank account's password!
PowerShell 64-bit hanging on new machine
Using Workflows In PowershellInvoke-WebRequest alterative in PowerShell v5PowerShell change console tab sizeUpdate Powershell through command lineSetting window size and position in PowerShell 5 and 6Powershell ISE: Closing a PowerShell Tab does not unlock a dynamically loaded .NET assemblyPowerShell is missing Import-CertificatePowershell Core on linux through Proxy connection issuesEditing an RDP session with Notepad and PowershellPowershell Display Error
I recently got a new computer with plenty of horsepower and its works very fast everywhere except PowerShell.
Environment:
- Dell XPS 8930 (i7-8700K, 32GB RAM, 1TB NVMe SSD)
- Windows 10 Pro with latest updates (1809/10.0.17763)
- PowerShell 5.1.17763.316 and PowerShell Core 6.1.1
- I have plenty of memory left (>16GB) and CPU is near idle while it's hanging.
- Only Windows Defender (no other antivirus)
Some of the symptoms, which seem to be consistent:
- Opening PowerShell shows the copyright info and hangs there for 2 minutes before showing the prompt.
- I start typing a command and it takes almost a minute for the text to appear
- Once the text appears I can modify the command and it's responsive.
- I enter a simple command such as
echo 'hello'and hit enter, it takes about 45 seconds for 'hello' to appear on the screen and another 45 seconds to return to the prompt. - Once at the prompt typing a command is responsive, but the running it is slow again.
- Run the
dircommand in my home directory (few files/folders): about 2:30 before listing the directory, another 15 seconds to go back to the prompt.
Some attempted troubleshooting:
- PowerShell ISE: Takes about 5 minutes to get to prompt.
- PowerShell ISE (x86): It works fast!
- PowerShell (x86): Also works fast!
- PowerShell Core: Also very slow.
- PowerShell legacy console: No change.
- Opening up a regular command line and running
powershell -NoProfile: No change.
sfc /scannow: No problems found, rebooting doesn't help.- Disable network connections: No change.
- Run Sysinternals procmon: Nothing obvious, but it always seems to hang right after some of the "Thread Exit" operations.
- Look at thread stacks in Sysinternals procexp: When it's hanging the main thread is always at ntdll.dll
ZwWaitForMultipleObjects. - Uninstall WSL/Hyper-V: No change.
- Ran "Microsoft .NET Framework Repair Tool" and rebooted, no change.
- Check
C:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadline, only one 4KB file.
$PSModuleAutoloadingPreference = 'none': no change. I wouldn't imagine running one of the basic commands such asechomultiple times would always try to load modules.
netsh http show iplist:
IP addresses present in the IP listen list:
127.0.0.1
- Enable WinRM (
winrm quickconfig): The service starts, but then it can't connect.
- I can see port 5985 is being listened to by PID 4 when the service is started.
- The Windows Firewall has the two "Windows Remote Management (HTTP-In)" entries for port 5985 (allow any remote address when in a private network/profile).
- I can successfully
telnet localhost 5985
- After the WinRM service starts it takes about 7 minutes for it to respond with:
WSManFault
...
Error number: -2144108250 0x80338126
WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the
network, and that a firewall exception for the WinRM service is
enabled and allows access from this computer. By default, the WinRM
firewall exception for public profiles limits access to remote
computers within the same local subnet.
The consistency in the delays makes me think there is some type of attempted connection and timeout, but I'm at a loss as to what that may be. Any gurus out there with ideas?
windows-10-v1809 powershell-5.0 powershell-6.1
asked Nov 21 '18 at 4:48
Nelson RothermelNelson Rothermel
94
This question has an open bounty worth +100
reputation from Nelson Rothermel ending in 2 days.
This question has not received enough attention.
I want my PowerShell to be fast again!
|
show 5 more comments
I recently got a new computer with plenty of horsepower and its works very fast everywhere except PowerShell.
Environment:
- Dell XPS 8930 (i7-8700K, 32GB RAM, 1TB NVMe SSD)
- Windows 10 Pro with latest updates (1809/10.0.17763)
- PowerShell 5.1.17763.316 and PowerShell Core 6.1.1
- I have plenty of memory left (>16GB) and CPU is near idle while it's hanging.
- Only Windows Defender (no other antivirus)
Some of the symptoms, which seem to be consistent:
- Opening PowerShell shows the copyright info and hangs there for 2 minutes before showing the prompt.
- I start typing a command and it takes almost a minute for the text to appear
- Once the text appears I can modify the command and it's responsive.
- I enter a simple command such as
echo 'hello'and hit enter, it takes about 45 seconds for 'hello' to appear on the screen and another 45 seconds to return to the prompt. - Once at the prompt typing a command is responsive, but the running it is slow again.
- Run the
dircommand in my home directory (few files/folders): about 2:30 before listing the directory, another 15 seconds to go back to the prompt.
Some attempted troubleshooting:
- PowerShell ISE: Takes about 5 minutes to get to prompt.
- PowerShell ISE (x86): It works fast!
- PowerShell (x86): Also works fast!
- PowerShell Core: Also very slow.
- PowerShell legacy console: No change.
- Opening up a regular command line and running
powershell -NoProfile: No change.
sfc /scannow: No problems found, rebooting doesn't help.- Disable network connections: No change.
- Run Sysinternals procmon: Nothing obvious, but it always seems to hang right after some of the "Thread Exit" operations.
- Look at thread stacks in Sysinternals procexp: When it's hanging the main thread is always at ntdll.dll
ZwWaitForMultipleObjects. - Uninstall WSL/Hyper-V: No change.
- Ran "Microsoft .NET Framework Repair Tool" and rebooted, no change.
- Check
C:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadline, only one 4KB file.
$PSModuleAutoloadingPreference = 'none': no change. I wouldn't imagine running one of the basic commands such asechomultiple times would always try to load modules.
netsh http show iplist:
IP addresses present in the IP listen list:
127.0.0.1
- Enable WinRM (
winrm quickconfig): The service starts, but then it can't connect.
- I can see port 5985 is being listened to by PID 4 when the service is started.
- The Windows Firewall has the two "Windows Remote Management (HTTP-In)" entries for port 5985 (allow any remote address when in a private network/profile).
- I can successfully
telnet localhost 5985
- After the WinRM service starts it takes about 7 minutes for it to respond with:
WSManFault
...
Error number: -2144108250 0x80338126
WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the
network, and that a firewall exception for the WinRM service is
enabled and allows access from this computer. By default, the WinRM
firewall exception for public profiles limits access to remote
computers within the same local subnet.
The consistency in the delays makes me think there is some type of attempted connection and timeout, but I'm at a loss as to what that may be. Any gurus out there with ideas?
windows-10-v1809 powershell-5.0 powershell-6.1
asked Nov 21 '18 at 4:48
Nelson RothermelNelson Rothermel
94
This question has an open bounty worth +100
reputation from Nelson Rothermel ending in 2 days.
This question has not received enough attention.
I want my PowerShell to be fast again!
One other thing I've noticed which may or may not be related: when I download a file in Chrome, it will reach 100% and then sit there for almost exactly 30 seconds before I can open/show in folder.
– Nelson Rothermel
Feb 21 at 3:37
What version of PowerShell do you have installed, PowerShell 5.1 is installed by default on Windows 10, but you might have PowerShell Core installed. Do you still have the same security product installed, if so edit your question, and include the vital information necessary to answer your question. Please provide the relevant information from, netsh http show iplist, which will verify a theory of mine.
– Ramhound
Feb 21 at 3:41
Try: (1) See if you have an enormous file inC:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadlineand get rid of it. (2) Create a shortcut to%SystemRoot%system32WindowsPowerShellv1.0powershell.exeand in Properties > Options set Use legacy console, (3) Try to call PowerShell with the-NoProfileswitch, (4) Turn Off PowerShell Module Autoload.
– harrymc
Feb 21 at 12:54
@NelsonRothermel Additionally, I would try ....1.from admin elevated command prompt runsfc /scannowlet it complete, reboot, try again.2.Still having problems, try running the microsoft.com/en-us/download/details.aspx?id=30135 tool just in case, run it, reboot, try again.
– Pimp Juice IT
Feb 21 at 17:31
@harrymc: Yep, got busy with other things but just added more details. Only 4KB file in that path, I already tried legacy console and-NoProfile, disabling module autoload didn't help. @Ramhound: I no longer have Bitdefender, both PowerShell Core and regular are slow. I've included thenetshoutput in my question. @PimpJuice: Already triedsfc, the .NET repair tool didn't help.
– Nelson Rothermel
2 days ago
|
show 5 more comments
I recently got a new computer with plenty of horsepower and its works very fast everywhere except PowerShell.
Environment:
- Dell XPS 8930 (i7-8700K, 32GB RAM, 1TB NVMe SSD)
- Windows 10 Pro with latest updates (1809/10.0.17763)
- PowerShell 5.1.17763.316 and PowerShell Core 6.1.1
- I have plenty of memory left (>16GB) and CPU is near idle while it's hanging.
- Only Windows Defender (no other antivirus)
Some of the symptoms, which seem to be consistent:
- Opening PowerShell shows the copyright info and hangs there for 2 minutes before showing the prompt.
- I start typing a command and it takes almost a minute for the text to appear
- Once the text appears I can modify the command and it's responsive.
- I enter a simple command such as
echo 'hello'and hit enter, it takes about 45 seconds for 'hello' to appear on the screen and another 45 seconds to return to the prompt. - Once at the prompt typing a command is responsive, but the running it is slow again.
- Run the
dircommand in my home directory (few files/folders): about 2:30 before listing the directory, another 15 seconds to go back to the prompt.
Some attempted troubleshooting:
- PowerShell ISE: Takes about 5 minutes to get to prompt.
- PowerShell ISE (x86): It works fast!
- PowerShell (x86): Also works fast!
- PowerShell Core: Also very slow.
- PowerShell legacy console: No change.
- Opening up a regular command line and running
powershell -NoProfile: No change.
sfc /scannow: No problems found, rebooting doesn't help.- Disable network connections: No change.
- Run Sysinternals procmon: Nothing obvious, but it always seems to hang right after some of the "Thread Exit" operations.
- Look at thread stacks in Sysinternals procexp: When it's hanging the main thread is always at ntdll.dll
ZwWaitForMultipleObjects. - Uninstall WSL/Hyper-V: No change.
- Ran "Microsoft .NET Framework Repair Tool" and rebooted, no change.
- Check
C:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadline, only one 4KB file.
$PSModuleAutoloadingPreference = 'none': no change. I wouldn't imagine running one of the basic commands such asechomultiple times would always try to load modules.
netsh http show iplist:
IP addresses present in the IP listen list:
127.0.0.1
- Enable WinRM (
winrm quickconfig): The service starts, but then it can't connect.
- I can see port 5985 is being listened to by PID 4 when the service is started.
- The Windows Firewall has the two "Windows Remote Management (HTTP-In)" entries for port 5985 (allow any remote address when in a private network/profile).
- I can successfully
telnet localhost 5985
- After the WinRM service starts it takes about 7 minutes for it to respond with:
WSManFault
...
Error number: -2144108250 0x80338126
WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the
network, and that a firewall exception for the WinRM service is
enabled and allows access from this computer. By default, the WinRM
firewall exception for public profiles limits access to remote
computers within the same local subnet.
The consistency in the delays makes me think there is some type of attempted connection and timeout, but I'm at a loss as to what that may be. Any gurus out there with ideas?
windows-10-v1809 powershell-5.0 powershell-6.1
asked Nov 21 '18 at 4:48
Nelson RothermelNelson Rothermel
94
I recently got a new computer with plenty of horsepower and its works very fast everywhere except PowerShell.
Environment:
- Dell XPS 8930 (i7-8700K, 32GB RAM, 1TB NVMe SSD)
- Windows 10 Pro with latest updates (1809/10.0.17763)
- PowerShell 5.1.17763.316 and PowerShell Core 6.1.1
- I have plenty of memory left (>16GB) and CPU is near idle while it's hanging.
- Only Windows Defender (no other antivirus)
Some of the symptoms, which seem to be consistent:
- Opening PowerShell shows the copyright info and hangs there for 2 minutes before showing the prompt.
- I start typing a command and it takes almost a minute for the text to appear
- Once the text appears I can modify the command and it's responsive.
- I enter a simple command such as
echo 'hello'and hit enter, it takes about 45 seconds for 'hello' to appear on the screen and another 45 seconds to return to the prompt. - Once at the prompt typing a command is responsive, but the running it is slow again.
- Run the
dircommand in my home directory (few files/folders): about 2:30 before listing the directory, another 15 seconds to go back to the prompt.
Some attempted troubleshooting:
- PowerShell ISE: Takes about 5 minutes to get to prompt.
- PowerShell ISE (x86): It works fast!
- PowerShell (x86): Also works fast!
- PowerShell Core: Also very slow.
- PowerShell legacy console: No change.
- Opening up a regular command line and running
powershell -NoProfile: No change.
sfc /scannow: No problems found, rebooting doesn't help.- Disable network connections: No change.
- Run Sysinternals procmon: Nothing obvious, but it always seems to hang right after some of the "Thread Exit" operations.
- Look at thread stacks in Sysinternals procexp: When it's hanging the main thread is always at ntdll.dll
ZwWaitForMultipleObjects. - Uninstall WSL/Hyper-V: No change.
- Ran "Microsoft .NET Framework Repair Tool" and rebooted, no change.
- Check
C:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadline, only one 4KB file.
$PSModuleAutoloadingPreference = 'none': no change. I wouldn't imagine running one of the basic commands such asechomultiple times would always try to load modules.
netsh http show iplist:
IP addresses present in the IP listen list:
127.0.0.1
- Enable WinRM (
winrm quickconfig): The service starts, but then it can't connect.
- I can see port 5985 is being listened to by PID 4 when the service is started.
- The Windows Firewall has the two "Windows Remote Management (HTTP-In)" entries for port 5985 (allow any remote address when in a private network/profile).
- I can successfully
telnet localhost 5985
- After the WinRM service starts it takes about 7 minutes for it to respond with:
WSManFault
...
Error number: -2144108250 0x80338126
WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the
network, and that a firewall exception for the WinRM service is
enabled and allows access from this computer. By default, the WinRM
firewall exception for public profiles limits access to remote
computers within the same local subnet.
The consistency in the delays makes me think there is some type of attempted connection and timeout, but I'm at a loss as to what that may be. Any gurus out there with ideas?
windows-10-v1809 powershell-5.0 powershell-6.1
windows-10-v1809 powershell-5.0 powershell-6.1
asked Nov 21 '18 at 4:48
Nelson RothermelNelson Rothermel
94
asked Nov 21 '18 at 4:48
Nelson RothermelNelson Rothermel
94
edited 2 days ago
Nelson Rothermel
asked Nov 21 '18 at 4:48
Nelson RothermelNelson Rothermel
94
asked Nov 21 '18 at 4:48
Nelson RothermelNelson Rothermel
94
asked Nov 21 '18 at 4:48
Nelson RothermelNelson Rothermel
94
94
This question has an open bounty worth +100
reputation from Nelson Rothermel ending in 2 days.
This question has not received enough attention.
I want my PowerShell to be fast again!
This question has an open bounty worth +100
reputation from Nelson Rothermel ending in 2 days.
This question has not received enough attention.
I want my PowerShell to be fast again!
One other thing I've noticed which may or may not be related: when I download a file in Chrome, it will reach 100% and then sit there for almost exactly 30 seconds before I can open/show in folder.
– Nelson Rothermel
Feb 21 at 3:37
What version of PowerShell do you have installed, PowerShell 5.1 is installed by default on Windows 10, but you might have PowerShell Core installed. Do you still have the same security product installed, if so edit your question, and include the vital information necessary to answer your question. Please provide the relevant information from, netsh http show iplist, which will verify a theory of mine.
– Ramhound
Feb 21 at 3:41
Try: (1) See if you have an enormous file inC:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadlineand get rid of it. (2) Create a shortcut to%SystemRoot%system32WindowsPowerShellv1.0powershell.exeand in Properties > Options set Use legacy console, (3) Try to call PowerShell with the-NoProfileswitch, (4) Turn Off PowerShell Module Autoload.
– harrymc
Feb 21 at 12:54
@NelsonRothermel Additionally, I would try ....1.from admin elevated command prompt runsfc /scannowlet it complete, reboot, try again.2.Still having problems, try running the microsoft.com/en-us/download/details.aspx?id=30135 tool just in case, run it, reboot, try again.
– Pimp Juice IT
Feb 21 at 17:31
@harrymc: Yep, got busy with other things but just added more details. Only 4KB file in that path, I already tried legacy console and-NoProfile, disabling module autoload didn't help. @Ramhound: I no longer have Bitdefender, both PowerShell Core and regular are slow. I've included thenetshoutput in my question. @PimpJuice: Already triedsfc, the .NET repair tool didn't help.
– Nelson Rothermel
2 days ago
|
show 5 more comments
One other thing I've noticed which may or may not be related: when I download a file in Chrome, it will reach 100% and then sit there for almost exactly 30 seconds before I can open/show in folder.
– Nelson Rothermel
Feb 21 at 3:37
What version of PowerShell do you have installed, PowerShell 5.1 is installed by default on Windows 10, but you might have PowerShell Core installed. Do you still have the same security product installed, if so edit your question, and include the vital information necessary to answer your question. Please provide the relevant information from, netsh http show iplist, which will verify a theory of mine.
– Ramhound
Feb 21 at 3:41
Try: (1) See if you have an enormous file inC:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadlineand get rid of it. (2) Create a shortcut to%SystemRoot%system32WindowsPowerShellv1.0powershell.exeand in Properties > Options set Use legacy console, (3) Try to call PowerShell with the-NoProfileswitch, (4) Turn Off PowerShell Module Autoload.
– harrymc
Feb 21 at 12:54
@NelsonRothermel Additionally, I would try ....1.from admin elevated command prompt runsfc /scannowlet it complete, reboot, try again.2.Still having problems, try running the microsoft.com/en-us/download/details.aspx?id=30135 tool just in case, run it, reboot, try again.
– Pimp Juice IT
Feb 21 at 17:31
@harrymc: Yep, got busy with other things but just added more details. Only 4KB file in that path, I already tried legacy console and-NoProfile, disabling module autoload didn't help. @Ramhound: I no longer have Bitdefender, both PowerShell Core and regular are slow. I've included thenetshoutput in my question. @PimpJuice: Already triedsfc, the .NET repair tool didn't help.
– Nelson Rothermel
2 days ago
One other thing I've noticed which may or may not be related: when I download a file in Chrome, it will reach 100% and then sit there for almost exactly 30 seconds before I can open/show in folder.
– Nelson Rothermel
Feb 21 at 3:37
One other thing I've noticed which may or may not be related: when I download a file in Chrome, it will reach 100% and then sit there for almost exactly 30 seconds before I can open/show in folder.
– Nelson Rothermel
Feb 21 at 3:37
What version of PowerShell do you have installed, PowerShell 5.1 is installed by default on Windows 10, but you might have PowerShell Core installed. Do you still have the same security product installed, if so edit your question, and include the vital information necessary to answer your question. Please provide the relevant information from, netsh http show iplist, which will verify a theory of mine.
– Ramhound
Feb 21 at 3:41
What version of PowerShell do you have installed, PowerShell 5.1 is installed by default on Windows 10, but you might have PowerShell Core installed. Do you still have the same security product installed, if so edit your question, and include the vital information necessary to answer your question. Please provide the relevant information from, netsh http show iplist, which will verify a theory of mine.
– Ramhound
Feb 21 at 3:41
Try: (1) See if you have an enormous file in
C:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadline and get rid of it. (2) Create a shortcut to %SystemRoot%system32WindowsPowerShellv1.0powershell.exe and in Properties > Options set Use legacy console, (3) Try to call PowerShell with the -NoProfile switch, (4) Turn Off PowerShell Module Autoload.– harrymc
Feb 21 at 12:54
Try: (1) See if you have an enormous file in
C:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadline and get rid of it. (2) Create a shortcut to %SystemRoot%system32WindowsPowerShellv1.0powershell.exe and in Properties > Options set Use legacy console, (3) Try to call PowerShell with the -NoProfile switch, (4) Turn Off PowerShell Module Autoload.– harrymc
Feb 21 at 12:54
@NelsonRothermel Additionally, I would try ....
1. from admin elevated command prompt run sfc /scannow let it complete, reboot, try again. 2. Still having problems, try running the microsoft.com/en-us/download/details.aspx?id=30135 tool just in case, run it, reboot, try again.– Pimp Juice IT
Feb 21 at 17:31
@NelsonRothermel Additionally, I would try ....
1. from admin elevated command prompt run sfc /scannow let it complete, reboot, try again. 2. Still having problems, try running the microsoft.com/en-us/download/details.aspx?id=30135 tool just in case, run it, reboot, try again.– Pimp Juice IT
Feb 21 at 17:31
@harrymc: Yep, got busy with other things but just added more details. Only 4KB file in that path, I already tried legacy console and
-NoProfile, disabling module autoload didn't help. @Ramhound: I no longer have Bitdefender, both PowerShell Core and regular are slow. I've included the netsh output in my question. @PimpJuice: Already tried sfc, the .NET repair tool didn't help.– Nelson Rothermel
2 days ago
@harrymc: Yep, got busy with other things but just added more details. Only 4KB file in that path, I already tried legacy console and
-NoProfile, disabling module autoload didn't help. @Ramhound: I no longer have Bitdefender, both PowerShell Core and regular are slow. I've included the netsh output in my question. @PimpJuice: Already tried sfc, the .NET repair tool didn't help.– Nelson Rothermel
2 days ago
|
show 5 more comments
2 Answers
2
active
oldest
votes
Thanks to the antivirus comment at https://stackoverflow.com/questions/45021585/powershell-hangs-on-launch! I had Bitdefender Antivirus installed. Disabling it didn't fix the problem, but uninstalling did. I tried reinstalling and the problem reappeared. Adding all of C: to the exclusion list did not fix the issue.
2/20 update: I still have Bitdefender Antivirus uninstalled but the problem reappeared some weeks ago.
answered Nov 22 '18 at 0:55
Nelson RothermelNelson Rothermel
94
add a comment |
Try blocking network access at the firewall. This will rule out PowerShell waiting on external resources.
If you block all network connections for Powershell, it should look like this
EXAMPLE RULES:
Powershell All Yes Block No %SystemRoot%SysWOW64WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
Powershell2 All Yes Block No %SystemRoot%system32WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
answered 6 hours ago
HackSlashHackSlash
2,2621722
Thanks for the suggestion, but unfortunately it didn't make a difference. I had already tried disconnecting from all networks which I assumed would work in a similar way and any network requests would immediately fail.
– Nelson Rothermel
5 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377171%2fpowershell-64-bit-hanging-on-new-machine%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks to the antivirus comment at https://stackoverflow.com/questions/45021585/powershell-hangs-on-launch! I had Bitdefender Antivirus installed. Disabling it didn't fix the problem, but uninstalling did. I tried reinstalling and the problem reappeared. Adding all of C: to the exclusion list did not fix the issue.
2/20 update: I still have Bitdefender Antivirus uninstalled but the problem reappeared some weeks ago.
answered Nov 22 '18 at 0:55
Nelson RothermelNelson Rothermel
94
add a comment |
Thanks to the antivirus comment at https://stackoverflow.com/questions/45021585/powershell-hangs-on-launch! I had Bitdefender Antivirus installed. Disabling it didn't fix the problem, but uninstalling did. I tried reinstalling and the problem reappeared. Adding all of C: to the exclusion list did not fix the issue.
2/20 update: I still have Bitdefender Antivirus uninstalled but the problem reappeared some weeks ago.
answered Nov 22 '18 at 0:55
Nelson RothermelNelson Rothermel
94
add a comment |
Thanks to the antivirus comment at https://stackoverflow.com/questions/45021585/powershell-hangs-on-launch! I had Bitdefender Antivirus installed. Disabling it didn't fix the problem, but uninstalling did. I tried reinstalling and the problem reappeared. Adding all of C: to the exclusion list did not fix the issue.
2/20 update: I still have Bitdefender Antivirus uninstalled but the problem reappeared some weeks ago.
answered Nov 22 '18 at 0:55
Nelson RothermelNelson Rothermel
94
Thanks to the antivirus comment at https://stackoverflow.com/questions/45021585/powershell-hangs-on-launch! I had Bitdefender Antivirus installed. Disabling it didn't fix the problem, but uninstalling did. I tried reinstalling and the problem reappeared. Adding all of C: to the exclusion list did not fix the issue.
2/20 update: I still have Bitdefender Antivirus uninstalled but the problem reappeared some weeks ago.
answered Nov 22 '18 at 0:55
Nelson RothermelNelson Rothermel
94
edited Feb 21 at 3:34
answered Nov 22 '18 at 0:55
Nelson RothermelNelson Rothermel
94
answered Nov 22 '18 at 0:55
Nelson RothermelNelson Rothermel
94
answered Nov 22 '18 at 0:55
Nelson RothermelNelson Rothermel
94
94
add a comment |
add a comment |
Try blocking network access at the firewall. This will rule out PowerShell waiting on external resources.
If you block all network connections for Powershell, it should look like this
EXAMPLE RULES:
Powershell All Yes Block No %SystemRoot%SysWOW64WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
Powershell2 All Yes Block No %SystemRoot%system32WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
answered 6 hours ago
HackSlashHackSlash
2,2621722
Thanks for the suggestion, but unfortunately it didn't make a difference. I had already tried disconnecting from all networks which I assumed would work in a similar way and any network requests would immediately fail.
– Nelson Rothermel
5 hours ago
add a comment |
Try blocking network access at the firewall. This will rule out PowerShell waiting on external resources.
If you block all network connections for Powershell, it should look like this
EXAMPLE RULES:
Powershell All Yes Block No %SystemRoot%SysWOW64WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
Powershell2 All Yes Block No %SystemRoot%system32WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
answered 6 hours ago
HackSlashHackSlash
2,2621722
Thanks for the suggestion, but unfortunately it didn't make a difference. I had already tried disconnecting from all networks which I assumed would work in a similar way and any network requests would immediately fail.
– Nelson Rothermel
5 hours ago
add a comment |
Try blocking network access at the firewall. This will rule out PowerShell waiting on external resources.
If you block all network connections for Powershell, it should look like this
EXAMPLE RULES:
Powershell All Yes Block No %SystemRoot%SysWOW64WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
Powershell2 All Yes Block No %SystemRoot%system32WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
answered 6 hours ago
HackSlashHackSlash
2,2621722
Try blocking network access at the firewall. This will rule out PowerShell waiting on external resources.
If you block all network connections for Powershell, it should look like this
EXAMPLE RULES:
Powershell All Yes Block No %SystemRoot%SysWOW64WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
Powershell2 All Yes Block No %SystemRoot%system32WindowsPowerShellv1.0powershell.exe Any Any Any Any Any Any Any Any Any
answered 6 hours ago
HackSlashHackSlash
2,2621722
answered 6 hours ago
HackSlashHackSlash
2,2621722
answered 6 hours ago
HackSlashHackSlash
2,2621722
answered 6 hours ago
HackSlashHackSlash
2,2621722
2,2621722
Thanks for the suggestion, but unfortunately it didn't make a difference. I had already tried disconnecting from all networks which I assumed would work in a similar way and any network requests would immediately fail.
– Nelson Rothermel
5 hours ago
add a comment |
Thanks for the suggestion, but unfortunately it didn't make a difference. I had already tried disconnecting from all networks which I assumed would work in a similar way and any network requests would immediately fail.
– Nelson Rothermel
5 hours ago
Thanks for the suggestion, but unfortunately it didn't make a difference. I had already tried disconnecting from all networks which I assumed would work in a similar way and any network requests would immediately fail.
– Nelson Rothermel
5 hours ago
Thanks for the suggestion, but unfortunately it didn't make a difference. I had already tried disconnecting from all networks which I assumed would work in a similar way and any network requests would immediately fail.
– Nelson Rothermel
5 hours ago
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377171%2fpowershell-64-bit-hanging-on-new-machine%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
One other thing I've noticed which may or may not be related: when I download a file in Chrome, it will reach 100% and then sit there for almost exactly 30 seconds before I can open/show in folder.
– Nelson Rothermel
Feb 21 at 3:37
What version of PowerShell do you have installed, PowerShell 5.1 is installed by default on Windows 10, but you might have PowerShell Core installed. Do you still have the same security product installed, if so edit your question, and include the vital information necessary to answer your question. Please provide the relevant information from, netsh http show iplist, which will verify a theory of mine.
– Ramhound
Feb 21 at 3:41
Try: (1) See if you have an enormous file in
C:UsersUSERNAMEAppDataRoamingMicrosoftWindowsPowerShellPSReadlineand get rid of it. (2) Create a shortcut to%SystemRoot%system32WindowsPowerShellv1.0powershell.exeand in Properties > Options set Use legacy console, (3) Try to call PowerShell with the-NoProfileswitch, (4) Turn Off PowerShell Module Autoload.– harrymc
Feb 21 at 12:54
@NelsonRothermel Additionally, I would try ....
1.from admin elevated command prompt runsfc /scannowlet it complete, reboot, try again.2.Still having problems, try running the microsoft.com/en-us/download/details.aspx?id=30135 tool just in case, run it, reboot, try again.– Pimp Juice IT
Feb 21 at 17:31
@harrymc: Yep, got busy with other things but just added more details. Only 4KB file in that path, I already tried legacy console and
-NoProfile, disabling module autoload didn't help. @Ramhound: I no longer have Bitdefender, both PowerShell Core and regular are slow. I've included thenetshoutput in my question. @PimpJuice: Already triedsfc, the .NET repair tool didn't help.– Nelson Rothermel
2 days ago