Downloads:

542

Downloads of v 0.0.1:

538

Last Update:

14 Jul 2019

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

microsoft windows sandbox feature

Windows Sandbox (Install)

0.0.1 | Updated: 14 Jul 2019

Downloads:

542

Downloads of v 0.0.1:

538

Maintainer(s):

Software Author(s):

  • Microsoft

Windows Sandbox (Install) 0.0.1

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

Requires Windows 10.

To install Windows Sandbox (Install), run the following command from the command line or from PowerShell:

>

To upgrade Windows Sandbox (Install), run the following command from the command line or from PowerShell:

>

To uninstall Windows Sandbox (Install), 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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade windows-sandbox -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 windows-sandbox -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure windows-sandbox installed
  win_chocolatey:
    name: windows-sandbox
    state: present
    version: 0.0.1
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

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


chocolatey_package 'windows-sandbox' do
  action    :install
  version  '0.0.1'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: windows-sandbox,
    Version: 0.0.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller windows-sandbox
{
   Name     = 'windows-sandbox'
   Ensure   = 'Present'
   Version  = '0.0.1'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'windows-sandbox':
  provider => 'chocolatey',
  ensure   => '0.0.1',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install windows-sandbox version="0.0.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator Pauby on 15 Jul 2019.

Description


choco://windows-sandbox

To use choco:// protocol URLs, install (unofficial) choco:// Protocol support


Windows Sandbox is a new lightweight desktop environment tailored for safely running applications in isolation.

NOTE: The version is Chocolatey package related only. Windows Sandbox version corresponds with your Windows build version. The actual version of Windows Sandbox will depend on your version of Windows.

PACKAGE NOTES


Click here to Patreon-ize the package maintainer.



tools\.SkipAutoUninstaller
 
tools\ChocolateyInstall.ps1
$ErrorActionPreference = 'Stop'
$packageName = 'windows-sandbox'

$test=(Get-WindowsOptionalFeature -Featurename "Containers-DisposableClientVM" -Online)
if (!$test) {
    Write-Warning "Unsupported Operating System: Windows 10 Pro or Enterprise 1903 or greater required."
	throw
	}
if ($test.state -eq 'Enabled') {
    Write-Host "  ** Sandbox already installed!" -Foreground Magenta
	return
	} else {
	  Enable-WindowsOptionalFeature -Online -FeatureName Containers-DisposableClientVM -NoRestart
	  }
tools\ChocolateyUninstall.ps1
$ErrorActionPreference = 'Stop'
$packageName = 'windows-sandbox'

Disable-WindowsOptionalFeature -Online -FeatureName Containers-DisposableClientVM -NoRestart

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

This package has no dependencies.

Discussion for the Windows Sandbox (Install) Package

Ground Rules:

  • This discussion is only about Windows Sandbox (Install) and the Windows Sandbox (Install) 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 Windows Sandbox (Install), 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