the two computers couldn't connect in the amount of time allotted

Question

the two computers couldn't connect in the amount of time allotted

Robins Kumar 5

Anyone from Microsoft team please help me the solution. User's image

Carlos Alcala 0 Reputation points

2026-09-22T16:20:48.0233333+00:00

I've started to see the same error message after the last Windows Security Updates were installed on the server we are having the issue.

3 answers

Your answer

Carlos Alcala 0 Reputation points

2026-09-22T16:20:48.0233333+00:00

I've started to see the same error message after the last Windows Security Updates were installed on the server we are having the issue.

Answer 1

sachin kumar 0

Microsoft releases emergency Windows updates to fix RDS failures

This is due to Latest Patch released by Microsoft.

to Fix the issue please installed the patch as per the windows os version

here is the Resolution article.

https://www.bleepingcomputer.com/news/microsoft/microsoft-releases-emergency-windows-updates-to-fix-rds-failures/

0 comments

Answer 2

Hello Robins,

This error happens because your computer tries to connect using a fast network protocol called UDP, but something on your network or firewall is blocking it before it can establish a connection.

To fix this right now, we just need to force your Remote Desktop app to use the standard, reliable TCP connection instead:

Click the Start menu, search for Registry Editor, and open it.

In the top address bar, paste this path and press Enter:Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client

Right-click on the right side of the window, select New > DWORD (32-bit) Value, and name it fClientDisableUDP.

Double-click fClientDisableUDP, change its value data to 1, and click OK.

Once you close the Registry Editor, try connecting through Remote Desktop again, it should connect immediately without timing out.

Hope this helps :) Please give it a thumbs up if you find my support helpful, thank you very much!

Answer 3

For the Remote Desktop timeout error, check these items in order:

Verify the remote computer is available.
- Make sure the remote computer is turned on.
- Try connecting by computer name and by IP address.
- Confirm the remote computer is reachable on the network.
Confirm Remote Desktop is allowed.
- The error can occur if remote access is not enabled on the target machine.
- Also make sure no policy is blocking Remote Desktop connections.
Check Windows Firewall on the remote computer.
- Open wf.msc.
- Go to Inbound Rules.
- Make sure these rules are enabled for all profiles:
  - Remote Desktop - User Mode (TCP-In)
  - Remote Desktop - User Mode (UDP-In)
- PowerShell alternative in an elevated session:
```
     Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Set-NetFirewallRule -Enabled True
```
Check other network controls.
- If there is a firewall, proxy, antivirus, or network security filtering between the two computers, it may be blocking RDP traffic.
- If possible, temporarily disable antivirus and test again.
- In Azure, verify the Network Security Group allows RDP.
Verify the machine state.
- If the machine is running but still cannot be reached, test access through console access if available.
- If the machine cannot be put into a running state, or console access also fails, Microsoft Support is required.
If the issue is specifically a timeout on a remote management connection using WMI, use the maximum wait flag.
- For SWbemLocator.ConnectServer or IWbemLocator::ConnectServer, set wbemConnectFlagUseMaxWait or WBEM_FLAG_CONNECT_USE_MAX_WAIT to 128 (0x80) to impose a two-minute timeout.

If the connection still fails after firewall and network checks, and connectivity tests remain unsuccessful, contact Microsoft Support.