RDP connection to Windows 10 client fails with code 0x904
I have a Win10 workstation to which I cannot RDP. I use the built-in RDP client from Win11. The connection fails with the following message (translated from German):
"Error code: 0x904
Extended error code: 0x7"
The workstation is fully set up and working fine otherwise. A lot of customization has been done by the main user. Would be a shame to have to do all this again. However, RDP is vital for the use case on this machine.
Unfortunately, I had trusted the main user with installing his own software. And for whatever reason he had been running Windows 7 Firewall Controll, and then later removed it. He contacted me when he found he cannot longer RDP.
What I have already tried:
- connecting via NetBios name as well as IPv4 address (both pingable)
- resetting the Windows firewall
- fully disabling Windows firewall
- resetting the complete network settings as per Win10
- uninstalling the network device from device manager (including driver software) and reinstalling it
- use a different NIC on this machine
- connect from a different guest (even Android)
- use Win10 Firewall Control portable to access the existing rules, but no avail (all has been deleted)
- use the Windows Store RDP app, it also fails to connect with this output (translated from German):
"Error code: 0x4
Extended Error code: 0x0
Activity ID: {98bd10a7-6d18-4103-9336-91673e6a0000}"
What I have checked:
- RDP related services are running
- RDP related firewall rules are set and enabled (plus disabling the firewall does not help)
- I can ping the machine
- I can access shared folders
- I can RDP into a different Windows 10 installation on the same machine (it's dual boot)
What else can I do?
"Error code: 0x904
Extended error code: 0x7"
The workstation is fully set up and working fine otherwise. A lot of customization has been done by the main user. Would be a shame to have to do all this again. However, RDP is vital for the use case on this machine.
Unfortunately, I had trusted the main user with installing his own software. And for whatever reason he had been running Windows 7 Firewall Controll, and then later removed it. He contacted me when he found he cannot longer RDP.
What I have already tried:
- connecting via NetBios name as well as IPv4 address (both pingable)
- resetting the Windows firewall
- fully disabling Windows firewall
- resetting the complete network settings as per Win10
- uninstalling the network device from device manager (including driver software) and reinstalling it
- use a different NIC on this machine
- connect from a different guest (even Android)
- use Win10 Firewall Control portable to access the existing rules, but no avail (all has been deleted)
- use the Windows Store RDP app, it also fails to connect with this output (translated from German):
"Error code: 0x4
Extended Error code: 0x0
Activity ID: {98bd10a7-6d18-4103-9336-91673e6a0000}"
What I have checked:
- RDP related services are running
- RDP related firewall rules are set and enabled (plus disabling the firewall does not help)
- I can ping the machine
- I can access shared folders
- I can RDP into a different Windows 10 installation on the same machine (it's dual boot)
What else can I do?
Please also mark the comments that contributed to the solution of the article
Content-ID: 668888
Url: https://administrator.de/contentid/668888
Printed on: December 3, 2024 at 11:12 o'clock
1 Comment