Downloads of v 0.70:


Last Update:

30 Dec 2014

Package Maintainer(s):

Software Author(s):

  • Brian Mathis


hotkey key winhotkey


This is not the latest version of WinHotKey available.

0.70 | Updated: 30 Dec 2014



Downloads of v 0.70:



Software Author(s):

  • Brian Mathis

WinHotKey 0.70

This is not the latest version of WinHotKey available.

All Checks are Unknown

2 Test of Unknown Status

Validation Testing Unknown

Verification Testing Unknown

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


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


To uninstall WinHotKey, 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 winhotkey -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 winhotkey -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 winhotkey installed
    name: winhotkey
    state: present
    version: 0.70
    source: STEP 3 URL

See docs at

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

chocolatey_package 'winhotkey' do
  action    :install
  version  '0.70'
  source   'STEP 3 URL'

See docs at

    Name: winhotkey,
    Version: 0.70,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winhotkey
   Name     = 'winhotkey'
   Ensure   = 'Present'
   Version  = '0.70'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winhotkey version="0.70" 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 by moderator purity on 30 Dec 2014.


WinHotKey allows you to assign "hot keys" that do various things. Actions that can be done with a hotkey are:

  • Launch a Program
  • Open a document
  • Open a folder
  • Automatically type something (Sorry, this feature doesn't work on Vista, Windows 7, or later)
  • Control other windows on the screen

The main goal of this tool is to be easy to use. There are many other hotkey programs out there, but most of them do not provide a sufficient level of "ease of use". This walks the user through the options, while remaining a powerful tool.

When running, the program sits in the system tray. Double-clicking on the system tray icon will bring up the main window.

$packageName = 'winhotkey'
$fileType = 'exe'
$url = '' 
Install-ChocolateyPackage $packageName $fileType $silentArgs $url
$packageName = 'winhotkey'
$fileType = 'exe'
$scriptPath = Split-Path -parent $MyInvocation.MyCommand.Definition
$ahkFile = "$scriptPath\killwinhotkey.ahk"

if (Test-Path "${env:programfiles(x86)}\WinHotKey")
    $uninstallerPath = "${env:programfiles(x86)}\WinHotKey\unins000.exe"
	$uninstallerPath = "${env:programfiles}\WinHotKey\unins000.exe"

try {
	Start-Process 'AutoHotkey' $ahkFile
	Uninstall-ChocolateyPackage $packageName $fileType $silentArgs $uninstallerPath
	Write-ChocolateySuccess $packageName
	} catch {
	Write-ChocolateyFailure $packageName $($_.Exception.Message)
; wait for uninstaller to start
sleep 5000
while (true)
	; if uninstaller is running kill everything that has to do with winhotkey. else it opens on its own and waits to be closed.
	Process, Exist, unins000.exe
	IF (!ErrorLevel= 0)
	Process, Close, WinHotKey.exe
	Process, Close, WinHotKeyCfg.exe
	sleep, 1000

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
WinHotKey 0.70 332 Tuesday, December 30, 2014 Approved
Discussion for the WinHotKey Package

Ground Rules:

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