RemoteApp crashing on Windows Server 2025 with Windows 11/10

Question

RemoteApp crashing on Windows Server 2025 with Windows 11/10

Marcelo Gomes 20

Hi!

I'm currently having some troubles with the following scenario:

SRRDS01 - Connection Broker, WebAccess, SessionHost, Licensing

SRRDS02 - SessionHost

This two servers have a RemoteApp collection where both are session hosts.

Some users are reporting that the RemoteApps are crashing. When this happens, on the client computer I can see the event below.

Faulting application name: mstsc.exe, version: 10.0.26100.4202, time stamp: 0x8ee6b89b

Faulting module name: TextInputMethodFormatter.dll, version: 10.0.26100.4202, time stamp: 0xc4f09ed9

Exception code: 0xc0000005

Fault offset: 0x0000000000031fb9

Faulting process id: 0x64C8

Faulting application start time: 0x1DBDBA1ECE5D1AC

Faulting application path: C:\Windows\System32\mstsc.exe

Faulting module path: C:\Windows\System32\TextInputMethodFormatter.dll

Report Id: 94d54dec-6084-4e6a-a7dc-7dc32716afc2

Faulting package full name:

Faulting package-relative application ID:

On the server, I can see the following events:

ProviderName: Microsoft-Windows-TerminalServices-LocalSessionManager

TimeCreated Id LevelDisplayName Message

12/06/2025 15:00:54 40 Information Session 22 has been disconnected, reason code 2147942464

12/06/2025 14:18:57 40 Information Session 21 has been disconnected, reason code 2147942464

12/06/2025 12:29:42 40 Information Session 18 has been disconnected, reason code 2147942521

12/06/2025 11:38:42 40 Information Session 18 has been disconnected, reason code 2147942464

12/06/2025 11:31:25 40 Information Session 13 has been disconnected, reason code 2147942464

12/06/2025 11:25:46 40 Information Session 12 has been disconnected, reason code 2147942464

12/06/2025 11:25:41 40 Information Session 16 has been disconnected, reason code 2147942521

12/06/2025 10:15:04 40 Information Session 15 has been disconnected, reason code 2147942464

12/06/2025 08:37:52 40 Information Session 10 has been disconnected, reason code 2147942464

I have tried disable UDP on the client but that didn't make any difference.

Does anybody has had this problem before?

Dennis | Digisens 20 Reputation points

2025-06-16T14:42:09.1433333+00:00

I'm breaking my head over this one too for the pas two weeks!

New deployment

Windows 10 machines do not have this problem
Windows 11 machines crashes randomly.
Kaeden 0 Reputation points

2025-06-18T13:29:04.4033333+00:00

We are having this same issue, any solutions to it yet?
Dennis | Digisens 20 Reputation points

2025-06-18T14:19:04.0766667+00:00
Sadly not, i tried every workarround.

Troubleshooting & Mitigation Steps Tried:

Switched to MSRDC (Remote Desktop Client): Tried publishing via webfeed and .rdp — but MSRDC doesn’t work with internal RDS (only with Azure/Remote Desktop Services feed).

Tuned RDP File Settings:

Disabled multimonitor, animations, and bitmap cache

Disabled cursor and full window drag

Enabled smart sizing

Removed all unnecessary device redirections

Disabled legacy features where possible

Disabled Clipboard

Group Policy Audit: Checked and disabled policies that could interfere with RDP (keyboard hooks, input method editors, clipboard redirection, etc.)

Server-Side Fixes:

Verified RDS configuration and feed URL

Ensured .NET and IIS roles were properly installed

Confirmed updated Webfeed.aspx behavior

Analyzed server event logs for disconnect reasons (Reason code: 5 / 2147942464)

Client Analysis:

Issue occurs only on Windows 11 (not on Windows 10)

Tried stable and Insider builds

Reviewed WER logs pointing to TextInputMethodFormatter.dll

Windows Update KB5060842 Installed:

This update modifies Input Services and TextInputMethodFormatter.dll

However, issue persists post-update

Hardware/Network Checks:

Verified NIC offloading, MTU settings

Optimized for small packet handling

No bandwidth drops or latency during session drop

Tried Turning off UDP

Server-side logs (TerminalServices-LocalSessionManager):

Event ID 40 with reason codes like 2147942464 (ERROR_NETNAME_DELETED) — the server detects that the client suddenly disappeared (typical of a crash).

Crash only occurs with RemoteApp on Windows 11. Full RDP desktops or RemoteApp on Windows 10 do not crash.

Still looking for a stable resolution. Would appreciate any insights, especially if others have encountered mstsc.exe crashing via RemoteApp on Windows 11.
Marcelo Gomes 20 Reputation points

2025-06-18T15:44:10.85+00:00

Hi Dennis,

I have open a case with Microsoft regarding this issue, I will let you know if they figure it out.

I did tried everything you said and still got the same issue.

Do you have events with the reason code 2147942521 too?

My servers are in EN-US and my clients are in PT-PT, don't know if this can be related.
Dennis | Digisens 20 Reputation points

2025-06-18T16:15:10.19+00:00

Hey Marcelo,

I indeed have the same reason code too!,
There servers on my customer side are (terminal server en-US with nl-NL packs installed)
The clients are nl-NL.

Thanks for the info that you have an case at Microsoft, we have like 40+ People working with it everyday and they get a little frustrated now haha.
Dennis | Digisens 20 Reputation points

2025-06-24T11:39:05.14+00:00

Hey there Marcelo, is there any feedback from microsoft yet ? :) Hope to hear from you!
Marcelo Gomes 20 Reputation points

2025-06-24T13:55:47.5866667+00:00

Hi Dennis!

No news yet. The support has collected the logs from my machine and the server but they are still analyzing them.

I will let you know when they report back. I have escalated the issue as well.
Kaeden 0 Reputation points

2025-06-27T11:23:17.8266667+00:00

Hey guys, we updated a few users yesterday to KB5060842 and none of them crashed. This may not be the fix yet and could be coincidence however they were usually crashing 4-5 times per day so its looking promising. I can report back if they do continue to crash.
Dennis | Digisens 0 Reputation points

2025-06-27T11:49:18.66+00:00

Hey Kaeden,

As I mentioned in my previous comment, unfortunately this didn’t solve the issue for us. That said, it’s good to hear you’re seeing some progress on your end.

Since this doesn’t appear to be a widespread problem, I suspect it might be related to our keyboard input methods or language/driver configurations.
NZKiwiTech 0 Reputation points

2025-06-27T11:53:09.4366667+00:00

I have also been chasing the solution to this since Server 2025 released.
None of the W11 versions of TextInputMethodFormatter.dll all the way up to 10.0.26100.4202 have had any real difference for me so far.

I was able to confirm the crashes stop when replacing the DLL with the Windows 10 22H2 version.
The problem with this is it causes CTFMon.exe on the local machine to crash constantly, and this in turn causes input lag as it crashes and restarts.

I also see the odd crash for mstsc.exe in ntdll.dll as well.
Kaeden 0 Reputation points

2025-07-01T11:57:15.3366667+00:00

Yeah, unfortunately our windows update didn't seem to fix the issue, just must have been a good day. We also opened a ticket with Microsoft and have sent them our logs.
Kaeden 0 Reputation points

2025-07-07T12:41:28.94+00:00
We have heard back from Microsoft, they did recognize it as a bug:

"I hope this message finds you well,

I’m writing to provide an update regarding the ongoing case. Based on our investigation, the issue appears to be related to Bug 57816984, which affects the RailTest.dll component and results in the exception 800706BE.

Microsoft is aware of the issue and is actively working on a fix. The current plan is to include the fix in the August patch. However, it’s important to note that the rollout of this update will be gradual, and it may take up to three additional months for the fix to reach all customers.

With that in mind, we’d like to align expectations as follows:

The fix is under development and will be released once all necessary testing is completed.

While the August patch may contain the fix, there is no guarantee that it will be immediately available to all environments.

A more realistic timeline for broad availability is +3 months after the initial release.

We are closely monitoring the progress with the engineering team and will keep you informed of any significant updates."
Bryan Fulkersin 0 Reputation points

2025-07-08T11:36:51.3433333+00:00

Is there a publication or other source of information regarding Bug 57816984? Interested in learning more about Bug 57816984 and how it would affect UDP transport of RDP/RDS traffic, causing it to hang, freeze, lock up or otherwise crash.
NZKiwiTech 0 Reputation points

2025-07-09T22:21:35.98+00:00

I'm aware it's not August or 3 months after yet but confirming the latest DLL version I have seen, 10.0.26100.4484 is still having the same issue.
Dennis | Digisens 0 Reputation points

2025-07-11T09:27:05.66+00:00

Hi Kaeden, In the post you made you state (Microsoft) that RailTest.dll components are related. How did they find this? Because in my log files i do not see this .dll back. i just want to check if it is indeed the exact same problem as that we experience. @marcelo gomes Do you have any updates from microsoft, that mayby link these problems to eachother?

1 answer

Your answer

Dennis | Digisens 20 Reputation points

2025-06-16T14:42:09.1433333+00:00

I'm breaking my head over this one too for the pas two weeks!

New deployment

Windows 10 machines do not have this problem
Windows 11 machines crashes randomly.
Kaeden 0 Reputation points

2025-06-18T13:29:04.4033333+00:00

We are having this same issue, any solutions to it yet?
Dennis | Digisens 20 Reputation points

2025-06-18T14:19:04.0766667+00:00

Sadly not, i tried every workarround.

Troubleshooting & Mitigation Steps Tried:

Switched to MSRDC (Remote Desktop Client): Tried publishing via webfeed and .rdp — but MSRDC doesn’t work with internal RDS (only with Azure/Remote Desktop Services feed).

Tuned RDP File Settings:

Disabled multimonitor, animations, and bitmap cache

Disabled cursor and full window drag

Enabled smart sizing

Removed all unnecessary device redirections

Disabled legacy features where possible

Disabled Clipboard

Group Policy Audit: Checked and disabled policies that could interfere with RDP (keyboard hooks, input method editors, clipboard redirection, etc.)

Server-Side Fixes:

Verified RDS configuration and feed URL

Ensured .NET and IIS roles were properly installed

Confirmed updated Webfeed.aspx behavior

Analyzed server event logs for disconnect reasons (Reason code: 5 / 2147942464)

Client Analysis:

Issue occurs only on Windows 11 (not on Windows 10)

Tried stable and Insider builds

Reviewed WER logs pointing to TextInputMethodFormatter.dll

Windows Update KB5060842 Installed:

This update modifies Input Services and TextInputMethodFormatter.dll

However, issue persists post-update

Hardware/Network Checks:

Verified NIC offloading, MTU settings

Optimized for small packet handling

No bandwidth drops or latency during session drop

Tried Turning off UDP

Server-side logs (TerminalServices-LocalSessionManager):

Event ID 40 with reason codes like 2147942464 (ERROR_NETNAME_DELETED) — the server detects that the client suddenly disappeared (typical of a crash).

Crash only occurs with RemoteApp on Windows 11. Full RDP desktops or RemoteApp on Windows 10 do not crash.

Still looking for a stable resolution. Would appreciate any insights, especially if others have encountered mstsc.exe crashing via RemoteApp on Windows 11.
Marcelo Gomes 20 Reputation points

2025-06-18T15:44:10.85+00:00

Hi Dennis,

I have open a case with Microsoft regarding this issue, I will let you know if they figure it out.

I did tried everything you said and still got the same issue.

Do you have events with the reason code 2147942521 too?

My servers are in EN-US and my clients are in PT-PT, don't know if this can be related.
Dennis | Digisens 20 Reputation points

2025-06-18T16:15:10.19+00:00

Hey Marcelo,

I indeed have the same reason code too!,
There servers on my customer side are (terminal server en-US with nl-NL packs installed)
The clients are nl-NL.

Thanks for the info that you have an case at Microsoft, we have like 40+ People working with it everyday and they get a little frustrated now haha.
Dennis | Digisens 20 Reputation points

2025-06-24T11:39:05.14+00:00

Hey there Marcelo, is there any feedback from microsoft yet ? :) Hope to hear from you!
Marcelo Gomes 20 Reputation points

2025-06-24T13:55:47.5866667+00:00

Hi Dennis!

No news yet. The support has collected the logs from my machine and the server but they are still analyzing them.

I will let you know when they report back. I have escalated the issue as well.
Kaeden 0 Reputation points

2025-06-27T11:23:17.8266667+00:00

Hey guys, we updated a few users yesterday to KB5060842 and none of them crashed. This may not be the fix yet and could be coincidence however they were usually crashing 4-5 times per day so its looking promising. I can report back if they do continue to crash.
Dennis | Digisens 0 Reputation points

2025-06-27T11:49:18.66+00:00

Hey Kaeden,

As I mentioned in my previous comment, unfortunately this didn’t solve the issue for us. That said, it’s good to hear you’re seeing some progress on your end.

Since this doesn’t appear to be a widespread problem, I suspect it might be related to our keyboard input methods or language/driver configurations.
NZKiwiTech 0 Reputation points

2025-06-27T11:53:09.4366667+00:00

I have also been chasing the solution to this since Server 2025 released.
None of the W11 versions of TextInputMethodFormatter.dll all the way up to 10.0.26100.4202 have had any real difference for me so far.

I was able to confirm the crashes stop when replacing the DLL with the Windows 10 22H2 version.
The problem with this is it causes CTFMon.exe on the local machine to crash constantly, and this in turn causes input lag as it crashes and restarts.

I also see the odd crash for mstsc.exe in ntdll.dll as well.
Kaeden 0 Reputation points

2025-07-01T11:57:15.3366667+00:00

Yeah, unfortunately our windows update didn't seem to fix the issue, just must have been a good day. We also opened a ticket with Microsoft and have sent them our logs.
Kaeden 0 Reputation points

2025-07-07T12:41:28.94+00:00

We have heard back from Microsoft, they did recognize it as a bug:

"I hope this message finds you well,

I’m writing to provide an update regarding the ongoing case. Based on our investigation, the issue appears to be related to Bug 57816984, which affects the RailTest.dll component and results in the exception 800706BE.

Microsoft is aware of the issue and is actively working on a fix. The current plan is to include the fix in the August patch. However, it’s important to note that the rollout of this update will be gradual, and it may take up to three additional months for the fix to reach all customers.

With that in mind, we’d like to align expectations as follows:

The fix is under development and will be released once all necessary testing is completed.

While the August patch may contain the fix, there is no guarantee that it will be immediately available to all environments.

A more realistic timeline for broad availability is +3 months after the initial release.

We are closely monitoring the progress with the engineering team and will keep you informed of any significant updates."
Bryan Fulkersin 0 Reputation points

2025-07-08T11:36:51.3433333+00:00

Is there a publication or other source of information regarding Bug 57816984? Interested in learning more about Bug 57816984 and how it would affect UDP transport of RDP/RDS traffic, causing it to hang, freeze, lock up or otherwise crash.
NZKiwiTech 0 Reputation points

2025-07-09T22:21:35.98+00:00

I'm aware it's not August or 3 months after yet but confirming the latest DLL version I have seen, 10.0.26100.4484 is still having the same issue.
Dennis | Digisens 0 Reputation points

2025-07-11T09:27:05.66+00:00

Hi Kaeden, In the post you made you state (Microsoft) that RailTest.dll components are related. How did they find this? Because in my log files i do not see this .dll back. i just want to check if it is indeed the exact same problem as that we experience. @marcelo gomes Do you have any updates from microsoft, that mayby link these problems to eachother?

Answer 1

Hi!

Just to give you guys a follow up.

I have been sending logs to a Microsoft engineer about this issue.

I will let you know as soon as I do.

This is what I have from a dump at the moment of the crash:

TextInputMethodFormatter!RemoteAppIntegrationClient::OperationCompleted2+0x19:
00007fff`15d01fb9 498b02          mov     rax,qword ptr [r10] ds:00000000`00000000=????????????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007fff15d01fb9 (TextInputMethodFormatter!RemoteAppIntegrationClient::OperationCompleted2+0x0000000000000019)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000001
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

PROCESS_NAME:  mstsc.exe

READ_ADDRESS:  0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

Share via

RemoteApp crashing on Windows Server 2025 with Windows 11/10

1 answer

Your answer