Downloads of v 2.3.24:


Last Update:

01 Feb 2014

Package Maintainer(s):

Software Author(s):

  • Matt Wrock


devops chocolatey bootstraper setup windows customizations

Boxstarter WinConfig Module

This is not the latest version of Boxstarter WinConfig Module available.

2.3.24 | Updated: 01 Feb 2014



Downloads of v 2.3.24:


Software Author(s):

  • Matt Wrock

Boxstarter WinConfig Module 2.3.24

This is not the latest version of Boxstarter WinConfig Module available.

All Checks are Unknown

2 Test of Unknown Status

Validation Testing Unknown

Verification Testing Unknown

To install Boxstarter WinConfig Module, run the following command from the command line or from PowerShell:


To upgrade Boxstarter WinConfig Module, run the following command from the command line or from PowerShell:


To uninstall Boxstarter WinConfig Module, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade boxstarter.winconfig -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade boxstarter.winconfig -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure boxstarter.winconfig installed
    name: boxstarter.winconfig
    state: present
    version: 2.3.24
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'boxstarter.winconfig' do
  action    :install
  version  '2.3.24'
  source   'STEP 3 URL'

See docs at

    Name: boxstarter.winconfig,
    Version: 2.3.24,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller boxstarter.winconfig
   Name     = 'boxstarter.winconfig'
   Ensure   = 'Present'
   Version  = '2.3.24'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'boxstarter.winconfig':
  provider => 'chocolatey',
  ensure   => '2.3.24',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install boxstarter.winconfig version="2.3.24" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 27 Nov 2014.


Functions that Boxstarter uses to customize the windows environment.

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Boxstarter WinConfig Module 2.12.0 378146 Tuesday, October 30, 2018 Approved
Boxstarter WinConfig Module 2.11.0 65530 Wednesday, May 16, 2018 Approved
Boxstarter WinConfig Module 2.10.3 53525 Thursday, July 27, 2017 Approved
Boxstarter WinConfig Module 2.9.27 2483 Wednesday, June 21, 2017 Approved
Boxstarter WinConfig Module 2.9.26 5308 Monday, June 19, 2017 Approved
Boxstarter WinConfig Module 2.9.24 612 Sunday, June 18, 2017 Approved
Boxstarter WinConfig Module 2.9.14 6811 Friday, May 5, 2017 Approved
Boxstarter WinConfig Module 2.9.5 4717 Thursday, March 30, 2017 Approved

  • report an exception if chocolatey faied to find package
    - Do not attempt to install windows updates that require user interaction
    - Fix Windows Update from breaking when reseting the windows update service if it was stopped prior to running
    - Load VM Plugins relative to current path and not by module name in case module is not in PSModulePath
    - Fix pipeline input of VM names broken by function proxy
    - Can supply multiple packages to Install-BoxstarterPackage and Launch URLs
    - Boxstarter.Azure now globally imports the Windows Azure module
    - Fixed issues with using the Boxstarter Web launcher to install Boxstarter
    - Fixed errors when installing Boxstarter with Chocolatey in the same session after installing Chocolatey
    - Adds Windows Azure VM Integration
    - Supports VM Checkpoints using Azure Blob Snapshots
    - Adds Graceful failure to Enable-RemoteDesktop for Home versions of Windows 7
    - Adds support for unattended install of Boxstarter
Discussion for the Boxstarter WinConfig Module Package

Ground Rules:

  • This discussion is only about Boxstarter WinConfig Module and the Boxstarter WinConfig Module package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Boxstarter WinConfig Module, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus