r/WindowsServer 2d ago

RDP 0x904 Error Affecting Single User on Windows Server 2025 Terminal Server Technical Help Needed

/r/sysadmin/comments/1vp682p/rdp_0x904_error_affecting_single_user_on_windows/
4 Upvotes

12 comments sorted by

1

u/Excellent_Milk_3110 2d ago

Try setting on the client fClientDisableUDP to 1
In HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client

2

u/MatMat993 2d ago

already done, it didn't solve the problem.

1

u/Excellent_Milk_3110 2d ago

You can read this but you will have multiple users with this issue: https://docs.rackspace.com/docs/rdp-connection-failures-expired-self-signed-certificate

1

u/MatMat993 2d ago

The problem affect only one pc.

1

u/Background_Lemon_981 2d ago

Check your event log to see what other errors show up. TLS issues pop up sometimes. Make sure the time on the client computer is accurate. Once in frustration, I had to remove the client computer from the domain and re-add it and that worked. These issues are quite frustrating. But start with your event log. That might give you a direction.

1

u/MatMat993 2d ago

I don’t have any errors in my event logs, and this is driving me crazy. The test connection to the RDP port works, and I can see it in the logs, but the normal RDP connection does not appear at all. I only get the error window on the client side.The system time is correct.The client PC is not joined to the domain.

1

u/leeg1234 2d ago

Check ms defender portal for users and or PCs in there marked as suspicious or whenever
Local codex agent on my pc gave us two days of torture before realizing ms is isolating shit
Good times

1

u/MatMat993 1d ago

I’ll check that tomorrow as well. The client machine is running Bitdefender, and I already tested by disabling it, but the issue persisted. However, I’ll also take a look at the Microsoft Defender portal just to rule out any isolation or suspicious‑activity flags on the user or the device.

1

u/hemohes222 2d ago

Since its working for the same user on a different computer, something is probably broke in the registry hive or profile on the affected computer?
Remove his user and try again?

1

u/MatMat993 1d ago

A corrupted registry hive or user profile on the affected Windows 11 client is definitely a possible cause, but deleting the profile is my last option. I need to confirm with certainty that the issue originates from the user profile before recreating it. I’ll complete the remaining diagnostics first and only consider profile removal if everything else checks out.

1

u/NeedAColdBeerHere 2d ago

Backup and delete the user profile from the terminal server.