Accidentally Deleted ctfmon.exe From System32 Folder

pepanee · 24 Oct 2019

Hello. So I highly believe, a while ago, I deleted the ctfmon.exe from the System32 folder in my Windows 10 x64. So I tried downloading a bunch of different ctfmon.exe files online for Windows 10, yet I see in my Task Manager that ctfmon.exe opens up and closes automatically with a Winerr exe, or such, that shows up and disappears too (this means that it's trying to report an error, most likely that it's the wrong ctfmon).
Whenever I delete the ctfmon from that folder, then no error tries to load or whatnot

So I'm wondering if someone can upload their ctfmon.exe from the System32 folder (with the most recent Windows updates all installed) and help me out a bit?

Bree · 24 Oct 2019

First try Dism /Online /Cleanup-Image /RestoreHealth followed by SFC /ScanNow

Use DISM to Repair Windows 10 Image

Run SFC Command in Windows 10

If that fails to restore ctfmon.exe, then do you have the install media (ISO or USB) for the version of Windows 10 you are running?

Download Windows 10 ISO File

Mount the ISO (or explore the USB) and find the Install.esd in the Sources folder. You can open this with 7-Zip File Manager. Ctfmon.exe can be found in ...\sources\install.esd\1\Windows\System32\

Accidentally Deleted ctfmon.exe From System32 Folder-image.png

pepanee · 24 Oct 2019

Thanks for the reply. So I messed around a bit with things, and I think I accidentally deleted an important system file instead of "unlocking" it temporarily, and now I cannot run cmd.exe from an elevated prompt, not open Task Manager, etc.

I get this error:

Ugh. This is annoying.

FreeBooter · 24 Oct 2019

Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.

Code:

Sfc  /Scannow   /OFFBOOTDIR=D:\   /OFFWINDIR=D:\Windows

Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

pepanee · 24 Oct 2019

Okay, I was able to get everything working back again. I was just a little wary about wanting to avoid doing an "SFC /scannow" command, because, in the past, it had reset some custom system settings that were annoying to set back, but currently I'm not noticing anything different really after doing that command.

I appreciate all the help.