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

Startup Error: cmder\vendor\profile.ps1 cannot be loaded. #769

Closed
alanyee opened this issue Dec 13, 2015 · 5 comments
Closed

Startup Error: cmder\vendor\profile.ps1 cannot be loaded. #769

alanyee opened this issue Dec 13, 2015 · 5 comments

Comments

@alanyee
Copy link

alanyee commented Dec 13, 2015

Everytime I start up Cmder, I get

. : File C:\Users\Alan\Desktop\Dropbox\cmder\vendor\profile.ps1 cannot be loaded. The file
C:\Users\Alan\Desktop\Dropbox\cmder\vendor\profile.ps1 is not digitally signed. You cannot run this script on
the current system. For more information about running scripts and setting execution policy, see
about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ . 'C:\Users\Alan\Desktop\Dropbox\cmder\vendor\conemu-maximus5\..\prof ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

How do I fix this problem?

@alanyee alanyee changed the title Startup error with ps1 Startup Error: cmder\vendor\profile.ps1 cannot be loaded. Dec 13, 2015
@daxgames
Copy link
Member

Open PowerShell. Type 'set-execution policy remotesigned' without the quotes.

@daxgames
Copy link
Member

Needs to be PowerShell as admin

@alanyee
Copy link
Author

alanyee commented Dec 13, 2015

Oh I just reinstalled cmder, and it worked. Anyways thanks for the help.

@alanyee alanyee closed this as completed Dec 13, 2015
@ngocphamm
Copy link

For others having same issue, I don't know why but the command I have to put into PowerShell is set-ExecutionPolicy remotesigned. Thanks @daxgames for the hint!

@rowet
Copy link

rowet commented Jul 9, 2019

I do not have privileges to set the execution policy at the Machine or User policy level, so the fix does not work.
Is there any other way to get around this annoying error? Perhaps generate a local signature? (I don't know how signing works.)

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

4 participants