Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invoke-Expression : The term 'Invoke-Expression' is not recognized #636

Closed
Rutix opened this issue Sep 14, 2015 · 0 comments
Closed

Invoke-Expression : The term 'Invoke-Expression' is not recognized #636

Rutix opened this issue Sep 14, 2015 · 0 comments

Comments

@Rutix
Copy link

Rutix commented Sep 14, 2015

Hi,

Sorry if there is already an issue with the following problem but I couldn't find it.
I downloaded cmder ( https://github.com/bliker/cmder/releases/download/v1.2/cmder.7z ) and extracted it to my disk. But when I try to start cmder it refuses to open a working powershell tab.

I sometimes get the following error but not always:

Invoke-Expression : The term 'Invoke-Expression' is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ Invoke-Expression '. ''E:\cmder\vendor\conemu-maximus5\..\profile.ps1'''
+ ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Invoke-Expression:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

The cmd task works fine and starting powershell manually (by starting powershell.exe) also seems to work fine. Is this a known problem? If so how can I fix this?

I am running Windows 8.1 fully updated by windows update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants