Windows terminal not showing cursor for couple minutes when starting #13188

@DHowett commented on GitHub (Mar 25, 2021):

If you open powershell without Terminal, what happens?

@DHowett commented on GitHub (Mar 25, 2021): If you open powershell **without** Terminal, what happens?

claunia commented

@mjrlgue commented on GitHub (Mar 26, 2021):

same thing with powershell prints the same message OperationStopped ...

@mjrlgue commented on GitHub (Mar 26, 2021): same thing with powershell prints the same message `OperationStopped ...`

claunia commented

@zadjii-msft commented on GitHub (Mar 26, 2021):

Well good, then we know this isn't specific to the Terminal!

What about cmd.exe, does that work?
Does powershell --nologo -noprofile?

@zadjii-msft commented on GitHub (Mar 26, 2021): Well good, then we know this isn't specific to the Terminal! * What about `cmd.exe`, does that work? * Does `powershell --nologo -noprofile`?

claunia commented

@mjrlgue commented on GitHub (Mar 26, 2021):

cmd.exe work well
when I type powershell --nologo -noprofile in both cmd.exe and powershell, I get this error message:

At character Line: 1: 3
+ --nologo -noprofile
+   ~
Missing expression after the unary operator « -- ».
At character Line: 1: 3
+ --nologo -noprofile
+   ~~~~~~
Unexpected "nologo" token in the expression or instruction.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

@mjrlgue commented on GitHub (Mar 26, 2021): - `cmd.exe` work well - when I type `powershell --nologo -noprofile` in both `cmd.exe` and `powershell`, I get this error message: ``` At character Line: 1: 3 + --nologo -noprofile + ~ Missing expression after the unary operator « -- ». At character Line: 1: 3 + --nologo -noprofile + ~~~~~~ Unexpected "nologo" token in the expression or instruction. + CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException + FullyQualifiedErrorId : MissingExpressionAfterOperator ```

claunia commented

@mjrlgue commented on GitHub (Mar 26, 2021):

I don't know what's wrong with powershell it was working fine :(

@mjrlgue commented on GitHub (Mar 26, 2021): I don't know what's wrong with powershell it was working fine :(

claunia commented

@zadjii-msft commented on GitHub (Mar 26, 2021):

My bad, that was a typo. Try powershell -nologo -noprofile

@zadjii-msft commented on GitHub (Mar 26, 2021): My bad, that was a typo. Try `powershell -nologo -noprofile`

claunia commented

@mjrlgue commented on GitHub (Mar 26, 2021):

No worries, I get nothing in return in both cmd.exe and powershell

@mjrlgue commented on GitHub (Mar 26, 2021): No worries, I get nothing in return in both `cmd.exe` and `powershell`

claunia commented

@zadjii-msft commented on GitHub (Mar 26, 2021):

Wait like, nothing at all? It should boot into powershell, like this:

I suppose in PowerShell's case, it'll seem like it did nothing, but it should create a new nested instance of PowerShell.

Does %USERPROFILE%\Documents\PowerShell\Microsoft.PowerShell_profile.ps1 exist (and have any contents)? It might be under %USERPROFILE%\Documents\WindowsPowerShell, and the filename might be different - we're really just looking for any .ps1 scripts in that directory.

@zadjii-msft commented on GitHub (Mar 26, 2021): Wait like, nothing _at all_? It should boot into powershell, like this: ![image](https://user-images.githubusercontent.com/18356694/112642538-6715c400-8e11-11eb-9841-981875c8eb67.png) I suppose in PowerShell's case, it'll _seem_ like it did nothing, but it should create a new nested instance of PowerShell. Does `%USERPROFILE%\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` exist (and have any contents)? It might be under `%USERPROFILE%\Documents\WindowsPowerShell`, and the filename might be different - we're really just looking for any `.ps1` scripts in that directory.

claunia commented

2026-01-31 03:36:13 +00:00

@mjrlgue commented on GitHub (Mar 26, 2021):

yes sorry it boots in powershell didn't pay attention to the PS at the beginning.
I checked %USERPROFILE%\Documents\WindowsPowerShell it's empty.
The following directory %USERPROFILE%\Documents\PowerShell contains the ps file Microsoft.PowerShell_profile.ps1 and there is two directories Modules and Scripts

@mjrlgue commented on GitHub (Mar 26, 2021): yes sorry it boots in powershell didn't pay attention to the `PS` at the beginning. I checked `%USERPROFILE%\Documents\WindowsPowerShell` it's empty. The following directory `%USERPROFILE%\Documents\PowerShell` contains the ps file `Microsoft.PowerShell_profile.ps1` and there is two directories `Modules` and `Scripts`

claunia commented

@zadjii-msft commented on GitHub (Mar 26, 2021):

What are the contents of Microsoft.PowerShell_profile.ps1?

@zadjii-msft commented on GitHub (Mar 26, 2021): What are the contents of `Microsoft.PowerShell_profile.ps1`?

claunia commented

2026-01-31 03:36:13 +00:00

@mjrlgue commented on GitHub (Mar 26, 2021):

it's an empty file

@mjrlgue commented on GitHub (Mar 26, 2021): it's an empty file

claunia commented

2026-01-31 03:36:13 +00:00

@zadjii-msft commented on GitHub (Mar 26, 2021):

Huh. Is there a difference between:

powershell.exe -nologo
powershell.exe -noprofile
powershell.exe -nologo -noprofile

for you?

Clearly, if you're not getting the error in the third case, then there's something that those flags are disabling which is causing the error, but I don't know enough about powershell to be sure what it is.

@zadjii-msft commented on GitHub (Mar 26, 2021): Huh. Is there a difference between: * `powershell.exe -nologo` * `powershell.exe -noprofile` * `powershell.exe -nologo -noprofile` for you? Clearly, if you're not getting the error in the third case, then there's something that those flags are disabling which is causing the error, but I don't know enough about powershell to be sure what it is.

claunia commented

@mjrlgue commented on GitHub (Mar 26, 2021):

All command executed with no error

@mjrlgue commented on GitHub (Mar 26, 2021): All command executed with no error

claunia commented

@mjrlgue commented on GitHub (Mar 26, 2021):

I just started powershell with administrator privilege and got the following message in red:

.: File C:\Users\myUser\Documents\PowerShell\Microsoft.PowerShell_profile.ps1 cannot be loaded because its operation is blocked by software restriction policies, such as those created by using Group Policy.
Loading personal and system profiles took 791ms.

when I start it without administrator privilege i get the message with OperationStopped: ..

@mjrlgue commented on GitHub (Mar 26, 2021): I just started powershell with administrator privilege and got the following message in red: ``` .: File C:\Users\myUser\Documents\PowerShell\Microsoft.PowerShell_profile.ps1 cannot be loaded because its operation is blocked by software restriction policies, such as those created by using Group Policy. Loading personal and system profiles took 791ms. ``` when I start it without administrator privilege i get the message with `OperationStopped: ..`

claunia commented

@DHowett commented on GitHub (Mar 26, 2021):

So PowerShell is taking a while to start up because your profile was blocked by the “script execution policy.” There’s a bunch of documentation about this online! 😄

@DHowett commented on GitHub (Mar 26, 2021): So PowerShell is taking a while to start up because your profile was blocked by the “script execution policy.” There’s a bunch of documentation about this online! :smile:

claunia commented