Powershell error: The type initializer for 'System.Net.ServicePointManager' threw an exception
1
Whenever I try to open Powershell, it just won't open. When I try to open it from the cmd, I get this error:
The shell cannot be started. A failure occurred during initialization:
The type initializer for 'System.Net.ServicePointManager' threw an exception.
Things I have tried:
- opening with administrator
- sfc /scannow which showed no errors
The 32 bit version of powershell still works for some reason if that helps in any way.
windows windows-10 powershell
asked Jan 30 at 1:48
gommbgommb
1114
|
show 7 more comments
1
Whenever I try to open Powershell, it just won't open. When I try to open it from the cmd, I get this error:
The shell cannot be started. A failure occurred during initialization:
The type initializer for 'System.Net.ServicePointManager' threw an exception.
Things I have tried:
- opening with administrator
- sfc /scannow which showed no errors
The 32 bit version of powershell still works for some reason if that helps in any way.
windows windows-10 powershell
asked Jan 30 at 1:48
gommbgommb
1114
1
Open command prompt as administrator and runDISM.exe / Online / Cleanup-image / Scanhealth, let that complete and then from the admin elevated command prompt type inDISM.exe / Online / Cleanup-image / Restorehealthand let that complete and once it does, restart the PC. After the restart, log back in and try running PowerShell again and see what happens. Some of this is here too social.technet.microsoft.com/Forums/lync/en-US/…
– Pimp Juice IT
Jan 31 at 2:29
1
Okay then the next thing to try is to sign onto the PC with another account (or create a new account and then sign on with it) and then try running PowerShell running under that account and see if it does not have the problem. If not, then the Windows user account profile is corrupt and you should rebuild a new one for the existing account.
– Pimp Juice IT
Jan 31 at 15:48
1
You might also check and confirm that all Windows Updates are applied as well and if not consider getting those fully updated to the latest and greatest, reboot, and try again. Lastly, poke thru the Event Viewer system and application logs and see if you notice any errors or warning which correlate to the problem or that you think even might be relevant. All you can do is be extra thorough and a process of elimination short of reinstalling Windows. I dig around the Internet a little more on this issue to see if anything else sticks out to me though.
– Pimp Juice IT
Jan 31 at 15:51
1
Okay, check out this post and read over the comments on the answer as well in case those things help any stackoverflow.com/questions/24875408/… it would be worth at least eliminating some of this as the issue if you want. I assume you already confirming running PowerShell as administrator is not the solution but wanted to mention that as well. Be sure to check thePATHenvironmental variable and the reg path listed in that comment and see what you have there on your side. Perhaps event viewer will show the full exception error message you can disclose.
– Pimp Juice IT
Jan 31 at 16:07
1
What antivirus software package(s) do you have installed on this machine, perhaps there is a security package that is blocking Windows core processes you need to add an exception to? Have you already run throughchdskbut if not, run thruCHKDSK C: /F /R /Xand let that complete, reboot, try again. Have you already done up-to-date virus and malware definition antivirus and antimalware scans including any that performs then offline? These are just other things I can think of which I did not mention, food for thought if nothing else!! Full RAM/memory scan/check too if you can wouldn't hurt,
– Pimp Juice IT
Feb 1 at 21:30
|
show 7 more comments
1
1
1
Whenever I try to open Powershell, it just won't open. When I try to open it from the cmd, I get this error:
The shell cannot be started. A failure occurred during initialization:
The type initializer for 'System.Net.ServicePointManager' threw an exception.
Things I have tried:
- opening with administrator
- sfc /scannow which showed no errors
The 32 bit version of powershell still works for some reason if that helps in any way.
windows windows-10 powershell
asked Jan 30 at 1:48
gommbgommb
1114
Whenever I try to open Powershell, it just won't open. When I try to open it from the cmd, I get this error:
The shell cannot be started. A failure occurred during initialization:
The type initializer for 'System.Net.ServicePointManager' threw an exception.
Things I have tried:
- opening with administrator
- sfc /scannow which showed no errors
The 32 bit version of powershell still works for some reason if that helps in any way.
windows windows-10 powershell
windows windows-10 powershell
asked Jan 30 at 1:48
gommbgommb
1114
asked Jan 30 at 1:48
gommbgommb
1114
edited Jan 31 at 0:30
gommb
asked Jan 30 at 1:48
gommbgommb
1114
asked Jan 30 at 1:48
gommbgommb
1114
asked Jan 30 at 1:48
gommbgommb
1114
1114
1
Open command prompt as administrator and runDISM.exe / Online / Cleanup-image / Scanhealth, let that complete and then from the admin elevated command prompt type inDISM.exe / Online / Cleanup-image / Restorehealthand let that complete and once it does, restart the PC. After the restart, log back in and try running PowerShell again and see what happens. Some of this is here too social.technet.microsoft.com/Forums/lync/en-US/…
– Pimp Juice IT
Jan 31 at 2:29
1
Okay then the next thing to try is to sign onto the PC with another account (or create a new account and then sign on with it) and then try running PowerShell running under that account and see if it does not have the problem. If not, then the Windows user account profile is corrupt and you should rebuild a new one for the existing account.
– Pimp Juice IT
Jan 31 at 15:48
1
You might also check and confirm that all Windows Updates are applied as well and if not consider getting those fully updated to the latest and greatest, reboot, and try again. Lastly, poke thru the Event Viewer system and application logs and see if you notice any errors or warning which correlate to the problem or that you think even might be relevant. All you can do is be extra thorough and a process of elimination short of reinstalling Windows. I dig around the Internet a little more on this issue to see if anything else sticks out to me though.
– Pimp Juice IT
Jan 31 at 15:51
1
Okay, check out this post and read over the comments on the answer as well in case those things help any stackoverflow.com/questions/24875408/… it would be worth at least eliminating some of this as the issue if you want. I assume you already confirming running PowerShell as administrator is not the solution but wanted to mention that as well. Be sure to check thePATHenvironmental variable and the reg path listed in that comment and see what you have there on your side. Perhaps event viewer will show the full exception error message you can disclose.
– Pimp Juice IT
Jan 31 at 16:07
1
What antivirus software package(s) do you have installed on this machine, perhaps there is a security package that is blocking Windows core processes you need to add an exception to? Have you already run throughchdskbut if not, run thruCHKDSK C: /F /R /Xand let that complete, reboot, try again. Have you already done up-to-date virus and malware definition antivirus and antimalware scans including any that performs then offline? These are just other things I can think of which I did not mention, food for thought if nothing else!! Full RAM/memory scan/check too if you can wouldn't hurt,
– Pimp Juice IT
Feb 1 at 21:30
|
show 7 more comments
1
Open command prompt as administrator and runDISM.exe / Online / Cleanup-image / Scanhealth, let that complete and then from the admin elevated command prompt type inDISM.exe / Online / Cleanup-image / Restorehealthand let that complete and once it does, restart the PC. After the restart, log back in and try running PowerShell again and see what happens. Some of this is here too social.technet.microsoft.com/Forums/lync/en-US/…
– Pimp Juice IT
Jan 31 at 2:29
1
Okay then the next thing to try is to sign onto the PC with another account (or create a new account and then sign on with it) and then try running PowerShell running under that account and see if it does not have the problem. If not, then the Windows user account profile is corrupt and you should rebuild a new one for the existing account.
– Pimp Juice IT
Jan 31 at 15:48
1
You might also check and confirm that all Windows Updates are applied as well and if not consider getting those fully updated to the latest and greatest, reboot, and try again. Lastly, poke thru the Event Viewer system and application logs and see if you notice any errors or warning which correlate to the problem or that you think even might be relevant. All you can do is be extra thorough and a process of elimination short of reinstalling Windows. I dig around the Internet a little more on this issue to see if anything else sticks out to me though.
– Pimp Juice IT
Jan 31 at 15:51
1
Okay, check out this post and read over the comments on the answer as well in case those things help any stackoverflow.com/questions/24875408/… it would be worth at least eliminating some of this as the issue if you want. I assume you already confirming running PowerShell as administrator is not the solution but wanted to mention that as well. Be sure to check thePATHenvironmental variable and the reg path listed in that comment and see what you have there on your side. Perhaps event viewer will show the full exception error message you can disclose.
– Pimp Juice IT
Jan 31 at 16:07
1
What antivirus software package(s) do you have installed on this machine, perhaps there is a security package that is blocking Windows core processes you need to add an exception to? Have you already run throughchdskbut if not, run thruCHKDSK C: /F /R /Xand let that complete, reboot, try again. Have you already done up-to-date virus and malware definition antivirus and antimalware scans including any that performs then offline? These are just other things I can think of which I did not mention, food for thought if nothing else!! Full RAM/memory scan/check too if you can wouldn't hurt,
– Pimp Juice IT
Feb 1 at 21:30
1
1
Open command prompt as administrator and run
DISM.exe / Online / Cleanup-image / Scanhealth, let that complete and then from the admin elevated command prompt type in DISM.exe / Online / Cleanup-image / Restorehealth and let that complete and once it does, restart the PC. After the restart, log back in and try running PowerShell again and see what happens. Some of this is here too social.technet.microsoft.com/Forums/lync/en-US/…– Pimp Juice IT
Jan 31 at 2:29
Open command prompt as administrator and run
DISM.exe / Online / Cleanup-image / Scanhealth, let that complete and then from the admin elevated command prompt type in DISM.exe / Online / Cleanup-image / Restorehealth and let that complete and once it does, restart the PC. After the restart, log back in and try running PowerShell again and see what happens. Some of this is here too social.technet.microsoft.com/Forums/lync/en-US/…– Pimp Juice IT
Jan 31 at 2:29
1
1
Okay then the next thing to try is to sign onto the PC with another account (or create a new account and then sign on with it) and then try running PowerShell running under that account and see if it does not have the problem. If not, then the Windows user account profile is corrupt and you should rebuild a new one for the existing account.
– Pimp Juice IT
Jan 31 at 15:48
Okay then the next thing to try is to sign onto the PC with another account (or create a new account and then sign on with it) and then try running PowerShell running under that account and see if it does not have the problem. If not, then the Windows user account profile is corrupt and you should rebuild a new one for the existing account.
– Pimp Juice IT
Jan 31 at 15:48
1
1
You might also check and confirm that all Windows Updates are applied as well and if not consider getting those fully updated to the latest and greatest, reboot, and try again. Lastly, poke thru the Event Viewer system and application logs and see if you notice any errors or warning which correlate to the problem or that you think even might be relevant. All you can do is be extra thorough and a process of elimination short of reinstalling Windows. I dig around the Internet a little more on this issue to see if anything else sticks out to me though.
– Pimp Juice IT
Jan 31 at 15:51
You might also check and confirm that all Windows Updates are applied as well and if not consider getting those fully updated to the latest and greatest, reboot, and try again. Lastly, poke thru the Event Viewer system and application logs and see if you notice any errors or warning which correlate to the problem or that you think even might be relevant. All you can do is be extra thorough and a process of elimination short of reinstalling Windows. I dig around the Internet a little more on this issue to see if anything else sticks out to me though.
– Pimp Juice IT
Jan 31 at 15:51
1
1
Okay, check out this post and read over the comments on the answer as well in case those things help any stackoverflow.com/questions/24875408/… it would be worth at least eliminating some of this as the issue if you want. I assume you already confirming running PowerShell as administrator is not the solution but wanted to mention that as well. Be sure to check the
PATH environmental variable and the reg path listed in that comment and see what you have there on your side. Perhaps event viewer will show the full exception error message you can disclose.– Pimp Juice IT
Jan 31 at 16:07
Okay, check out this post and read over the comments on the answer as well in case those things help any stackoverflow.com/questions/24875408/… it would be worth at least eliminating some of this as the issue if you want. I assume you already confirming running PowerShell as administrator is not the solution but wanted to mention that as well. Be sure to check the
PATH environmental variable and the reg path listed in that comment and see what you have there on your side. Perhaps event viewer will show the full exception error message you can disclose.– Pimp Juice IT
Jan 31 at 16:07
1
1
What antivirus software package(s) do you have installed on this machine, perhaps there is a security package that is blocking Windows core processes you need to add an exception to? Have you already run through
chdsk but if not, run thru CHKDSK C: /F /R /X and let that complete, reboot, try again. Have you already done up-to-date virus and malware definition antivirus and antimalware scans including any that performs then offline? These are just other things I can think of which I did not mention, food for thought if nothing else!! Full RAM/memory scan/check too if you can wouldn't hurt,– Pimp Juice IT
Feb 1 at 21:30
What antivirus software package(s) do you have installed on this machine, perhaps there is a security package that is blocking Windows core processes you need to add an exception to? Have you already run through
chdsk but if not, run thru CHKDSK C: /F /R /X and let that complete, reboot, try again. Have you already done up-to-date virus and malware definition antivirus and antimalware scans including any that performs then offline? These are just other things I can think of which I did not mention, food for thought if nothing else!! Full RAM/memory scan/check too if you can wouldn't hurt,– Pimp Juice IT
Feb 1 at 21:30
|
show 7 more comments
0
active
oldest
votes
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
});
}
});
draft saved
draft discarded
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%2f1399906%2fpowershell-error-the-type-initializer-for-system-net-servicepointmanager-thre%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f1399906%2fpowershell-error-the-type-initializer-for-system-net-servicepointmanager-thre%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
1
Open command prompt as administrator and run
DISM.exe / Online / Cleanup-image / Scanhealth, let that complete and then from the admin elevated command prompt type inDISM.exe / Online / Cleanup-image / Restorehealthand let that complete and once it does, restart the PC. After the restart, log back in and try running PowerShell again and see what happens. Some of this is here too social.technet.microsoft.com/Forums/lync/en-US/…– Pimp Juice IT
Jan 31 at 2:29
1
Okay then the next thing to try is to sign onto the PC with another account (or create a new account and then sign on with it) and then try running PowerShell running under that account and see if it does not have the problem. If not, then the Windows user account profile is corrupt and you should rebuild a new one for the existing account.
– Pimp Juice IT
Jan 31 at 15:48
1
You might also check and confirm that all Windows Updates are applied as well and if not consider getting those fully updated to the latest and greatest, reboot, and try again. Lastly, poke thru the Event Viewer system and application logs and see if you notice any errors or warning which correlate to the problem or that you think even might be relevant. All you can do is be extra thorough and a process of elimination short of reinstalling Windows. I dig around the Internet a little more on this issue to see if anything else sticks out to me though.
– Pimp Juice IT
Jan 31 at 15:51
1
Okay, check out this post and read over the comments on the answer as well in case those things help any stackoverflow.com/questions/24875408/… it would be worth at least eliminating some of this as the issue if you want. I assume you already confirming running PowerShell as administrator is not the solution but wanted to mention that as well. Be sure to check the
PATHenvironmental variable and the reg path listed in that comment and see what you have there on your side. Perhaps event viewer will show the full exception error message you can disclose.– Pimp Juice IT
Jan 31 at 16:07
1
What antivirus software package(s) do you have installed on this machine, perhaps there is a security package that is blocking Windows core processes you need to add an exception to? Have you already run through
chdskbut if not, run thruCHKDSK C: /F /R /Xand let that complete, reboot, try again. Have you already done up-to-date virus and malware definition antivirus and antimalware scans including any that performs then offline? These are just other things I can think of which I did not mention, food for thought if nothing else!! Full RAM/memory scan/check too if you can wouldn't hurt,– Pimp Juice IT
Feb 1 at 21:30