Downloads of v


Last Update:

09 Oct 2015

Package Maintainer(s):

Software Author(s):

  • Ryan Conrad


powershell virtualmachine virtualbox internetexplorer ie vm machine testing


This is not the latest version of PSIEVM available. | Updated: 09 Oct 2015



Downloads of v



Software Author(s):

  • Ryan Conrad


This is not the latest version of PSIEVM available.

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test

Validation Testing Passed

Verification Testing Failed


To install PSIEVM, run the following command from the command line or from PowerShell:


To upgrade PSIEVM, run the following command from the command line or from PowerShell:


To uninstall PSIEVM, 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 psievm -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 psievm -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 psievm installed
    name: psievm
    state: present
    source: STEP 3 URL

See docs at

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

chocolatey_package 'psievm' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: psievm,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller psievm
   Name     = 'psievm'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'psievm':
  provider => 'chocolatey',
  ensure   => '',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install psievm version="" 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 29 Dec 2015.


psievm is a powershell module for standing up an IE Virtual Machine in VirtualBox quickly and without hassle. This will do all the steps needed to get the VM running.

#requires -version 3

$name   = 'psievm'

function Download-File {
	Param (
	process {
		"Downloading $url to $file" | Write-Host;
		$downloader = new-object System.Net.WebClient;
		$downloader.DownloadFile($url, $file);

function Install-PSIEVM {
	param (
		[string] $ModulesPath
	begin {
		"Installing PSIEVM PowerShell module" | Write-Host;
		"Copyright (c) 2015 Ryan Conrad" | Write-Host;
		"License:" | Write-Host;
		$url = (Get-LatestGithubRelease -Owner camalot -Repo psievm);
		if ($env:TEMP -eq $null) {
			$env:TEMP = (Join-Path $env:SystemDrive 'temp');

		$tempDir = (Join-Path $env:TEMP "psievm");
		if(!(Test-Path -Path $tempDir)) {
			New-Item -Path $tempDir -ItemType Directory | Out-Null;

		$file = (Join-Path $tempDir "");
		$psievmModulePath = (Join-Path $ModulesPath "psievm");

		if(!(Test-Path -Path $psievmModulePath)) {
			New-Item -Path $psievmModulePath -ItemType Directory | Out-Null;
	process {
		# download the package
		Download-File -url $url -file $file;

		# download 7zip
		"Download 7Zip commandline tool" | Write-Host;
		$7zaExe = (Join-Path $tempDir '7za.exe');
		Download-File -url '' -file "$7zaExe";

		# unzip the package
		"Extracting $file to $ModulesPath" | Write-Host;
		Start-Process "$7zaExe" -ArgumentList "x -o`"$ModulesPath`" -y `"$file`"" -Wait -NoNewWindow;
		"Unblock module files on the system" | Write-Host;
		Get-ChildItem -Path "$psievmModulePath" -File -Recurse | Unblock-File | Out-Null;
	end {
		if(Test-Path -Path $tempDir) {
			"Clean up temp directory [$tempDir]" | Write-Host;
			Remove-Item -Path $tempDir -Force -Recurse | Out-Null;

function Get-LatestGithubRelease {
	This gets the download URL for what ever is the latest release.
		[string] $Owner,
		[string] $Repo
	begin {
		$netAssembly = [Reflection.Assembly]::GetAssembly([System.Net.Configuration.SettingsSection])
		if($netAssembly) {
				$bindingFlags = [Reflection.BindingFlags] "Static,GetProperty,NonPublic";
				$settingsType = $netAssembly.GetType("System.Net.Configuration.SettingsSectionInternal");
				$instance = $settingsType.InvokeMember("Section", $bindingFlags, $null, $null, @());

				if($instance) {
						$bindingFlags = "NonPublic","Instance";
						$useUnsafeHeaderParsingField = $settingsType.GetField("useUnsafeHeaderParsing", $bindingFlags);
						if($useUnsafeHeaderParsingField) {
							$useUnsafeHeaderParsingField.SetValue($instance, $true);
	process {
		$webclient = New-Object net.webclient;
		"Getting latest release information from GitHub Repository $Owner/$Repo" | Write-Host;
		$webclient.Headers.Add("User-Agent", "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.52 Safari/537.36");
		$latest = ($webclient.DownloadString("$Owner/$Repo/releases") | ConvertFrom-Json) | select -First 1;
		"Using release '$($'" | Write-Host;
		$url = $latest.assets | select -ExpandProperty browser_download_url -First 1;
		return $url;

$params = ConvertFrom-StringData ($env:chocolateyPackageParameters -replace ';', "`n");
$ModulesRoot = $params.PSModuleDirectory;

if(-not $ModulesRoot) {
	$userDocsPath = [Environment]::GetFolderPath("MyDocuments");
	$ModulesRoot = (Join-Path $userDocsPath "\WindowsPowerShell\Modules\");

if($env:chocolateyPackageFolder) {
	$ModuleTarget = (Join-Path $env:chocolateyPackageFolder "Modules");
	$PSIEVMModuleTarget = (Join-Path $ModuleTarget "psievm");
	$PSIEVModuleRootPath = (Join-Path $ModulesRoot "psievm");

	Install-PSIEVM -ModulesPath $ModuleTarget;

	if (Test-Path "$PSIEVModuleRootPath") {
		Remove-Item -Path "$PSIEVModuleRootPath" -Force -Recurse | Out-Null;
	"Creating junction: $PSIEVModuleRootPath -> $PSIEVMModuleTarget" | Write-Host;
	cmd /c mklink /j "$PSIEVModuleRootPath" "$PSIEVMModuleTarget";
} else {
	Install-PSIEVM -ModulesPath $ModulesRoot;


$params = ConvertFrom-StringData ($env:chocolateyPackageParameters -replace ';', "`n");
$ModulesRoot = $params.PSModuleDirectory;

if(-not $ModulesRoot) {
	$userDocsPath = [Environment]::GetFolderPath("MyDocuments");
	$ModulesRoot = (Join-Path $userDocsPath "\WindowsPowerShell\Modules\");

$PSIEVMModuleRootPath = (Join-Path $ModulesRoot "psievm");

if($env:chocolateyPackageFolder) {
	$ModuleTarget = (Join-Path $env:chocolateyPackageFolder "Modules");
	if(Test-Path($ModuleTarget)) {
		"Delete $ModuleTarget" | Write-Host;
		Remove-Item -Path $ModuleTarget -Recurse -Force | Out-Null;

if(Test-Path($PSIEVMModuleRootPath)) {
	"Delete $PSIEVMModuleRootPath" | Write-Host;
	cmd /c rmdir "$PSIEVMModuleRootPath";

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
PSIEVM 257 Sunday, October 25, 2015 Approved
PSIEVM 278 Sunday, October 25, 2015 Approved
PSIEVM 254 Friday, October 16, 2015 Approved
PSIEVM 265 Sunday, October 11, 2015 Approved
PSIEVM 265 Friday, October 9, 2015 Approved

This package has no dependencies.

Discussion for the PSIEVM Package

Ground Rules:

  • This discussion is only about PSIEVM and the PSIEVM 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 PSIEVM, 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