-
Notifications
You must be signed in to change notification settings - Fork 162
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
Error when user denies execution from Boxstarter is uncaught #301
Comments
I get this always when I run boxstarter for the first time. Eg if I click on this link http://boxstarter.org/package/nr/url?https://raw.githubusercontent.com/laurentkempe/Cacao/master/PrepareMyCacao.ps1 I click on a link in Edge Then I click the link second time I am running it on freshly installed Windows 10 x64 build 1803 Pro edition. |
@martinskuta @laurentkempe would either of you be able to check that it wasn't this issue that you are running into? https://stackoverflow.com/questions/50379742/clickonce-app-doesnt-start-with-windows-1803 |
As a workaround you can install boxstarter locally and then refer it to the same scripts you're attempting to run. |
Yeah @gep13 it might have been my issue for sure! on @martinskuta VM we have seen the exception described in that issue, but let's try it again next week and we let you know
Thanks @yodurr exactly what I did at the end. But clicking on an hyperlink on a webpage is so much fun 😄 |
Yep it is that, when I changed Check app and files OFF as described in the stackoverflow thread, everything ran properly. |
One of my 1803 machines is not reproducing this bug anymore. Anyone else seeing a change in behavior? |
I think we should close this issue - I'm not having this problem anymore. |
Closing as requested |
Windows will pop up a dialog asking permission for the second command window that Boxstarter opens. The exception that's thrown when the user denies this permission is uncaught.
Is it possible to catch this, and display in some nice bright text:
"You denied permission to run Boxstarter. Packages X Y Z will not be installed."
The text was updated successfully, but these errors were encountered: