How to delete a custom keyboard layout in Windows?

do you still have the .msi? Perhaps you can run it with msiexec /u? Or re-install it again?

Basically, it should be impossible that a .msi does not create an uninstall entry (and will not be rolled back when you try to install any other .msi). If you removed the uninstall entry manually, you can still uninstall it via msiexec /u, but you will need to find the installer GUID for that (which can be hard to find if you have a lot of stuff installed...)

If that fails: The entries themselves are in the registry at HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Keyboard Layouts, so you can at least remove the entry for your layout (if not uninstall the .dll and stuff).

I have done the exact same thing once, if you can't uninstall with the msi follow this:

1. Note the same of the .dll you installed with the msi
2. Search it on the local drive and delete the occurrence in sys32
3. Open the registry editor and go to HKLM\System\CurrentControlSet\Control\Keyboard Layouts
4. Browse all the sub-folders until you find the one that reference your custom dll
5. Delete the sub-folder
6. Reboot the machine

After that you're clean, you can reinstall the updated version of your layout with the same dll name without any conflicting issues.

Gotcha.

That'd be a registry key under HKLM\System\CurrentControlSet\Control\Keyboard Layouts.

Since it is a custom layout, you'll have to go through all subfolders to find it.

Note: Prudence demands to create a backup (right click > export) before you delete the folder from the registry. :)

Go to the setup directory ((Drive):\Users\(Username)\Documents\(Layout Name (like US-PS))\setup.exe): Open the setup. It'll have 2 options,just select the first one ("Remove Keyboard Layout"),wait until it's uninstalled and you'll have it removed. I just did that.

I believe I know why this happened. The creator makes some .msis for various architectures and a setup.exe. If you run one of these .msis directly, no uninstaller is made. You should use the setup.exe created instead.

The easy solution is as mihi says: run the .msi with the /uninstall flag.