-
Notifications
You must be signed in to change notification settings - Fork 239
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
2.25.0 is broken on Windows due to ExecutionPolicy requirement; recommended to use 2.24 for now #3812
Comments
@jeffmaury does running i tried to reproduce by upgrading CRC from
|
Check the timestamp the file is huge i'm a long time user of CRC ! 🥲 |
Please note that it has also been reported by a Podman Desktop user on Discord: https://discord.com/channels/852634929845239818/1085121643782873118/threads/1145952685464485938 |
A I went through the discord thread, it seems that user tried to start the daemon manually and then run
@jeffmaury can you please also share the content of |
So after debugging with @jeffmaury we found the cause to be the To fix the issue we ran @gbraad maybe we need to add a preflight check or custom action in the MSI to set the execution policy to allow to run posh scripts? |
Why was it setup to "restricted"? shouldn't be an error message explaining the error too? |
This is the default on Windows |
the default effective policy is Restricted which prevents the hidden_daemon.ps1 script from running when started from the scheduled task this fixes crc-org#3812
the default effective policy is Restricted which prevents the hidden_daemon.ps1 script from running which is started from the scheduled task to run the daemon this fixes crc-org#3812
yep; this is the default... and most likely why I can not repeat the issue: I have changed this policy :-/ |
perhaps a GUI wrapper to handle this case might be cleaner (changing the policy might not be something that everybody can do). |
the default effective policy is Restricted which prevents the hidden_daemon.ps1 script from running which is started from the scheduled task to run the daemon this fixes #3812
General information
crc setup
before starting it (Yes/No)?YesCRC version
CRC status
CRC config
- preset : microshift
Host Operating System
Steps to reproduce
Expected
Daemon should start
Actual
Daemon does not start
Logs
crc.log
Please consider posting the output of
crc start --log-level debug
on http://gist.github.com/ and post the link in the issue.The text was updated successfully, but these errors were encountered: