Boxstarter.ps1 failed to invoke expression about packer-templates HOT 6 OPEN

Strange. I just kicked off a packer run to see if this reproduces. Did not have any luck reproducing this error. Its odd that it complains that "The definition "Get-Boxstarter" was not recognised" because that is the function that it is running inside of.

from packer-templates.

Just found out that this error occures when executing boxstarter.ps1 without admin privileges (tried to reproduce why the script didnt run until the end and executed boxstarter.ps1 for debugging purposes - without admin privileges... dumb myself).

Now the Get-Boxstarter cmdlet is invoked and running, though it throws now the actual error which made the script stop.

This does happen when executing the Get-Boxstarter cmdlet aswell as manually executing cinst Boxstarter -version 2.6.41 in the powershell. The chocolatey logfile doesnt give more information.
When cinst Boxstarter on my host machine it does work without any errors. The VM has unrestricted access to the network and clist Boxstarter returns the full dependency list.

from packer-templates.

very strange. Curious what happens if you run cinst Boxstarter.Common

from packer-templates.

Runs without problems and installs the Boxstarter.Common package.

Edit: I did the following steps to detect if this problem remains to my configuration/iso or maybe this is being more general.

• cloned this repository
• replaced iso_checksum and iso_url with my local ISO
• set german as the default language in Autounattend.xml (en-US => de-DE) because Ive only got a german ISO
• ran packer build -only virtualbox-iso -force vbox-2012r2.json

And still, the unresolved dependency of Boxstarter.Common shows up and the boxstarter.ps1 script fails. (Here is my final almost untouched vbox-2012r2.json).

So the error thrown belongs either to my ISO or my environment.
Since I can use the IE inside my (incomplete) machine the internet connection does work as expected, I can ping packages.chocolatey.org without problems and also install Boxstarter.Common by hand I dont think this error is related to network stuff.

Also, I'm curious if my ISO can cause such a problem - its most likely an original copy and has all features needed packaged.

from packer-templates.

@LokiTaria it's possible some part of the software isn't fully i18n compliant and can't handle the German names vs the English ones. Could you test with leaving the language on your ISO as English in the unattend, and then in the "postunattend.xml" try changing the language? You should be able to copy the XML block for language and drop it into the appropriate section since it is basically just another Autounattend that runs after the install is complete.

from packer-templates.

Actually the Boxstarter.ps1 doesn't work with Windows 7 Enterprise at the line 11:

Import-Module $env:appdata\boxstarter\boxstarter.chocolatey\boxstarter.chocolatey.psd1

because the folder boxstarter in AppData\Roaming isn't created due faulty chocolatey setup

EDIT: I've found out that in the function Enable-Net40 it's downloaded .NET 4.5 instead of downloading the .Net 4.0 (at this location)

from packer-templates.