Microsoft Text Input Application/Inicio (Start in English) processes

BLaZiNgSPEED said:

Dear @empleat I saw your post process - Windows 10 - how to prevent Microsoft Text Input Application from starting? - Super UserYou mentioned denying all permissions for "InputService" APPID = {730BFCEC-E4BF-4D3A-9FBB-01DD132467A4} in DCOMcnfg.exe

I noticed I get a new error despite using the previous method for debugger. Attachment 349315

How do we get rid of this error? I noticed that when I press Windows+H or use CCleaner to run clean I am met with this. App did not register with DCOM within the required timeout. CCleaner is what basically tries to initiate the Microsoft Text Input causing this error.

This is pretty annoying. I don't know if you or anyone has experienced this. Because while debugger prevents the Input Application from starting. If I use CCleaner then this will trigger with error.

If I try to deny permission for "InputService" APPID = {730BFCEC-E4BF-4D3A-9FBB-01DD132467A4} in DCOMcnfg.exe then it vanishes from the DCOM Config list. I then can go to regedit and add myself as an Administrator again. But this seems to have no effect on getting rid of the error in my screenshot.

Anyone has a solution for this?

I Am not sure, I Am not expert on DCOM it is very esoteric... I gave up on this... You shouldn't change anything in DCOMCONFIG honestly, or in regedit, because you can mess up permissions! Some are not even visible, so I don't know how to know their default state. And while in DCOM, you should be able to reset them globally. But that doesn't affect all registry setting, so write down default settings, before you change anything there! But still it is very weird, MS doesn't want you to have control over this! Even if DCOM is potentially dangerous... But most DCOM errors can be easily ignored, I think 10010 was one of them. Yeah I think you are fine: "app did not register with DCOM within the required timeout" type of errors can be ignored, at least according to what I read. You can google this if you want! Only some DCOM errors are problem!

I Am not sure if you could also hide this error and prevent it from showing, because that is what MS doesn't want you to do, so you don't ignore important errors!

Dear @empleat I have updated Windows 10 from 1903 to 20H2. Unfortunately disabling the TextInputHost.exe using Debugger introduces a new problem that did not occur in 1903.

Basically now this is not only being triggered to always run at system startup. But there is a new problem. Rundll32.exe will start and the screen icons will blink for a couple of seconds of system start up.

I can attest this. Pressing Windows+H to launch the Text Input Application will result in the desktop screen flashing and the icons disappearing for a couple of seconds before they return back!

The culprit is this new Windows 10 20H2 update. I very much regret updating. Biggest mistake I could've possibly made!

Previously the error that I was talking about would only trigger once but now repreatedly pressing Win+H would trigger the error continuously.

I found out that [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{1b562e86-b7aa-4131-badc-b6f3a001407e}]
"Enabled"=dword:00000000
"EnableLevel"=dword:00000000
"LoggerName"="EventLog-System"
"MatchAnyKeyword"=hex(b):00,00,00,00,00,00,00,80
"MatchAllKeyword"=hex(b):00,00,00,00,00,00,00,00
"EnableProperty"=dword:00000001
"Status"=dword:00000000

Changing Enable value to a 0 and these warnings will go away. However, it doesn't solve the problem with the blinking screen at startup!

I undoed the debugger and now TextInputHost.exe is running at startup but doesn't cause screen to flash. We need to find a proper way to disable this. But I honestly don't know how other than going back to older version of Windows 10 and then using Windows Update Blocker to prevent the auto-update to latest version...

- - - Updated - - -

Amazingly enough renaming the folder solves this problem with screen icons flashing at startup!

Basically in 20H2 update using the debugger method results in Rundll32.exe appearing at startup triggering desktop icons to flash on and off and it would randomly occur every time the TextInputHost.exe attempts to launch.

However, on this occasion renaming the folder rectifies this issue and Rundll32.exe does not get triggered on Windows startup and no errors are being triggered either in Event Viewer.

So yes, older version like 1903 you can use debugger method, no problem. But newer version such as 20H2 will mean screen desktop icons will flash. The only real solution right now is to rename this folder quickly after closing the TextInputHost.

I don't know how it was on 1909 as I never used that version. I updated from 1903 to 20H2 for the first time in 2 years.

BLaZiNgSPEED said:

a

Try to rename folder MicrosoftWindows.Client.CBS* instead of using debugger to prevent textinputapp to run.

Screen icons blink for me all the time, I have no idea WTF?

For rundll32.exe check this (some services may need it to run): rundll32.exe - What is it and what should I do about it? - Driver Easy

One needs to be not lazy and backup before updates, but holly shit! I use metered connection and check for updates using minitool, so you can update manually, or even hide some updates! But still I Am lazy and forget, or **** up ... Also check askwoody.com before updating anything. 20H2 is old BTW, maybe you need to update more to solve your issue !

Ah you renamed it...

Problem is windows builts core features into bloatware so you can't turn it off and it may as well interfere with something... I will switch to linux, but that is long time away yet... Windows is garbage and always will be...

After disabling text input application i have thousand of this error in event viewer
The server MicrosoftWindows.Client.CBS_120.2212.4180.0_x64__cw5n1h2txyewy!InputApp did not register with DCOM within the required timeoutit
how can i fix? thanks

djsolidsnake86 said:

After disabling text input application i have thousand of this error in event viewer
The server MicrosoftWindows.Client.CBS_120.2212.4180.0_x64__cw5n1h2txyewy!InputApp did not register with DCOM within the required timeoutit
how can i fix? thanks

As I have mentioned on post #32 20H2 and above, this method for disabling with debugger will trigger these DCOM warnings/errors.

You have to rename the folder or go to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{1b562e86-b7aa-4131-badc-b6f3a001407e}] and change Value to 0.

But the problem like I mentioned is that it still tries to attempt to launch it along with Rundll32.exe.

I returned back to Windows 10 1903 as of December 2021 and used Specify Target 1903 in registry/group policy editor so Windows 10 doesn't automatically upgrade me to latest version of Windows 10. How to Specify Target Feature Update Version in Windows 10
That way I now remain in the older version of Windows 10 and the debugger works fine and doesn't trigger these errors/warnings.

But in newer version of Windows 10 you need to rename the folder instead! That's the problem. This debugger that I posted does not apply for latest version as Microsoft changed the software side of it.

BLaZiNgSPEED said:

As I have mentioned on post #32 20H2 and above, this method for disabling with debugger will trigger these DCOM warnings/errors.

You have to rename the folder or go to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{1b562e86-b7aa-4131-badc-b6f3a001407e}] and change Value to 0.

But the problem like I mentioned is that it still tries to attempt to launch it along with Rundll32.exe.

I returned back to Windows 10 1903 as of December 2021 and used Specify Target 1903 in registry/group policy editor so Windows 10 doesn't automatically upgrade me to latest version of Windows 10. How to Specify Target Feature Update Version in Windows 10
That way I now remain in the older version of Windows 10 and the debugger works fine and doesn't trigger these errors/warnings.

But in newer version of Windows 10 you need to rename the folder instead! That's the problem. This debugger that I posted does not apply for latest version as Microsoft changed the software side of it.

what do you suggest me to do? re enable text input?

djsolidsnake86 said:

what do you suggest me to do? re enable text input?

Rename the folder by going to C:\Windows\SystemApps and rename the InputApp folder to something else. Maybe .Disabled. So that you can undo those changes.

Keep in mind though, with this method if you do SFC/ Scannow Windows will restore a copy of this folder and it will trigger it to start again.

Interestingly enough, from my end with 1903 fully updated to final build. The Microsoft Text Input Application for some reason no longer starts on its own. Of-course I avoid pressing the Start menu button as that's the only trigger I've found to cause this as well as Windows+H.

See if renaming the folder stops the error for your version. If that doesn't work then you can go to RegEdit and search for [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{1b562e86-b7aa-4131-badc-b6f3a001407e}] and change Value to 0.

A combination of these 2 changes should stop the errors/warnings being triggered.

Or alternatively you can freshly reinstall an older version of 1903 or 1909 version of Windows 10 and use Specify Target Release 1903/1909 so Windows 10 remains on this final build without forcefully upgrading to latest version. Then you can use the debugger method and that should take care of the problem.

BLaZiNgSPEED said:

Rename the folder by going to C:\Windows\SystemApps and rename the InputApp folder to something else. Maybe .Disabled. So that you can undo those changes.
there are 6 blue value, all value i must se to 0?
Keep in mind though, with this method if you do SFC/ Scannow Windows will restore a copy of this folder and it will trigger it to start again.

Interestingly enough, from my end with 1903 fully updated to final build. The Microsoft Text Input Application for some reason no longer starts on its own. Of-course I avoid pressing the Start menu button as that's the only trigger I've found to cause this as well as Windows+H.

See if renaming the folder stops the error for your version. If that doesn't work then you can go to RegEdit and search for [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{1b562e86-b7aa-4131-badc-b6f3a001407e}] and change Value to 0.

A combination of these 2 changes should stop the errors/warnings being triggered.

Or alternatively you can freshly reinstall an older version of 1903 or 1909 version of Windows 10 and use Specify Target Release 1903/1909 so Windows 10 remains on this final build without forcefully upgrading to latest version. Then you can use the debugger method and that should take care of the problem.

it worked
but this fix disable the error on the event viewer only or also disable windows that try in background to start that service?

djsolidsnake86 said:

it worked
but this fix disable the error on the event viewer only or also disable windows that try in background to start that service?

If you only renamed the folder and it didn't trigger the errors with [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{1b562e86-b7aa-4131-badc-b6f3a001407e}] Value being 1.

Then it means that Windows is not starting it. You can verify this by seeing if the registry Autologger for 1b562e86-b7aa-4131-badc-b6f3a001407e is set to Value 1 by default.

Then you can press Windows+H and check if it is triggering the errors to show up as normally Windows+H will also attempt to launch Microsoft Text Input Application. You can also check if Windows Error Reporting Service is also being triggered when doing that.

If this worked then most likely that's all that's needed. Windows will no longer try to trigger the service to start.

BLaZiNgSPEED said:

If you only renamed the folder and it didn't trigger the errors with [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{1b562e86-b7aa-4131-badc-b6f3a001407e}] Value being 1.

Then it means that Windows is not starting it. You can verify this by seeing if the registry Autologger for 1b562e86-b7aa-4131-badc-b6f3a001407e is set to Value 1 by default.

Then you can press Windows+H and check if it is triggering the errors to show up as normally Windows+H will also attempt to launch Microsoft Text Input Application. You can also check if Windows Error Reporting Service is also being triggered when doing that.

If this worked then most likely that's all that's needed. Windows will no longer try to trigger the service to start.

with value to 0 if i press win+h i see no errors on the event logs, so it not launch?