Powershell locks up for any command
2
Windows Server 2008 R2
When typing anything (or nothing) into PowerShell, and hitting enter it just locks up with a flashing cursor and does nothing for about 20 to 30 minutes. After waiting a long time, PowerShell works, it just takes a long time to initialize.
- I've installed Windows Management Framework 4.0 and rebooted
- I've tried SFC scan (no issues found)
- I've tried from a different user profile
- I've tried with the -noprofile switch
- I've tried with different PowerShell versions with the -version switch
- PSModulePath=C:Windowssystem32WindowsPowerShellv1.0Modules
Another thing I've noticed is that when starting version 1.0 or 2.0, I don't even get a command prompt, just a Windows PowerShell Copyright and a flashing cursor.
Everything else on the server works fine!
PSVersionTable: Major Minor Build Revision
4 0 -1 -1
powershell windows-server-2008-r2
asked Dec 18 '18 at 2:55
XebozoneXebozone
112
add a comment |
2
Windows Server 2008 R2
When typing anything (or nothing) into PowerShell, and hitting enter it just locks up with a flashing cursor and does nothing for about 20 to 30 minutes. After waiting a long time, PowerShell works, it just takes a long time to initialize.
- I've installed Windows Management Framework 4.0 and rebooted
- I've tried SFC scan (no issues found)
- I've tried from a different user profile
- I've tried with the -noprofile switch
- I've tried with different PowerShell versions with the -version switch
- PSModulePath=C:Windowssystem32WindowsPowerShellv1.0Modules
Another thing I've noticed is that when starting version 1.0 or 2.0, I don't even get a command prompt, just a Windows PowerShell Copyright and a flashing cursor.
Everything else on the server works fine!
PSVersionTable: Major Minor Build Revision
4 0 -1 -1
powershell windows-server-2008-r2
asked Dec 18 '18 at 2:55
XebozoneXebozone
112
Is this a domain member server or standalone playing server? Is the server a VM and when you did your pristine build, did you create a snapshot? What role is the server playing? If this is real hardware, after you pristine build, did you do a full back up and capture the system state? If none of the above are true, you may be in a rebuild from scratch, or deal with the delay, as this sounds like a full environmental issue.
– postanote
Dec 18 '18 at 3:47
Domain member. It's actually the primary DC
– Xebozone
Dec 18 '18 at 3:48
Completely rebuilding from scratch seems pretty extreme without any troubleshooting. If it was such a serious issue you would notice other issues as well. Have you checked the event logs? Do you notice any other delays or issues with the server? Any hardware diagnostics done? I notice powershell always takes some time to initialize when I start it. I’ve found that I often have to press enter to kick start it and get a prompt. I imagine there is something it is doing and it just happens to be more problematic for you.
– Appleoddity
Dec 18 '18 at 4:24
Possible duplicate of Powershell very slow to open/respond
– Appleoddity
Dec 18 '18 at 6:14
I believe that caching was an issue. I noticed that after leaving PowerShell to load, and waited, it seemed to speed up the subsequent time. I applied that script as above, which should hopefully help. Will keep an eye on things. Thanks for the support so far
– Xebozone
Dec 20 '18 at 1:57
add a comment |
2
2
2
Windows Server 2008 R2
When typing anything (or nothing) into PowerShell, and hitting enter it just locks up with a flashing cursor and does nothing for about 20 to 30 minutes. After waiting a long time, PowerShell works, it just takes a long time to initialize.
- I've installed Windows Management Framework 4.0 and rebooted
- I've tried SFC scan (no issues found)
- I've tried from a different user profile
- I've tried with the -noprofile switch
- I've tried with different PowerShell versions with the -version switch
- PSModulePath=C:Windowssystem32WindowsPowerShellv1.0Modules
Another thing I've noticed is that when starting version 1.0 or 2.0, I don't even get a command prompt, just a Windows PowerShell Copyright and a flashing cursor.
Everything else on the server works fine!
PSVersionTable: Major Minor Build Revision
4 0 -1 -1
powershell windows-server-2008-r2
asked Dec 18 '18 at 2:55
XebozoneXebozone
112
Windows Server 2008 R2
When typing anything (or nothing) into PowerShell, and hitting enter it just locks up with a flashing cursor and does nothing for about 20 to 30 minutes. After waiting a long time, PowerShell works, it just takes a long time to initialize.
- I've installed Windows Management Framework 4.0 and rebooted
- I've tried SFC scan (no issues found)
- I've tried from a different user profile
- I've tried with the -noprofile switch
- I've tried with different PowerShell versions with the -version switch
- PSModulePath=C:Windowssystem32WindowsPowerShellv1.0Modules
Another thing I've noticed is that when starting version 1.0 or 2.0, I don't even get a command prompt, just a Windows PowerShell Copyright and a flashing cursor.
Everything else on the server works fine!
PSVersionTable: Major Minor Build Revision
4 0 -1 -1
powershell windows-server-2008-r2
powershell windows-server-2008-r2
asked Dec 18 '18 at 2:55
XebozoneXebozone
112
asked Dec 18 '18 at 2:55
XebozoneXebozone
112
asked Dec 18 '18 at 2:55
XebozoneXebozone
112
asked Dec 18 '18 at 2:55
XebozoneXebozone
112
asked Dec 18 '18 at 2:55
XebozoneXebozone
112
112
Is this a domain member server or standalone playing server? Is the server a VM and when you did your pristine build, did you create a snapshot? What role is the server playing? If this is real hardware, after you pristine build, did you do a full back up and capture the system state? If none of the above are true, you may be in a rebuild from scratch, or deal with the delay, as this sounds like a full environmental issue.
– postanote
Dec 18 '18 at 3:47
Domain member. It's actually the primary DC
– Xebozone
Dec 18 '18 at 3:48
Completely rebuilding from scratch seems pretty extreme without any troubleshooting. If it was such a serious issue you would notice other issues as well. Have you checked the event logs? Do you notice any other delays or issues with the server? Any hardware diagnostics done? I notice powershell always takes some time to initialize when I start it. I’ve found that I often have to press enter to kick start it and get a prompt. I imagine there is something it is doing and it just happens to be more problematic for you.
– Appleoddity
Dec 18 '18 at 4:24
Possible duplicate of Powershell very slow to open/respond
– Appleoddity
Dec 18 '18 at 6:14
I believe that caching was an issue. I noticed that after leaving PowerShell to load, and waited, it seemed to speed up the subsequent time. I applied that script as above, which should hopefully help. Will keep an eye on things. Thanks for the support so far
– Xebozone
Dec 20 '18 at 1:57
add a comment |
Is this a domain member server or standalone playing server? Is the server a VM and when you did your pristine build, did you create a snapshot? What role is the server playing? If this is real hardware, after you pristine build, did you do a full back up and capture the system state? If none of the above are true, you may be in a rebuild from scratch, or deal with the delay, as this sounds like a full environmental issue.
– postanote
Dec 18 '18 at 3:47
Domain member. It's actually the primary DC
– Xebozone
Dec 18 '18 at 3:48
Completely rebuilding from scratch seems pretty extreme without any troubleshooting. If it was such a serious issue you would notice other issues as well. Have you checked the event logs? Do you notice any other delays or issues with the server? Any hardware diagnostics done? I notice powershell always takes some time to initialize when I start it. I’ve found that I often have to press enter to kick start it and get a prompt. I imagine there is something it is doing and it just happens to be more problematic for you.
– Appleoddity
Dec 18 '18 at 4:24
Possible duplicate of Powershell very slow to open/respond
– Appleoddity
Dec 18 '18 at 6:14
I believe that caching was an issue. I noticed that after leaving PowerShell to load, and waited, it seemed to speed up the subsequent time. I applied that script as above, which should hopefully help. Will keep an eye on things. Thanks for the support so far
– Xebozone
Dec 20 '18 at 1:57
Is this a domain member server or standalone playing server? Is the server a VM and when you did your pristine build, did you create a snapshot? What role is the server playing? If this is real hardware, after you pristine build, did you do a full back up and capture the system state? If none of the above are true, you may be in a rebuild from scratch, or deal with the delay, as this sounds like a full environmental issue.
– postanote
Dec 18 '18 at 3:47
Is this a domain member server or standalone playing server? Is the server a VM and when you did your pristine build, did you create a snapshot? What role is the server playing? If this is real hardware, after you pristine build, did you do a full back up and capture the system state? If none of the above are true, you may be in a rebuild from scratch, or deal with the delay, as this sounds like a full environmental issue.
– postanote
Dec 18 '18 at 3:47
Domain member. It's actually the primary DC
– Xebozone
Dec 18 '18 at 3:48
Domain member. It's actually the primary DC
– Xebozone
Dec 18 '18 at 3:48
Completely rebuilding from scratch seems pretty extreme without any troubleshooting. If it was such a serious issue you would notice other issues as well. Have you checked the event logs? Do you notice any other delays or issues with the server? Any hardware diagnostics done? I notice powershell always takes some time to initialize when I start it. I’ve found that I often have to press enter to kick start it and get a prompt. I imagine there is something it is doing and it just happens to be more problematic for you.
– Appleoddity
Dec 18 '18 at 4:24
Completely rebuilding from scratch seems pretty extreme without any troubleshooting. If it was such a serious issue you would notice other issues as well. Have you checked the event logs? Do you notice any other delays or issues with the server? Any hardware diagnostics done? I notice powershell always takes some time to initialize when I start it. I’ve found that I often have to press enter to kick start it and get a prompt. I imagine there is something it is doing and it just happens to be more problematic for you.
– Appleoddity
Dec 18 '18 at 4:24
Possible duplicate of Powershell very slow to open/respond
– Appleoddity
Dec 18 '18 at 6:14
Possible duplicate of Powershell very slow to open/respond
– Appleoddity
Dec 18 '18 at 6:14
I believe that caching was an issue. I noticed that after leaving PowerShell to load, and waited, it seemed to speed up the subsequent time. I applied that script as above, which should hopefully help. Will keep an eye on things. Thanks for the support so far
– Xebozone
Dec 20 '18 at 1:57
I believe that caching was an issue. I noticed that after leaving PowerShell to load, and waited, it seemed to speed up the subsequent time. I applied that script as above, which should hopefully help. Will keep an eye on things. Thanks for the support so far
– Xebozone
Dec 20 '18 at 1:57
add a comment |
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%2f1385413%2fpowershell-locks-up-for-any-command%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%2f1385413%2fpowershell-locks-up-for-any-command%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
Is this a domain member server or standalone playing server? Is the server a VM and when you did your pristine build, did you create a snapshot? What role is the server playing? If this is real hardware, after you pristine build, did you do a full back up and capture the system state? If none of the above are true, you may be in a rebuild from scratch, or deal with the delay, as this sounds like a full environmental issue.
– postanote
Dec 18 '18 at 3:47
Domain member. It's actually the primary DC
– Xebozone
Dec 18 '18 at 3:48
Completely rebuilding from scratch seems pretty extreme without any troubleshooting. If it was such a serious issue you would notice other issues as well. Have you checked the event logs? Do you notice any other delays or issues with the server? Any hardware diagnostics done? I notice powershell always takes some time to initialize when I start it. I’ve found that I often have to press enter to kick start it and get a prompt. I imagine there is something it is doing and it just happens to be more problematic for you.
– Appleoddity
Dec 18 '18 at 4:24
Possible duplicate of Powershell very slow to open/respond
– Appleoddity
Dec 18 '18 at 6:14
I believe that caching was an issue. I noticed that after leaving PowerShell to load, and waited, it seemed to speed up the subsequent time. I applied that script as above, which should hopefully help. Will keep an eye on things. Thanks for the support so far
– Xebozone
Dec 20 '18 at 1:57