-
Notifications
You must be signed in to change notification settings - Fork 30
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
Cannot install chocolatey - chocolateyInstall.ps1 is not digitally signed #141
Comments
@opoplawski looking into the latter error it sounds like we might also need to run Unblock-File on the script? https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0713009 Although I had thought that this wasn't something that would normally happen for files created in this manner 🤔 |
Set-Content can cause a trailing newline to be added, which will break the signature if the script is signed.
Trying out running tests in RemoteSigned mode, to see if things work as expected there.
Trying out running tests in RemoteSigned mode, to see if things work as expected there.
@opoplawski Can you try the branch from #161 to see if that helps any for the issue you're seeing? More information about the client machine would be useful, too; this isn't a signing issue exactly, Ansible automatically runs scripts with the execution policy set to Unrestricted, this is something else. The error reminds me a bit of perhaps AppLocker or something of that nature, perhaps? |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
Checklist
What You Are Seeing?
Trying to do an initial chocolatey install on a Windows 11 Enterprise machine I get:
What is Expected?
Chocolatey is installed
How Did You Get This To Happen?
System Details
Installed Packages
Output Log
Additional Context
I can fix the signing issue by adding
-NoNewline
to theSet-Content
call. But then I get:The text was updated successfully, but these errors were encountered: