RemoteApp crashing on Windows Server 2025 with Windows 11/10

Question

RemoteApp crashing on Windows Server 2025 with Windows 11/10

Marcelo Gomes 40

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 40 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 40 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.

Marcelo Gomes 40

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

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?
Marcelo Gomes 40 Reputation points

2025-07-18T15:44:08.67+00:00

Hi Dennis, unfortunately no updates from Microsoft yet. I can't find any relation to RailTest.dll on my side. Maybe there are two separate problems.
Benson 0 Reputation points

2025-08-10T22:20:36.26+00:00

Keeping a close eye on this one, has anyone seen any updates from microsoft?.
ArnoV 0 Reputation points

2025-08-13T10:11:14.4366667+00:00

Hi Guys,

any update on this?

We have the exact same issue in different enviroment and even different hardware.

Almost thinking about reinstall the complete RDS farm to go back to Windows Server 2022...

Looks like Windows Server 2025 is still quite buggy..
Dennis | Digisens 0 Reputation points

2025-08-27T15:40:23.9633333+00:00

Hi!,

Sadly i still do not have any more info. We are having the sameproblem, do we wait or do we reinstall it back to 2022... This would be a big headache.

Hopefully someone has an update in a short while.
Marcelo Gomes 40 Reputation points

2025-08-27T17:29:00.4633333+00:00

Hi guys,

Unfortunately, there is no official solution from Microsoft yet. We are analyzing the possibility of going back to Windows Server 2022 at least for now.
Dennis | Digisens 0 Reputation points

2025-09-16T10:00:16.51+00:00

Hey All,

Unfortunately i've god no answers from Microsoft and the only thing i suspect is that is an small bug in Windows on only a few systems like ours, i have yet to find an fix and are also looking at going back tot Windows server 2022.

Is there an posibilty we can connect to eachother before we do this? Mayby i've we try to compare a few things we could find something.

The only thing that i can find right now is that the biggest problem occurs when working in email (email is intergrated in the program we use with Remoteapp).
Timo C 0 Reputation points

2025-09-18T14:36:41.31+00:00

Hello,

yes, connecting would be great. We have also been searching for two weeks and tried everything without success. Since we are running on Windows Server 2025, we believe this issue is related to a known bug.

Best way to connect here?

Best regards,
Andreas Jud 0 Reputation points

2025-10-15T09:45:42.1033333+00:00

Hello

Is there any news on this topic? We have the same problem and would be very grateful for a solution or new information.

Thanks

Andy
ArnoV 0 Reputation points

2025-10-15T09:50:20.74+00:00

Hi Andreas

We have downgraded our RDS environment back to Windows Server 2022, and all the crashes have stopped. We also noticed a performance improvement, so my advice would be to downgrade to Windows Server 2022 as well. Unfortunately, Windows Server 2025 seems to be a version to skip.
Dennis | Digisens 0 Reputation points

2025-10-15T10:22:37.0466667+00:00

Hi,

We also placed an Server 2022, as solution.
I've noted an Calendar for 06-2026, to check it is stable then.
Andreas Jud 0 Reputation points

2025-10-15T11:15:42.28+00:00

Thank you for your feedback. I think we also need to downgrade our “new” infrastructure that we set up in July.

The question for me would be, is it a client or server bug? Because it only affects Windows 11 clients and it's actually the client that crashes.
Salzner, Daniel 10 Reputation points

2025-10-22T06:43:13.0266667+00:00

Good morning, any news on this topic over the opened Microsoft Ticket?

We are facing into the same issue in our company.
Server 2025 ist native en-US, additional german language pack installed.

Windows 11 Clients have german language pack only. Input method will automatically assigned to german for RDP sessions. RDP disconnects are the result.

Graeme Lawton 5

We're also experiencing this, after upgrading to Server 2025. We see MSTSC crash every few minutes using our application. Dump analysis indicates exactly the same as above.

Incredibly disappointed to have to downgrade to 2022 after purchasing all the licensing for 2025, for 70 users. Particularly as this was reported 4 months ago!

PROCESS_NAME:  mstsc.exe

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

SYMBOL_NAME:  TextInputMethodFormatter!RemoteAppIntegrationClient::FocusLeaveCompleted+1c

MODULE_NAME: TextInputMethodFormatter

IMAGE_NAME:  TextInputMethodFormatter.dll

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_TextInputMethodFormatter.dll!RemoteAppIntegrationClient::FocusLeaveCompleted

FAILURE_ID_HASH:  {397b7b9a-0162-074b-bf9d-598189abde41}

Followup:     MachineOwner
---------

Salzner, Daniel 10 Reputation points

2025-11-04T11:54:58.3733333+00:00

We are getting the same mstsc.exe crash report on Server 2022 as well.

Only Server 2019 has no issue.
Graeme Lawton 5 Reputation points

2025-11-05T08:35:47.9733333+00:00

Interesting, we defiantly don’t see it in 2022.

I’ve virtualised our RDP server on a 2022 image and don’t see these occurring at all.

Users were experiencing it every few minutes on 2025.
Amy 0 Reputation points

2025-11-05T18:41:20.2+00:00

Same issue for us. Unfortuently we cannot go back to 2022 without a significant cost. We are using full RDP as a work around until RemoteApps are fixed.
Benson 0 Reputation points

2025-11-05T22:22:22.6733333+00:00

We have a ticket logged with MS for this issue as well. Not having much luck with a resolution so we have started testing Server 2022. Dissapointing that Microsoft havent provided a fix or even acknowledged the problem.
Dennis | Digisens 0 Reputation points

2025-11-06T07:56:40.75+00:00

i've got an second server/hyper-v Which now has Server 2022 with the remote app. So people with full RDS kan still login on the 2025 one and with remote app can log in on 2022. This way it is not that big of an cost to go back when it is patched.
Amy 0 Reputation points

2025-12-15T18:16:26.9066667+00:00

Have you heard anything else or found a fix yet?
Amy 0 Reputation points

2025-12-15T18:19:23.51+00:00

Has anyone gotten an update from microsoft yet? We are still using full RDP instead of remoteapp for now
Nitin Sharma 0 Reputation points

2025-12-27T07:07:42.19+00:00

Hey Marcelo,

Do you have an update for us on this, I am having the same issue with error code: 2147942464 for few users on RDS server 2022 Datacenter OS version 21H2
Nitin Sharma 0 Reputation points

2025-12-27T07:10:14.5733333+00:00

Hey Graeme, I am seeing this issue on 2022 server for few users in my organization.
Jakoniuk Maciej 0 Reputation points

2026-03-09T08:05:06.16+00:00

Any updates? Still waiting for the fix.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

3 answers

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 40 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 40 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.
Marcelo Gomes 40 Reputation points

2025-07-03T01:07:59.7+00:00

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
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?
Marcelo Gomes 40 Reputation points

2025-07-18T15:44:08.67+00:00

Hi Dennis, unfortunately no updates from Microsoft yet. I can't find any relation to RailTest.dll on my side. Maybe there are two separate problems.
Benson 0 Reputation points

2025-08-10T22:20:36.26+00:00

Keeping a close eye on this one, has anyone seen any updates from microsoft?.
ArnoV 0 Reputation points

2025-08-13T10:11:14.4366667+00:00

Hi Guys,

any update on this?

We have the exact same issue in different enviroment and even different hardware.

Almost thinking about reinstall the complete RDS farm to go back to Windows Server 2022...

Looks like Windows Server 2025 is still quite buggy..
Dennis | Digisens 0 Reputation points

2025-08-27T15:40:23.9633333+00:00

Hi!,

Sadly i still do not have any more info. We are having the sameproblem, do we wait or do we reinstall it back to 2022... This would be a big headache.

Hopefully someone has an update in a short while.
Marcelo Gomes 40 Reputation points

2025-08-27T17:29:00.4633333+00:00

Hi guys,

Unfortunately, there is no official solution from Microsoft yet. We are analyzing the possibility of going back to Windows Server 2022 at least for now.
Dennis | Digisens 0 Reputation points

2025-09-16T10:00:16.51+00:00

Hey All,

Unfortunately i've god no answers from Microsoft and the only thing i suspect is that is an small bug in Windows on only a few systems like ours, i have yet to find an fix and are also looking at going back tot Windows server 2022.

Is there an posibilty we can connect to eachother before we do this? Mayby i've we try to compare a few things we could find something.

The only thing that i can find right now is that the biggest problem occurs when working in email (email is intergrated in the program we use with Remoteapp).
Timo C 0 Reputation points

2025-09-18T14:36:41.31+00:00

Hello,

yes, connecting would be great. We have also been searching for two weeks and tried everything without success. Since we are running on Windows Server 2025, we believe this issue is related to a known bug.

Best way to connect here?

Best regards,
Andreas Jud 0 Reputation points

2025-10-15T09:45:42.1033333+00:00

Hello

Is there any news on this topic? We have the same problem and would be very grateful for a solution or new information.

Thanks

Andy
ArnoV 0 Reputation points

2025-10-15T09:50:20.74+00:00

Hi Andreas

We have downgraded our RDS environment back to Windows Server 2022, and all the crashes have stopped. We also noticed a performance improvement, so my advice would be to downgrade to Windows Server 2022 as well. Unfortunately, Windows Server 2025 seems to be a version to skip.
Dennis | Digisens 0 Reputation points

2025-10-15T10:22:37.0466667+00:00

Hi,

We also placed an Server 2022, as solution.
I've noted an Calendar for 06-2026, to check it is stable then.
Andreas Jud 0 Reputation points

2025-10-15T11:15:42.28+00:00

Thank you for your feedback. I think we also need to downgrade our “new” infrastructure that we set up in July.

The question for me would be, is it a client or server bug? Because it only affects Windows 11 clients and it's actually the client that crashes.
Salzner, Daniel 10 Reputation points

2025-10-22T06:43:13.0266667+00:00

Good morning, any news on this topic over the opened Microsoft Ticket?

We are facing into the same issue in our company.
Server 2025 ist native en-US, additional german language pack installed.

Windows 11 Clients have german language pack only. Input method will automatically assigned to german for RDP sessions. RDP disconnects are the result.
Graeme Lawton 5 Reputation points

2025-10-25T19:24:29.84+00:00

We're also experiencing this, after upgrading to Server 2025. We see MSTSC crash every few minutes using our application. Dump analysis indicates exactly the same as above.

Incredibly disappointed to have to downgrade to 2022 after purchasing all the licensing for 2025, for 70 users. Particularly as this was reported 4 months ago!

PROCESS_NAME: mstsc.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. SYMBOL_NAME: TextInputMethodFormatter!RemoteAppIntegrationClient::FocusLeaveCompleted+1c MODULE_NAME: TextInputMethodFormatter IMAGE_NAME: TextInputMethodFormatter.dll FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_TextInputMethodFormatter.dll!RemoteAppIntegrationClient::FocusLeaveCompleted FAILURE_ID_HASH: {397b7b9a-0162-074b-bf9d-598189abde41} Followup: MachineOwner ---------
Salzner, Daniel 10 Reputation points

2025-11-04T11:54:58.3733333+00:00

We are getting the same mstsc.exe crash report on Server 2022 as well.

Only Server 2019 has no issue.
Graeme Lawton 5 Reputation points

2025-11-05T08:35:47.9733333+00:00

Interesting, we defiantly don’t see it in 2022.

I’ve virtualised our RDP server on a 2022 image and don’t see these occurring at all.

Users were experiencing it every few minutes on 2025.
Amy 0 Reputation points

2025-11-05T18:41:20.2+00:00

Same issue for us. Unfortuently we cannot go back to 2022 without a significant cost. We are using full RDP as a work around until RemoteApps are fixed.
Benson 0 Reputation points

2025-11-05T22:22:22.6733333+00:00

We have a ticket logged with MS for this issue as well. Not having much luck with a resolution so we have started testing Server 2022. Dissapointing that Microsoft havent provided a fix or even acknowledged the problem.
Dennis | Digisens 0 Reputation points

2025-11-06T07:56:40.75+00:00

i've got an second server/hyper-v Which now has Server 2022 with the remote app. So people with full RDS kan still login on the 2025 one and with remote app can log in on 2022. This way it is not that big of an cost to go back when it is patched.
Amy 0 Reputation points

2025-12-15T18:16:26.9066667+00:00

Have you heard anything else or found a fix yet?
Amy 0 Reputation points

2025-12-15T18:19:23.51+00:00

Has anyone gotten an update from microsoft yet? We are still using full RDP instead of remoteapp for now
Nitin Sharma 0 Reputation points

2025-12-27T07:07:42.19+00:00

Hey Marcelo,

Do you have an update for us on this, I am having the same issue with error code: 2147942464 for few users on RDS server 2022 Datacenter OS version 21H2
Nitin Sharma 0 Reputation points

2025-12-27T07:10:14.5733333+00:00

Hey Graeme, I am seeing this issue on 2022 server for few users in my organization.
Jakoniuk Maciej 0 Reputation points

2026-03-09T08:05:06.16+00:00

Any updates? Still waiting for the fix.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

We have been working with Microsoft Support for several weeks on it. Currently there are prequalified three bugs (several *.dll libraries) in the mstsc.exe RDP client which all causes the crashes and which are confirmed by Microsoft.

With the Cumulative Update from December 2025 the first bug is fixed already by Microsoft - but only for 24h2 and 25h2. Older Windows 11 versions will not be fixed anymore.

For the second and third bug Microsoft is currently developing patches - after we had tested private fixes provided by them for the second bug.

They will be included in one of the next patch cycles - but again only for Windows 11 24h2 and 25h2.

Depending on your hardware vendor and installed applications on the end user workstations it may be that the Cumulative Update from December is helping already. If not you may be affected with the bug two and/or three like our company. The fix will be provided soon by Microsoft.

Answer 2

Philipp Reichl 0

We've received information from Microsoft and our Provider that this problem should resolved with Windows 11 25h2. Does anyone have experience with Windows 11 25h2! and Windows Server 2025 where this problem no longer occurs?

We haven't tested it yet because we don't have any Windows 25H2 clients.

Dennis | Digisens 0 Reputation points

2026-01-28T08:57:59.6966667+00:00

Hey Reph,

I've a user which till last week had problems and is on OS version 25H2 OS build 26200.7623. Mayby a few more update before it is completly fixed. He has access to the 2022 server, which he works on most of the time and i will ask him to test it again with the 2025 server after 10th of February.
Mike Barker 0 Reputation points

2026-03-18T21:34:17.1266667+00:00

Tried it with a 25H2 system on a fresh 2025 server, Full remote desktop, no problem. Remote app? Tells me off and to contact my network administrator. We have server 2022 versions running just fine on this deployment, DC is server 2025.

Answer 3

Marcelo Gomes 40

Hi everyone! After several months working with Microsoft Support, with limited progress, we reverted the RDS infrastructure to Windows Server 2022.

Nitin Sharma 0 Reputation points

2025-12-27T11:41:12.3+00:00

Hi Marcelo,

Thanks for sharing details on this but I have been facing issues on windows server 2022 as well for multiple users.
Salzner, Daniel 10 Reputation points

2026-04-01T08:14:18.7933333+00:00

We have been working with Microsoft Support for several weeks on it. Currently there are prequalified three bugs (several *.dll libraries) in the mstsc.exe RDP client which all causes the crashes and which are confirmed by Microsoft.

With the Cumulative Update from December 2025 the first bug is fixed already by Microsoft - but only for 24h2 and 25h2. Older Windows 11 versions will not be fixed anymore.

For the second and third bug Microsoft is currently developing patches - after we had tested private fixes provided by them for the second bug.

They will be included in one of the next patch cycles - but again only for Windows 11 24h2 and 25h2.

Depending on your hardware vendor and installed applications on the end user workstations it may be that the Cumulative Update from December is helping already. If not you may be affected with the bug two and/or three like our company. The fix will be provided soon by Microsoft.
Graeme Lawton 5 Reputation points

2026-04-01T12:21:29.76+00:00

Thanks very much for the update @Salzner, Daniel

Hopefully the end is in sight!

Share via

RemoteApp crashing on Windows Server 2025 with Windows 11/10

3 answers

Your answer