Downloads of v


Last Update:

05 Apr 2018

Package Maintainer(s):

Software Author(s):

  • Ivo Beltchev


classic-shell shell freeware start-menu admin

Classic Shell

  • 1
  • 2
  • 3 | Updated: 05 Apr 2018



Downloads of v


Software Author(s):

  • Ivo Beltchev

  • 1
  • 2
  • 3
Classic Shell

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


To uninstall Classic Shell, 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

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 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 classic-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 classic-shell -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install classic-shell
    name: classic-shell
    version: ''
    state: present

See docs at

chocolatey_package 'classic-shell' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller classic-shell
    Name     = "classic-shell"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

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 12 Jul 2020.


Classic Shell is a collection of usability enhancements for Windows. The main features are:


  • Highly customizable start menu with multiple styles and skins
  • Quick access to recent, frequently-used, or pinned programs
  • Find programs, settings, files and documents
  • Start button for Windows 7, Windows 8, Windows 8.1 and Windows 10
  • Toolbar and status bar for Windows Explorer
  • Caption and status bar for Internet Explorer


  • If you want to install only specific components, e.g. only the Start Menu, use
    choco install classic-shell -installArgs ADDLOCAL=ClassicStartMenu. If Classic Shell gets updated, you won't have to specify the -installArgs again. It remembers your previous selection and will only install the component you have specified. To look for other possible installer arguments, go to

You are permitted to distribute the Classic Shell installer or offer it for download on your website, as long as:
You do it free of charge
You don't misrepresent the origin of the software
You don't modify the software in any way
Wrapping Classic Shell in a secondary installer or bundling with other software is not allowed
The Classic Shell name and logo are trademarks and cannot be used to identify other products or services.

* "Commercial use" means you can use it in a commercial environment - your office, school, etc. It does not mean you can sell the software.
If you are operating a computer shop it is permitted to install Classic Shell for your customers as long as you do it free of charge. If you do this on a large scale a donation is encouraged.
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <>
and can be verified by doing the following:

1. Download the following <>
2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:

  checksum type: sha256
  checksum: 8BBD850FD8A2B41D090FBF8E005F9A5A76C774ACA643318A8A34254F99F79ED8

The file 'LICENSE.txt' has been obtained from <>
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path -parent $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  fileType       = 'exe'
  file           = "$toolsPath\ClassicShellSetup_4_3_1.exe"
  softwareName   = 'classic-shell*'
  silentArgs     = '/passive'
  validExitCodes = @(0)

Install-ChocolateyInstallPackage @packageArgs

Get-ChildItem $toolsPath\*.exe | ForEach-Object { Remove-Item $_ -ea 0; if (Test-Path $_) { Set-Content "$_.ignore" } }
md5: 4C566D866483669EB44584E6E0339292 | sha1: 3C02AD8DB1B5EE6BC085588B89E8845C53387B15 | sha256: 8BBD850FD8A2B41D090FBF8E005F9A5A76C774ACA643318A8A34254F99F79ED8 | sha512: E973BFFC16C54667729FCBCBE02B3A5615E895787218681224E90EE62BE761148E203848DF43A4A280E8AEB1D4DDE43F29CA917748874012AA57E6DB1FB62583

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
Classic Shell 4.3.1 23328 Wednesday, August 16, 2017 Approved
Classic Shell 4.3.0 30565 Saturday, October 8, 2016 Approved
Classic Shell 66669 Saturday, May 21, 2016 Approved
Classic Shell 4.2.5 8833 Saturday, November 14, 2015 Approved
Classic Shell 4.2.4 4910 Monday, August 10, 2015 Approved
Classic Shell 4.2.1 9437 Saturday, April 11, 2015 Approved
Classic Shell 4262 Saturday, December 27, 2014 Approved
Classic Shell 2302 Thursday, October 2, 2014 Unknown
Classic Shell 1892 Tuesday, June 24, 2014 Unknown

This package has no dependencies.

Discussion for the Classic Shell Package

Ground Rules:

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