Use the "Run Command" feature in the Azure Portal to execute: Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old" Then, reboot the server to let it rebuild the key store.
"The connection was denied because the user account is not authorized for remote login." (Generic message) OR "Your computer can't connect to the remote computer because an error occurred on the remote computer that you are trying to connect to."
Error 0x904 isn’t just a generic “can’t connect.” It usually means the configuration on the target machine is missing a required role service or is stuck in a “listening but not accepting” state.
In your RDP client, enter the (e.g., 192.168.1.50 ) instead of the computer name.
Insufficient bandwidth, high packet loss, or slow VPN connections. TLS/Cipher Mismatches:
If you are using third-party antivirus software, you will need to consult its specific documentation to create an exception for TCP port 3389 and for . In many cases, you can temporarily disable the third-party firewall entirely to test if it is causing the issue.
If using a VPN, disconnect and reconnect to ensure a stable tunnel is established. 4. Special Fix for Azure VMs
Enable and select RDP as the layer.
Try the following methods in order to resolve the connection error.
If the certificate is not expired, the MachineKeys folder may be corrupted. This is especially common on Azure virtual machines but can occur on any Windows server.
Log into the affected server locally or via an alternative remote tool. certlm.msc
An expired or corrupted self-signed certificate on the remote host computer causes the majority of 0x904 errors. To force Windows to generate a clean, unexpired certificate, complete the following steps:
Input the following snippet to safely isolate the corrupted cryptographic directory: powershell
Ultimate Troubleshooting Guide: Fixing Remote Desktop Connection Error Code 0x904
Then the issue is likely a corrupted RDP listener. Uninstall and reinstall the :
Remote Desktop error code (often accompanied by extended error 0x7)
Use the "Run Command" feature in the Azure Portal to execute: Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old" Then, reboot the server to let it rebuild the key store.
"The connection was denied because the user account is not authorized for remote login." (Generic message) OR "Your computer can't connect to the remote computer because an error occurred on the remote computer that you are trying to connect to."
Error 0x904 isn’t just a generic “can’t connect.” It usually means the configuration on the target machine is missing a required role service or is stuck in a “listening but not accepting” state.
In your RDP client, enter the (e.g., 192.168.1.50 ) instead of the computer name.
Insufficient bandwidth, high packet loss, or slow VPN connections. TLS/Cipher Mismatches:
If you are using third-party antivirus software, you will need to consult its specific documentation to create an exception for TCP port 3389 and for . In many cases, you can temporarily disable the third-party firewall entirely to test if it is causing the issue.
If using a VPN, disconnect and reconnect to ensure a stable tunnel is established. 4. Special Fix for Azure VMs
Enable and select RDP as the layer.
Try the following methods in order to resolve the connection error.
If the certificate is not expired, the MachineKeys folder may be corrupted. This is especially common on Azure virtual machines but can occur on any Windows server.
Log into the affected server locally or via an alternative remote tool. certlm.msc
An expired or corrupted self-signed certificate on the remote host computer causes the majority of 0x904 errors. To force Windows to generate a clean, unexpired certificate, complete the following steps:
Input the following snippet to safely isolate the corrupted cryptographic directory: powershell
Ultimate Troubleshooting Guide: Fixing Remote Desktop Connection Error Code 0x904
Then the issue is likely a corrupted RDP listener. Uninstall and reinstall the :
Remote Desktop error code (often accompanied by extended error 0x7)
NOTE: If you're still having trouble getting either methods to work, then see here.
I often get e-mails from people asking how they can donate to my projects, but I don't like to accept donations for this particular kind of stuff. If you'd still really like to help out, though, if you buy any EarthBound/MOTHER merchandise through these links, I'll get a dollar or so. This will help keep EarthBound Central up and running, not to mention many of my other projects, like Game Swag!
| Poe | byuu | reidman | Jonk | Plo |
| sarsie | HockeyMonkey | weasly64 | Rhyselinn | PKDX |
| Buck Fever | dreraserhead | Demolitionizer | Kasumi | Ness and Sonic |
| PK_Fanta | linkdude20002001 | climhazard | TheZunar123 | sonicstar5 |
| Skye | Triverske | Mother Bound | Blair32 | PSIWolf674 |
| Ice Sage | PK Mt. Fuji | The Great Morgil | Ness-Ninten-Lucas | LordQuadros |
| Ross | rotschleim | LakituAl | Kuwanger | MotherFan |
| Anonymous | BroBuzz | Trevor | Rathe coolguy | EBrent |
| Robert | KingDarian | Satsy | tapioca | curtmack |
| Chuggaaconroy | Roido | MarioFan3 | blahmoomoo | VGMaster64 |
| Corey | Superstarman | Halloween | Robo85 | ZUUL |
| Crav | Priestess Paula | My Name Here | Aangie | platinatina |
| Petalklunk | Aviarei | Cuca | Realn |
And probably a hundred or more other helpful people! Forgive me if your name should have been here, there are so many to remember that my brain is failing me now. But know that your help was appreciated and led to this patch's creation!