Downloads of v 0.9.11:


Last Update:

03 Sep 2021

Package Maintainer(s):

Software Author(s):

  • Sam Hocevar


wincompose compose composekey keyboard admin


  • 1
  • 2
  • 3

0.9.11 | Updated: 03 Sep 2021



Downloads of v 0.9.11:



Software Author(s):

  • Sam Hocevar

  • 1
  • 2
  • 3
WinCompose 0.9.11

  • 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 WinCompose, run the following command from the command line or from PowerShell:


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


To uninstall WinCompose, 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 wincompose -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 wincompose -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 wincompose
    name: wincompose
    version: '0.9.11'
    state: present

See docs at

chocolatey_package 'wincompose' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.9.11'

See docs at

cChocoPackageInstaller wincompose
    Name     = "wincompose"
    Version  = "0.9.11"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'wincompose':
  ensure   => '0.9.11',
  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 is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

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


A compose key allows to easily write special characters such as é ž à ō û ø ☺ ¤ ∅ « ♯ ⸘ Ⓚ ㊷ ♪ ♬ using short and often very intuitive key combinations. For instance, ö is obtained using o + ", and ♥ is obtained using < + 3. I wrote WinCompose because I found none of the alternatives (FreeCompose, CKFW, AllChars or Unichars) to be satisfying.

# dummy file for wincompose virtual package

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
WinCompose 0.9.10 539 Friday, June 4, 2021 Approved
WinCompose 0.9.8 305 Tuesday, May 11, 2021 Approved
WinCompose 0.9.7 178 Friday, May 7, 2021 Approved
WinCompose 0.9.6 553 Friday, December 4, 2020 Approved
WinCompose 0.9.5 150 Sunday, November 29, 2020 Approved
WinCompose 0.9.4 873 Saturday, December 7, 2019 Approved
WinCompose 0.9.3 278 Sunday, November 17, 2019 Approved
WinCompose 0.9.1-beta20190805 134 Wednesday, August 7, 2019 Exempted
WinCompose 0.9.1-beta20190405 128 Tuesday, April 9, 2019 Exempted

This is a bugfix release:

fix startup issue with missing System.ValueTuple.dll (#425)
do not write debug messages to the log file (#420)
address an issue where WinCompose may interfer with monitor sleep (#432)
(maybe) fix an issue with the tooltip appearing at random times (#426, #350)
fix erratic behaviour of Scroll Lock key (#321, #421, #393)

Discussion for the WinCompose Package

Ground Rules:

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