Solved How to kill Ctfmon.exe ?

@TechnoMage2021

I'll bet that if you run sfc /scannow, it'll put that annoyance right back in your face.

Many things I thought I knew and processes that I've done before just didn't want to work with Ctfmon. That crazy file seemed to have a life of it's own. But falling just short of the use of C-4, I got the job done.

Contrary to some things I've read about Ctfmon, killing it did not disable my keyboard, or anything else. All systems are still GO!

TechnoMage2021 said:

Contrary to some things I've read about Ctfmon, killing it did not disable my keyboard, or anything else. All systems are still GO!

Click to expand...

Thank you for the feedback!

A little History with Ctfmon:

As far back as Windows 98, there has been a Ctfmon.exe. And there was the Ctfmon-Remover.
The date on that was 2008, and the last version of Windows it fully supported was Windows Vista.

Since it did not remove Ctfmon in Windows 11, I can only conclude that the program is out of date, and needs a serious RE-Write.

I guess I'll just stop running that old and out of date program, and just remove Ctfmon.exe manually. I now know that I CAN!

It's no big deal, really, but just one more POS that I don't want running in the background on my PC's.

Maybe one of the new Micro versions of Windows 11 will come out minus Ctfmon.exe like so many other pieces of Windows crapola.

pseymour said:

Process Explorer says ctfmon.exe is being run by the "Text Input Management Service," so you'd probably have to disable that service. I am definitely not recommending you do so, just saying that is what is launching it on my 23H2 system.

Click to expand...

Indeed, I used to disable it since XP till some late version, because once disabled, it prevents typing!
In other words, the user can not even log into Windows, being unable to type password and PIN.

I do have that service (Text Input Management Service) on my PC and it's running in Automatic mode, but...
I can not stop it, or change it's operating mode. All of those options are greyed out.

If shutting that down, could be done on earlier versions of Windows, that's been changed.
TM

Also totally not advocating people do this, but you could go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TextInputManagementService, and set the Start value to 4, and reboot. That will disable the service.

I did it on my machine just now, and my keyboard and mouse quit working.

Incredible! I hope you were able to recover from that obvious mistake! Eh?

There is an OLD thread on this same topic, and I just posted the following there, just for consistency:

However, not being one to accept failure lightly, I have devised my own method of disposing of Ctfmon.exe.
Not by Batch File or Script, but by the old Hammer and Chisel method. Hoping a Script will come along later.
I may have actually performed a step or two that was redundant, but....
I went into SAFE mode, took Ownership of the file, "C:\Windows\System32\Ctfmon.exe" and then renamed it to "Ctfmon.xxx". Thus ensuring that it could not load and run the next time the system was booted up.
Then I exited SAFE Mode and rebooted my PC in Normal mode. Then I just went back in, and deleted that now DEAD file.

I've read and heard that doing what I've done will mess up using my keyboard, or logging in.
Well, my keyboard is working just fine, and I NEVER LOG IN. I have no use for that MS BS.!!!

Repeating what I've actually said before, "my computer works for me. I don't work for my computer" (or anyone else)
When I flip the big red Power Switch on the Power Strip, to turn on my PC, within 30 sec's my PC is telling me "You've got mail!".
I don't even have to be sitting at my PC, but I could be getting a cup of coffee. (my Computer works for me!)

Y'all have a great 2024 now, Y'hear?
TM

Well, not a mistake. I was very much aware of what I was doing, and knew how to get out of it. And yes, I'm posting this from that same computer now. So no harm done.

Whew! I'm glad you had a recovery route all planned out.
I have done my own share of mistakes, knowing darn well that I had a fresh Ghost Image of C: in the tank.
Congrats! and ....
Happy New Year!
TM