Downloads of v 3.31:


Last Update:

19 Sep 2021

Package Maintainer(s):

Software Author(s):

  • MikroTik


winbox mikrotik network router routeros administration management


  • 1
  • 2
  • 3

3.31 | Updated: 19 Sep 2021



Downloads of v 3.31:



Software Author(s):

  • MikroTik

  • 1
  • 2
  • 3
WinBox 3.31

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged as a Note:

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


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


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


To uninstall WinBox, 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 winbox -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 winbox -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 winbox installed
    name: winbox
    state: present
    version: 3.31
    source: STEP 3 URL

See docs at

chocolatey_package 'winbox' do
  action    :install
  version  '3.31'
  source   'STEP 3 URL'

See docs at

    Name: winbox,
    Version: 3.31,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winbox
   Name     = 'winbox'
   Ensure   = 'Present'
   Version  = '3.31'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winbox version="3.31" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 19 Sep 2021.


WinBox is a small utility that allows administration of Mikrotik RouterOS using a fast and simple GUI. It is a native Win32 binary, but can be run on Linux and Mac OSX using Wine.

All WinBox interface functions are as close as possible to Console functions. Some of advanced and system critical configurations are not possible from WinBox, like MAC address change on an interface.

Note: WinBox is obviously freeware, but no details about the license are available either on the application website or in the application itself.

$packageName = 'winbox'
$appName = 'WinBox'
$url32 = ''
$url64 = ''
$dir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$is64 = ((Get-ProcessorBits 64) -and !$env:chocolateyForceX86)
$processName32 = 'winbox'
$processName64 = 'winbox64'
$processName = If ($is64) { $processName64 } Else { $processName32 }
$exe = $processName + '.exe'
$fullPath = Join-Path -Path $dir -ChildPath $exe
$checksum32 = '2b4ff7898213b7038e732f149c08c01fc88092b85e150aefe2c70bde48504073e3205b03bd90eb2f1d4c49f6487af90e424d2dc247e7c0a39dc9881a6a718ce1'
$checksum64 = 'b39d64e442d813fb88051ca487771701b8e8e4c2f48c4b50fc7c9ee54ac2b710a64829fbce9c6f6bd6acca55eea7b323f54612f81156e2da0df83018de8423ee'
$checksumType = 'sha512'

$startFolder = $appName

Function CreateStartMenuShortcut {
    $startMenuFolderPath = Join-Path -Path ([Environment]::GetFolderPath('Programs')) `
        -ChildPath $startFolder
    New-Item $startMenuFolderPath -Type Directory -ErrorAction SilentlyContinue
    If (Test-Path -Path $startMenuFolderPath -PathType Container) {
            Install-ChocolateyShortcut -shortcutFilePath `
                (Join-Path -Path $startMenuFolderPath -ChildPath ($appName + '.lnk')) `
                -targetPath $fullPath -workingDirectory $dir
    } Else {
        Write-Warning "Start menu folder couldn't be created."


Stop-Process -Name $processName32 -ErrorAction SilentlyContinue
Stop-Process -Name $processName64 -ErrorAction SilentlyContinue

# Workaround for
Remove-Item -Path $fullPath -Force -Confirm:$FALSE -ErrorAction SilentlyContinue

Get-ChocolateyWebFile -PackageName $packageName -FileFullPath $fullPath -Url $url32 -Url64bit $url64 -Checksum $checksum32 -ChecksumType $checksumType -Checksum64 $checksum64 -ChecksumType64 $ChecksumType

# create .gui file
New-Item -Path $dir -Name ($exe + '.gui') -ItemType file


$startFolder = 'WinBox'
$processName32 = 'winbox'
$processName64 = 'winbox64'

Function RemoveStartMenuShortcut {
    $startMenuFolderPath = Join-Path -Path ([Environment]::GetFolderPath('Programs')) `
        -ChildPath $startFolder
    Remove-Item $startMenuFolderPath -Recurse -Force -Confirm:$FALSE -ErrorAction SilentlyContinue


Stop-Process -Name $processName32 -ErrorAction SilentlyContinue
Stop-Process -Name $processName64 -ErrorAction SilentlyContinue


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
WinBox 3.30 1719 Sunday, September 12, 2021 Approved
WinBox 3.29 6303 Monday, August 23, 2021 Approved
WinBox 3.28 13872 Wednesday, June 9, 2021 Approved
WinBox 3.27 34671 Saturday, September 12, 2020 Approved
WinBox 3.24 10875 Monday, May 18, 2020 Approved
WinBox 3.23 987 Sunday, April 19, 2020 Approved
WinBox 3.22 1387 Sunday, March 15, 2020 Approved
WinBox 3.21 1108 Sunday, February 9, 2020 Approved
WinBox 3.20 10914 Saturday, October 19, 2019 Approved

This package has no dependencies.

Discussion for the WinBox Package

Ground Rules:

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