| Channel | Build Status | Downloads |
|---|
| Stable | | |
| Preview | | |
| Nightly | | |
Features
The following protocols are supported:
- RDP (Remote Desktop Protocol)
- VNC (Virtual Network Computing)
- SSH (Secure Shell)
- Telnet (TELecommunication NETwork)
- HTTP/HTTPS (Hypertext Transfer Protocol)
- rlogin (Remote Login)
- Raw Socket Connections
- Powershell remoting
- AnyDesk
For a detailed feature list and general usage support, refer to the Documentation.
Build environment
This project must be built on Windows using Visual Studio 2026 tooling. Use the MSBuild.exe from the Visual Studio 2026 installation instead of the .NET Core dotnet build fallback; the Windows desktop project requires the Visual Studio build environment and COM/desktop targets.
For local builds, prefer:
& "$env:ProgramFiles(x86)\Microsoft Visual Studio\2026\Enterprise\MSBuild\Current\Bin\MSBuild.exe" mRemoteNG.sln /p:Configuration=Debug /p:Platform=x64
If your installation path differs, locate the VS2026 MSBuild from vswhere.exe first and then call that MSBuild.exe explicitly.
Plugin development workflow
Plugin projects are built from a separate plugin-only solution and loaded from the app's plugin folder at runtime.
To build the plugin set:
dotnet build mRemoteNG.Plugins.sln -c Release -p:Platform=x64
Then copy the generated plugin DLLs into the app plugin folder, while keeping the shared contracts assembly in the app's Assemblies folder:
The example below uses the x64 output path. For ARM64 builds, replace x64 with arm64.
Copy-Item .\mRemoteNG.PluginContracts\bin\x64\Release\net10.0-windows10.0.26100.0\mRp.Contracts.dll .\mRemoteNG\bin\x64\Release\Assemblies\
Copy-Item .\mRemoteNG.Plugins.PortScan\bin\x64\Release\net10.0-windows10.0.26100.0\mRp.PortScan.dll .\mRemoteNG\bin\x64\Release\Plugins\
Copy-Item .\mRemoteNG.Plugins.SshTransfer\bin\x64\Release\net10.0-windows10.0.26100.0\mRp.SshTransfer.dll .\mRemoteNG\bin\x64\Release\Plugins\
Copy-Item .\mRemoteNG.Plugins.AWS\bin\x64\Release\net10.0-windows10.0.26100.0\mRp.AWS.dll .\mRemoteNG\bin\x64\Release\Plugins\
Copy-Item .\mRemoteNG.Plugins.MultiAddress\bin\x64\Release\net10.0-windows10.0.26100.0\mRp.MultiAddress.dll .\mRemoteNG\bin\x64\Release\Plugins\
See README.plugins.md for the full workflow and details.
Installation
Supported Operating Systems
Source package
This contains the source code from which mRemoteNG is built.
You will need to compile it yourself using Visual Studio.
Minimum Requirements
Make sure you have the latest version installed:
- Microsoft Terminal Service Client 6.0 or later (needed if you use RDP with mstscax.dll and/or msrdp.ocx to be registered)
Download
:star: Starting Windows 11 you can use winget to install mRemoteNG. Just run winget install -e --id mRemoteNG.mRemoteNG
mRemoteNG is available as a redistributable MSI package or as a portable ZIP package and can be downloaded from the following locations:
Command line install
The MSI package of mRemoteNG can be installed using the command line:
msiexec /i C:\Path\To\mRemoteNG-Installer.msi [/qn] [INSTALLDIR=value] [IGNOREPREREQUISITES=value] [/lv* <log path>]
Note on privileges: The MSI installer supports dual-mode installation. By default, it will prompt for an installation scope in the UI. When running silently (/qn), it skips the UI and installs per-machine by default (which requires Administrator privileges). If you want to silently install it for the current user without requiring Administrator privileges, you must set the MSIINSTALLPERUSER=1 ALLUSERS=2 properties from the command line.
| Argument/Property | Value | Description |
|---|
| /qn | Silent Installation | Will run the installer silently in the background. |
| /lv* | Silent Installation | Will write a logfile to the specified location. (For paths that contain spaces, enclose the path in double quotes) |
| INSTALLDIR | folder path | Allows you to set the installation directory from the command line. (For paths that contain spaces, enclose the path in double quotes) |
| IGNOREPREREQUISITES | 0 or 1 | When set to 1, the installer will not be halted if any prerequisite check is not met. Administrator privileges are still required for a per-machine installation. |
| ALLUSERS | 2 | Enables single-package authoring so MSIINSTALLPERUSER can select the installation scope. |
| MSIINSTALLPERUSER | 1 | With ALLUSERS=2, installs for the current user; omit this property for a per-machine installation. |
Manual Uninstall
If you are using the Portable version, simply deleting the folder that contains mRemoteNG should be sufficient. These uninstall instructions are only necessary for the normal binary .MSI installed version of mRemoteNG
-
Delete the folder where mRemoteNG was installed. By default, this is:
%PROGRAMFILES%\mRemoteNG (for versions before 1.77 on a x64 Windows its %programfiles(x86)%\mRemoteNG)
-
Delete the mRemoteNG install entry from the following location. You may search for "mRemoteNG" in the DisplayName field:
- x86 Windows or mRemoteNG starting with v1.77:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
- x64 Windows and mRemoteNG before 1.77:
HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\
-
Remove the following registry key: HKLM\SOFTWARE\mRemoteNG (on x64 Windows with mRemoteNG before 1.77 it's HKLM\SOFTWARE\WOW6432Node\mRemoteNG)
-
(Optional) If you would also like to delete user data remove %LOCALAPPDATA%\mRemoteNG
-
(Optional) If you would also like to remove the connection configuration, delete %APPDATA%\mRemoteNG
-
(Optional) If no other software uses it, the "Microsoft Windows Desktop Runtime" may be uninstalled too.
Featured Projects
- PSmRemoteNG A module to create mRemoteNG connection files from PowerShell.
- mRemoteNGOpenVPN A script that can be embedded as an external tool to control OpenVPN.
- mRemoteNG-Icons A collection of fancy icons to customize the connections
Contribute
If you find mRemoteNG useful and would like to contribute, it would be greatly appreciated. When you contribute, you make it possible for the team to cover the costs of producing mRemoteNG.
Submit Code
Check out the Wiki page on how to configure your development environment and submit a pull request.
Translate
Check out the Wiki page on how to help make mRemoteNG a polyglot.
