Downloads:
2,865
Downloads of v 0.70.0.1:
2,043
Last Update:
22 Aug 2016
Package Maintainer(s):
Software Author(s):
- Brian Mathis
Tags:
hotkey key winhotkey- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
WinHotKey
- 1
- 2
- 3
0.70.0.1 | Updated: 22 Aug 2016
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
2,865
Downloads of v 0.70.0.1:
2,043
Maintainer(s):
Software Author(s):
- Brian Mathis
WinHotKey 0.70.0.1
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Brian Mathis. The inclusion of Brian Mathis trademark(s), if any, upon this webpage is solely to identify Brian Mathis goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Passed
Verification Testing Passed
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
Deployment Method: Individual Install, Upgrade, & Uninstall
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:
Deployment Method:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download winhotkey --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade winhotkey -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 winhotkey -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 winhotkey
win_chocolatey:
name: winhotkey
version: '0.70.0.1'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'winhotkey' do
action :install
source 'INTERNAL REPO URL'
version '0.70.0.1'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller winhotkey
{
Name = "winhotkey"
Version = "0.70.0.1"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'winhotkey':
ensure => '0.70.0.1',
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.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved by moderator gep13 on 02 Sep 2016.
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'
$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART'
$scriptPath = Split-Path -parent $MyInvocation.MyCommand.Definition
$ahkFile = "$scriptPath\killwinhotkey.ahk"
$registryPath32 = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinHotKey_is1'
$registryPathWow6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\WinHotKey_is1'
if (Test-Path $registryPath32) {
$registryPath = $registryPath32
}
if (Test-Path $registryPathWow6432) {
$registryPath = $registryPathWow6432
}
if ($registryPath) {
$uninstallString = (Get-ItemProperty -Path $registryPath -Name 'UninstallString').UninstallString
}
if ($uninstallString) {
Start-Process 'AutoHotkey' $ahkFile
Uninstall-ChocolateyPackage $packageName $fileType $silentArgs $uninstallString
}
; 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
}
else
{
return
}
}
Log in or click on link to see number of positives.
- WinHotKey0.70.exe (0db56e24fbb0) - ## / 54
- winhotkey.0.70.0.1.nupkg (648eebd25103) - ## / 54
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 |
---|---|---|---|---|
WinHotKey 0.70.0.1 | 2043 | Monday, August 22, 2016 | Approved | |
WinHotKey 0.70 | 538 | Tuesday, December 30, 2014 | Approved |
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.