# What Is ctfmon.exe and Why Does CTF Loader Keep Running

ctfmon.exe is the file behind **CTF Loader** in Task Manager. It belongs to the Text Services Framework, the part of Windows that connects keyboard layouts, input methods, handwriting and speech input to the apps you type in, and it keeps running while you are signed in. A `ctfmon.exe` in `C:\Windows\System32`, or its 32-bit twin in `C:\Windows\SysWOW64`, with a valid Microsoft signature is Windows' own file, not malware, and not something to delete. If it uses CPU for a long time, look at the input methods and text services it manages before you turn anything off.

## What CTF Loader does

Microsoft's Text Services Framework (TSF) documentation describes the job in one sentence: [the ctfmon.exe process](https://learn.microsoft.com/en-us/windows/win32/tsf/64-bit-platform-considerations) "manages the Text Services Framework on the desktop and also provides the language bar user interface". Chinese, Japanese and Korean input methods, extra keyboard layouts, handwriting and dictation are all text services, and the same page explains that a text service is a COM object in a DLL. The code of an input method therefore runs inside the app you are typing in, while ctfmon.exe keeps track of which services are installed and which one is active.

The same page also explains why there can be two of them. On 64-bit Windows, "a 32-bit version and a 64-bit version of the ctfmon.exe process run simultaneously", each managing the text services built for its own bitness. So if you see a second CTF Loader row marked 32-bit, it is expected and does not mean another program is hiding under the name; many PCs show only one. A [Microsoft Q&A thread](https://learn.microsoft.com/en-us/answers/a/3572142) from a 64-bit PC found the 32-bit copy in `C:\Windows\SysWOW64`, the folder where 64-bit Windows keeps its 32-bit system files. On a Windows 11 test PC (build 26200), only the copy from `C:\Windows\System32` was running, and the 32-bit file sat unused in `C:\Windows\SysWOW64`.

## Check that it is the real file

1. Open Task Manager with `Ctrl + Shift + Esc` and go to **Details**.
2. Right-click `ctfmon.exe` and choose **Open file location**. Windows' own copy is in `C:\Windows\System32`, and a 32-bit copy is in `C:\Windows\SysWOW64`.
3. Or read the path and the signature from PowerShell:

```powershell
Get-Process ctfmon | ForEach-Object { Get-AuthenticodeSignature $_.Path } | Select-Object Path, Status, SignerCertificate
```

A `Valid` status with a Microsoft certificate settles it. A `ctfmon.exe` running from your user folder, `AppData`, `Temp` or anywhere outside the Windows folder is a different program borrowing the name, and that one deserves a full scan with Windows Security.

## When it uses CPU

| You see | Likely cause | Try |
| --- | --- | --- |
| One or two CTF Loader rows, near zero CPU | Normal, one copy per bitness | Nothing |
| CPU rises while you type in one app | That app and the text service loaded into it | Switch to another input method in that app, update the app |
| Steady CPU since you installed a keyboard tool or input method | The new input method or its helper | Remove it, then test for a day |
| `ctfmon.exe` outside `C:\Windows` | Not the Windows file | Scan with Windows Security |

Because a text service runs inside the app, the useful test is to take the text service out of the picture. Hold the Windows logo key and press `Space` to cycle through the installed keyboard layouts and move to Microsoft's own, then keep working. If CTF Loader calms down, the input method you left is the cause, and its update or removal is the fix.

To remove one on Windows 11, Microsoft's [language settings guide](https://support.microsoft.com/en-us/windows/manage-the-input-and-display-language-settings-in-windows-12a10cb4-8626-9b77-0ccb-5013e0c7c7a2) gives the path: Start › Settings › Time & language › Language & region, select the ellipsis next to the language, choose Language options, then under Keyboards select the ellipsis next to the keyboard and choose Remove. A third-party input method installed as an app also needs to be uninstalled from the apps list, or its own files stay behind.

## The touch keyboard service

Many guides say to disable the **Touch Keyboard and Handwriting Panel Service** to stop CTF Loader. Microsoft's [service guidelines for Windows Server 2016](https://learn.microsoft.com/en-us/windows-server/security/windows-services/security-guidelines-for-disabling-system-services-in-windows-server) describe this service, `TabletInputService`, as one that "enables Touch Keyboard and Handwriting Panel pen and ink functionality", list its startup type as Manual, and recommend "Do not disable" when the desktop experience is installed. That guide is written for Windows Server, but the description tells you what you give up on a PC: the on-screen touch keyboard and pen handwriting.

Do not follow that advice. Microsoft's [IME troubleshooting article](https://learn.microsoft.com/en-us/troubleshoot/windows-client/shell-experience/troubleshoot-ime-common-issues) says the same service has been called **Text Input Management Service** (`TextInputManagementService`) since Windows 11 25H2, and that when it is disabled, "Ctfmon.exe can't start", the input method framework does not load and you cannot switch input methods. On a Windows 11 test PC (build 26200) only the new name exists, running and set to Automatic. To see which name your PC uses:

```powershell
Get-Service TabletInputService, TextInputManagementService -ErrorAction SilentlyContinue | Select-Object Name, DisplayName, Status, StartType
```

Whichever name it has, leave it at its default. Turning it off does stop CTF Loader, and with it Chinese, Japanese and Korean input methods and the Windows logo key + Spacebar layout switch. If you already disabled it following an older guide and typing broke, Microsoft's fix is to open `services.msc`, set its startup type back to Manual or Automatic, start it, then sign out and back in.

## What not to do

- Do not delete `ctfmon.exe` or take ownership of it. It is a Windows file that input methods and the language bar depend on.
- Do not keep ending it in Task Manager. That does not remove the input method that made it busy.
- Do not trust a "ctfmon fix" download. The repair for a damaged Windows file is Windows' own DISM and System File Checker, see [what to do when Windows Explorer is not responding](/windows/blog/windows-explorer-not-responding) for the commands.

## Where Mole fits

Mole for Windows' **Status** page lists CTF Loader like any other process, with its CPU, memory and I/O. Choosing **Why is this running?** from the row's menu shows the program file and the process that started it, which is a quick way to confirm the path. Because it runs from the Windows folder, Mole marks the row **System** and offers no **Terminate** or **Force Quit** for it. Mole does not manage input methods, keyboard layouts or the touch keyboard service, so those changes stay in Settings. For other names in Task Manager, see [Windows processes explained](/windows/blog/windows-processes-explained) and [High CPU usage on Windows](/windows/blog/windows-high-cpu-usage).

## FAQ

### Is ctfmon.exe a virus?

Not when it runs from `C:\Windows\System32` or `C:\Windows\SysWOW64` and its signature is valid and from Microsoft. A file with that name in any other folder should be scanned with Windows Security.

### Can I disable CTF Loader?

There is no supported switch for ctfmon.exe itself, and input methods, handwriting and the language bar depend on it. Remove the input method that makes it busy instead.

### Why are there two CTF Loader processes?

On 64-bit Windows a 32-bit and a 64-bit copy can run at the same time, each managing text services of its own bitness. Microsoft documents this in its TSF developer notes.

### Does disabling the touch keyboard service stop ctfmon.exe?

It does, and that is the problem. Microsoft says that when this service, named Text Input Management Service since Windows 11 25H2, is disabled, ctfmon.exe can't start and you cannot switch input methods. Leave it at its default and remove the input method that keeps CTF Loader busy instead.


Canonical: https://mole.fit/windows/blog/ctfmon-exe-windows
