Manfred Wallner

ping @pauby / @JPRuskin - maybe this is something we should take a look at again now that version v3 is around the corner?

I like the idea of having a "unstable release" for each PR that gets merged onto develop - if these releases were available via a nuget feed it'd be a...

maybe postpone this to milestone 3.0.1?

Currently the "validity" of an URL / file is checked in [`New-PackageFromScript`](https://github.com/chocolatey/boxstarter/blob/5880cb112afa5bfeab39f1bd8b761681fe90e7c3/Boxstarter.Chocolatey/New-PackageFromScript.ps1#L61), which is called _way in_ the Boxstarter workflow. We'll have to do this at the very beginning, before...

This might go under "Setting up Chocolatey for organizational use" : http://mwallner.net/2017/06/10/using-chocolatey-in-corporate-environments-part-1/ - even though just "part 1" :-)

issue is most likely in https://github.com/chocolatey/boxstarter/blob/f3634ceddf5efca4a21f8a572a5bc2dd3a6e1f53/Boxstarter.Chocolatey/New-PackageFromScript.ps1#L58 -> `Call-Chocolatey` w/o arguments breaks further workflow

Without getting into all the detail, may I suggest you add ``` Install-WindowsUpdate -AcceptEula ``` at the very end of your Boxstarter install script(s) ? I suspect this would solve...

Update: cannot reproduce this issue anymore :shrug:

heya, not going to make any promises, but I can tell you that I'm working on two (other) different defect-type-issues that will make it into a bugfix-type version somewhen soonish....

as long as this issue persists, you could "automatically" fix the sources by doing something like ``` $ErrorActionPreference = "Stop" $cfgLocation = (Join-Path $env:ChocolateyInstall "config/chocolatey.config") if (-Not (Test-Path $cfgLocation)) {...