Frequently Asked Questions
You have to use the Unicode Subrange Editor to activate desired Unicode subset(s).
Custom layouts exported as Standalone Layout Installer packages can be deployed without any restrictions, i.e. they don't require a version of KbdEdit to be installed on the target computer. Note however that only Premium edition can generate these packages.
On the other hand, KBE files generated by the Personal or Lite edition require a version of KbdEdit to be installed on the target computer. KbdEdit Player provides a cost-effective solution for "create once, deploy many times" scenarios.
No. 32-bit version of KbdEdit is capable of generating only 32-bit keyboard DLLs. Conversely, 64-bit version generates only 64-bit DLLs. The recommended method for 32/64 bit interoperability is to use KBE files, which are platform-independent.
Yes, KbdEdit and its custom layouts work without problems on Intel Macs running Windows under either Parallels or Boot Camp.
KbdEdit also supports Windows as a guest OS under all major virtualization products (VMWare, VirtualPC etc).
This is usually caused by a conflict between Ctrl+Alt keyboard shortcuts and AltGr mappings, AltGr being simply a shorthand for Ctrl+Alt.
The solution is to replace AltGr with another modifier key which is not so overused, like Kana. See this example for a detailed step-by-step guide.
The popular Mozilla Thunderbird email client has a weird quirk that, even though probably created with the best intentions, ends up being quite annoying:
If an upper-case letter (e.g. Ç) is mapped to an AltGr combination, Thunderbird's editor will produce its lower-case version (ç in this case). All other Windows applications produce the correct letter (i.e. Ç). Thunderbird's "logic" seems to be that since the modifier combination doesn't include Shift, the user probably doesn't want it to produce upper-case letters.
The workaround is to move all upper-case letters from AltGr to AltGr+Shift . You might first have to enable this combination if it is not available in the High-level editor: switch to the Low-level, and move SHIFT + ALTGR from the "Unused modifier combinations" list to "Active modifier combinations".
Thanks to Peter Fairchild for pointing this problem out.
Unfortunately, no. The Fn key is hard-wired on the hardware level to change the function of other keys it impacts. The behavior of this key is not standardized - each laptop model handles it differently. Unlike other "normal" keys, it doesn't produce a scan code visible to Windows, and hence cannot be given a virtual key code (see Low-level editor for an explanation of scan and virtual key codes).
Certain keyboard models have less common or non-standard keys that don't appear in KbdEdit's GUI. These keys cannot be made "current" by clicking on their visual GUI representation, but it still might be possible to remap them.
First, switch to the Low-level editor. Then press the non-standard key on your physical keyboard. If this causes the "Scan code" field to change - congratulations, the key can be remapped, and you have just discovered its scan code.
The key might already have a virtual code assigned, in which case it will be displayed in the "Assigned virtual code" combo; otherwise, the combo will show "VK__none_".
If you want the key to behave as a non-mappable key (see List of Virtual Key Codes), simply choose the desired non-mappable VK code from the "Assigned virtual code" combo (e.g. you can make the key behave as Caps Lock by assigning it VK_CAPITAL).
If you want the key to produce characters, you should first give it an unused mappable virtual key code (VK), again by choosing it from "Assigned virtual code". Choosing the right VK might involve certain amount of hit-and-miss - unlike the standard keys, you cannot use the right-click popup which neatly classifies VKs into mappable / nonmappable, used / free.
After you have assigned an unused mappable VK (e.g. VK_ATTN), switch to the High-level editor. To make the key current, and thus editable, use the "Current key" combo to activate the VK you have just assigned to your non-standard key. It might also be possible to activate it by pressing it on the physical keyboard.
Once the key is made current, you can modify its mappings through the Mappings for the current key zone. E.g. you can edit the mappings using drag-drop, or through the Key mapping editor popup dialog.
The range of 16-bit characters 0000-FFFF is known as the "Basic Multilingual Plane" or BMP. These characters can be directly represented by the UTF-16 encoding KbdEdit uses. Unicode standard also defines 16 other planes with numerical character values ranging from 10000 to 10FFFF. Characters from this range are known as "non-BMP" code points.
Starting with version 1.2.2, non-BMP characters are fully supported by KbdEdit. More precisely, they are supported to the extent the Windows keyboard model supports them - in practice there are some limitations with Caps-Lock mappings and dead characters.
These limitations are caused by the way non-BMP characters are represented internally: since their numeric value is higher than FFFF, they must be stored as two-character ligatures of surrogate pairs. This renders them unusable in the few places where ligatures are not allowed.
For example, non-BMP codepoint 𠀀 20000 ("CJK Unified Ideograph Extension") is internally represented as a ligature of surrogate characters D840 and DC00. For an exact algorithm for calculating surrogate pairs, refer to the UTF-16 Wikipedia page. You can also try this very handy Surrogate Pair Online Calculator.
To properly render non-BMP characters, you will also need a font with good coverage of non-BMP Unicode ranges. We recommend Everson Mono.
The unfortunate fact about Windows keyboard layout file format is that, internally, it is an executable file (DLL) that has to be saved to the Windows System directory (see Administration and Deployment). This tends to trigger an “allergic reaction” in most antivirus programs, which are trained to treat any attempt to create executable files in sensitive system locations as a malware attack. This broad brush tends to taint even "benign" software like KbdEdit, which has a legitimate need for writing DLL files in the System directory.
It is very difficult to create whitelist entries for kbd layout files - each file is different by virtue of hosting a different layout payload, so it is hard if not impossible to create a specific whitelisting “fingerprint”.
As a workaround, if your antivirus software has an option to whitelist specific files, or groups of files, you can create a rule to exclude files matching pattern c:\Windows\system32\KbdEdit*.dll. If your computer runs a 64-bit operating system, you should also add c:\Windows\SysWOW64\KbdEdit*.dll .
You may also need to whitelist KbdEdit's own executable files KbdEdit.exe and KbdEditServer.exe. These files reside in KbdEdit's installation directory, which is by default C:\Program Files (x86)\KbdSoft\KbdEdit <version> <Edition>\ (64-bit OS), or C:\Program Files\KbdSoft\KbdEdit <version> <Edition>\ (32-bit OS).
As an example, for KbdEdit 1.3.4 Premium edition, and default installation directory on a 64-bit system, you should whitelist these two files:
The Sticker Map view enables easy creation of key cap sticker printouts. Occasionally, one may also want to obtain a soft copy as a high-resolution bitmap or, even better, a vector drawing.
KbdEdit does not have a built-in command for exporting sticker maps to a file, but this functionality can be easily achieved using the Microsoft XPS Document Writer virtual printer, which is included with every Windows version since Vista. Instead of paper, this "printer" sends printouts to files in the XPS vector format.
To produce a XPS sticker file, simply click the "Print Sticker Map" button, as you would do when printing stickers on paper. In the "Print" dialog that follows, choose "Microsoft XPS Document Writer" from the dropdown of available printers. This printer will be available even if you don't have any physical printers attached to the computer.
After clicking "OK", the "Save Print Output As" dialog will show up, allowing you to choose the XPS file name.
If you prefer the PDF format, you can choose from any of the numerous third party virtual PDF printer drivers available for Windows.
Major Windows 10 updates, like the Anniversary update from July/August 2016, or the Creator's update from April 2017, tend to reset or overwrite a lot of user-specific OS cusomisations, and custom keyboard layouts are one of the victims.
If you notice that your custom layouts are no longer available after an OS update, first check if the corresponding KbdEdit_*.dll file(s) are still present in the system directory C:\Windows\system32\ (also check C:\Windows\SysWOW64\ if you are running a 64-bit OS version).
Most likely, the files will still be there, and you will be able to re-register them using KbdEdit's Register Layout DLL file command (check "Show only unregistered files" to locate your layout files more easily).
If the files are no longer there, you can try looking for them under C:\$WINDOWS.~BT\ , where the previous Windows installation files have been backed up. Any backed up KbdEdit_*.dll files can be copied back to the System directory, after which they can be registered via the same "Register Layout DLL" command.
Note that, after the original layout files have been restored and re-registered, a system reboot may still be necessary for them to be properly picked up.
To protect against permanent data loss, you should create regular backups of your layouts using the Export KBE file command, especially before attempting a major OS upgrade.
This error is specific to Windows 10, and has been occurring sporadically since roughly the end of 2016.
In all known cases, it is caused by the system process taskhostw.exe , which at random decides to grab a lock on the layout file, preventing any subsequent writes to it.
If you encounter this error, the easiest workaround is to simply kill the offending taskhostw.exe instance:
After this, you should be able to save the changes to your layout.
The taskhostw.exe process will probably respawn itself immediately, but this should be ok - the file was being kept locked by the old instance, which is now gone.
When downloading a KbdEdit MSI installer package, Microsoft's "Internet Explorer" and "Edge" web browsers often report the following error:
"The signature of KbdEditSetup_<version_details>.msi is corrupt or invalid."
This error is harmless, and can be safely ignored. The download links received via purchase confirmation emails are guaranteed to lead to clean, valid KbdEdit installers.
If you are bothered by the error, you can easily avoid it by using a non-Microsoft web browser, such as Google Chrome or Mozilla Firefox.
Copyright © KbdSoft 2007-2017