Downloads:

135,452

Downloads of v 4.4.170:

30,185

Last Update:

28 May 2022

Package Maintainer(s):

Software Author(s):

  • Ivo Beltchev

Tags:

classic-shell open-shell shell freeware start-menu binary

Open-Shell (Install)

  • 1
  • 2
  • 3

4.4.170 | Updated: 28 May 2022

Downloads:

135,452

Downloads of v 4.4.170:

30,185

Maintainer(s):

Software Author(s):

  • Ivo Beltchev

  • 1
  • 2
  • 3
Open-Shell (Install) 4.4.170

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Open-Shell (Install), run the following command from the command line or from PowerShell:

>

To upgrade Open-Shell (Install), run the following command from the command line or from PowerShell:

>

To uninstall Open-Shell (Install), run the following command from the command line or from PowerShell:

>

Deployment Method:

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

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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://community.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. Copy Your Script

choco upgrade open-shell -y --source="'INTERNAL REPO 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 open-shell -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install open-shell
  win_chocolatey:
    name: open-shell
    version: '4.4.170'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'open-shell' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '4.4.170'
end

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


cChocoPackageInstaller open-shell
{
    Name     = "open-shell"
    Version  = "4.4.170"
    Source   = "INTERNAL REPO URL"
}

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


package { 'open-shell':
  ensure   => '4.4.170',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 28 May 2022.

Description

Open-Shell Open-Shell

Originally Classic Shell by Ivo Beltchev

Features

  • Classic style Start Menu for Windows 7, 8, 8.1, 10
  • Toolbar for Windows Explorer
  • Classic copy UI (Windows 7 only)
  • Show file size in Explorer status bar
  • Title bar and status bar for Internet Explorer

Package specific

By default, the package installs all three components, i.e. Open-Shell Menu, Classic Explorer, and Classic IE.
If you do want all three components, you can select which components you want via package parameters, which are documented below.

Package Parameters

The following package parameters can be set:

  • /StartMenu - Add the Open-Shell Menu component
  • /ClassicExplorer - Add the Classic Explorer component
  • /ClassicIE - Add the Classic IE component

To pass parameters, use --params "''" (e.g. choco install packageID [other options] --params="'/ITEM:value /ITEM2:value2 /FLAG_BOOLEAN'").
To have choco remember parameters on upgrade, be sure to set choco feature enable -n=useRememberedArgumentsForUpgrades.

Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.


legal\LICENSE.txt
From: https://github.com/Open-Shell/Open-Shell-Menu/blob/master/LICENSE
---------------------------------
MIT License

Copyright (c) 2017-2018

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
legal\VERIFICATION.txt
VERIFICATION

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to

   x32: https://github.com/Open-Shell/Open-Shell-Menu/releases/download/v4.4.170/OpenShellSetup_4_4_170.exe

   to download the installer.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum32: 0417041CFFED3478F13A840E45EE304CCF8D1F9CA38E4126BC315161AC9F1669
   checksumType: sha256
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'
$toolsDir              = Split-Path -parent $MyInvocation.MyCommand.Definition
$pp                    = Get-PackageParameters
$silentArgs            = '/qn'

if ($pp['StartMenu'] -or $pp['ClassicExplorer'] -or $pp['ClassicIE']) {
    $silentArgs = $silentArgs + ' ADDLOCAL='
    
    if ($pp['StartMenu']) {
        $silentArgs = $silentArgs + 'StartMenu,'
    }
    if ($pp['ClassicExplorer']) {
        $silentArgs = $silentArgs + 'ClassicExplorer,'
    }
    if ($pp['ClassicIE']) {
        $silentArgs = $silentArgs + 'ClassicIE'
    }
}

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  fileType       = 'EXE'
  file           = Join-Path $toolsDir 'OpenShellSetup_4_4_170.exe'
  softwareName   = 'Open-Shell*'
  silentArgs     = $silentArgs
  validExitCodes = @(0)
}

Install-ChocolateyInstallPackage @packageArgs

Remove-Item "$toolsDir\*.exe" -Force -EA SilentlyContinue | Out-Null
tools\OpenShellSetup_4_4_170.exe
md5: 98B7FEDAB5CA4EFCC91AFAA453E63C4D | sha1: D027A8B93D5F08B7E3AEAEEBD73A41B3BCFFBA8C | sha256: 0417041CFFED3478F13A840E45EE304CCF8D1F9CA38E4126BC315161AC9F1669 | sha512: 44E95F14C0222C43E6CE78CFF3F091D675D6A16A8F12F050A89E971CB09E35C014C5C37E5C3313EAA761D4FE1F6B4987B6A66B5673DB9D61FAF5B2878FD05267

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.

Add to Builder Version Downloads Last Updated Status
Open-Shell (Install) 4.4.169-beta 599 Saturday, July 10, 2021 Approved
Open-Shell (Install) 4.4.160 51301 Friday, October 23, 2020 Approved
Open-Shell (Install) 4.4.152 7646 Wednesday, September 9, 2020 Approved
Open-Shell (Install) 4.4.142 15493 Sunday, November 24, 2019 Approved
Open-Shell (Install) 4.4.131 6491 Monday, December 24, 2018 Approved

This package has no dependencies.

Discussion for the Open-Shell (Install) Package

Ground Rules:

  • This discussion is only about Open-Shell (Install) and the Open-Shell (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 Open-Shell (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