Manfred Wallner

can we postpone this to milestone 3.0.1 ? :smile:

I'm having trouble reproducing this issue on my machine(s). can you check what the value of `$VerbosePreference` is in your BoxstarterShell before you invoke `Install-BoxstarterPackage` ? Also, can you try...

@pauby - imo there are two possible ways to resolve this.. *1: change the reboot-wrapper for the sched.tasks so it always loads the full boxstarter context before executing anything *2:...

this might be fixed with Boxstarter v3, I'm moving it to take a look at again in milestone 3.0.1 anyway.

thanks for getting this fixed @MalwareMechanic ! CC @gep13 - I think we're having some issues with gitversion in the appveyor build - `3.1.0-fix-verbose-output-20220718` is too long as package version...

I'd like to put some prio on this issue, maybe we can even have this for v2.13.0 ?

I'm okay with it if we can get out 2.13 quickly so we can focus on 2.14 :smile: * the highly needed refactoring kind of depends on having the tests...

hey @rgl - have you had a look at https://github.com/chocolatey/chocolatey-test-environment ?

As far as I've understood this "chocolatey-test-environment" uses a powershell bootstrapper to install chocolatey packages. You could simply drop in "Install-BoxstarterPackage X" instead of "choco install X" in the bootstrapper...

oh right, was not aware of that - thanks :)