Automates clicking through the new RDP security prompt to revert to the old double-click-and-type UX.
Double click/ open the .exe with no paramaters to use the GUI set up wizard to configure and create an Auto-Rdp shortcut, else set up manually following instructions below.
Single combined exe for gui and clickbot.
Localisation now universal. (Prior was restricted to English).
RdpAutoClick.exe "C:USERS\PC\Desktop\Win10.rdp" Clipboard Drives
This will pre-click checkboxes named 'Clipboard' and 'Drives' then connect
- V4+ Requires .NET 4.8 framework which is usually present on most Windows 10 and 11 systems
- Enter Powershell command to test compatability:
$r=(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -ErrorAction SilentlyContinue).Release; if($r -ge 528040){"Compatible with RDP autoclicker (.NET 4.8+)"} else{"Not compatible (requires .NET Framework 4.8 or later)"}
- Officially you should be using signed rdp files
- Microsoft support a cleaner admin only registry fix editing HKEY LOCAL MACHINE but have said it may be patched out
- Since this is a security pop up it is automating it may get blocked one day. The intention to increase security a little bit is to ensure the machine name the user expects is still in the rdp file by adding a new "connectTo" parameter and verifying the rdp matches. This atleast means the user has passed and checked the machine hasnt changed. (tbd)
RdpAutoClick.exe "C:\file.rdp" [optional checkbox option names or Ids]
RdpAutoClick.exe -usage
This will show the paramater usage
RdpAutoClick.exe "C:\file.rdp" -showIds
This will display all available checkbox names and ids as stored in Windows automation.
RdpAutoClick.exe "C:\file.rdp" -all
This will select every available checkbox
RdpAutoClick.exe click [rdpX] [rdpY] [connectX] [connectY] [optional pre click x and ys]
Optionally change the icon of the shortcut to be RDP icon. 'Richt Click - Properties - Change Icon - Browse - C:\Windows\System32\mstsc.exe
Youtube watch?v=VETpTN30J1Y
Names of checkboxes:
- Open the desired rdp file to force the security prompt and inspect and note down the checkbox names you want to pre click. (Case sensitive)
- If names are non-simple (e.g. more than one word or with qualifiers) run with "-showIds" (see Usage) to get exact names or automation ids
- Close rdp after noting down names/ids
Rdp path
- Right click rdp file and choose 'Copy as path'
Finally add parameters
- Download and unzip RdpAutoClick.exe to a suitable location
- If happy with the .exe's location, double-click or open the exe to pre-set any warning triggers. E.g) If Windows smartscreen 'protected' your pc and stopped the exe running, click 'More info' then 'Run anyway' to prevent this dialogue in the future.
- Add exe shortcut. Right click .exe and choose 'Send To...Desktop (create shortcut)' and rename the shortcut after your rdp vm name
- Add paramaters: Right click the shortcut on Desktop and click 'Properties'
- In the Traget field, add Rdp Path as the first parameter in quotes after the exe path, and any desired checkbox names, without quotes if single word or with quotes if contains spaces.
e.g.) Target:# RdpAutoClick.exe "C:\Users\Dave\Desktop\WIN10.rdp" Clipboard Drives (This will pre click Clipboard and Drives) - Save and test.
Get X and Y coordinates
- Copy contents of 'powershell_command.find_pos.txt' into Powershell and press enter confirming any 'multi-line' warnings
- Keeping powershell visible, hover over the rdp file and note down the x and y values then open to force the prompt, similarly for any wanted pre-clicks such as clipboard as well as the final connect button position note down the x and y values.
Add parameters
- Extract RdpAutoClick.exe to a suitable loacation
- Create desktop shortcut of .exe and name it after your chosen rdp file/vm name
- Edit desktop shortcut properties Target field to include parameters: See Usage, E.g.) Target:# RdpAutoClick.exe "C:\USERS\BAKERDA\Desktop\WIN10.rdp" 1104 659 768 561 (This expects the rdp at 1104 659 and the connect button at 768 561 with no pre clicks defined
The first version to use a single .exe
The first version to both support every windows language and use a dictionary of top ten languages for user/error messages.
Now with a easy to use GUI set up wizard
The first NET 4.8 dependant version and the first version to automate the clicking by button name.
Flaws:
- NET 4.8 must be installaled. (Already present on most moderrn systems)
This is the first c# versions and the last 2 versions based on clicking at x and y coordinates as oppose to button name
Note:
- These have not been tested thoroughly for dependencies. The target was NET 8.0 framework so it is possible NET 8 may be required.
Flaws: - Click locations require fixed resolution so any resolution change (such as going from wfh to office) will need their own shortcuts.
This is the last self contained visual basic version.
Flaws:
- Large file size and slow to start until cached.
Use a pen or phone to note down the coordinates while hovering windows cursor over the buttons. If prefer windows a tip is to have it so a .txt pad, the security pop up and the LHS of Powershell are all cleanly visible. Click txt pad first to type, hover over button, examine Powershell without clicking anywhere else and type.
Move original rdp files to a folder and use the tools Path Mode.
- When editing target field use Ctrl A and copy off the small form field into a text editor and Ctrl A Del. Ctrl V to replace when finished adding coordinates
- Use path mode
- Have all rdps in the same directory
V3.2/V3.0
95% Visual Basic Human-developed, (assistance in stopping cmd pop ups)
100% C# LLM-Claude-converted.
- First developed and ironed out behaviour in Visual Basic, then after realising dependencies and file size, the source code was forwarded to Claude LLM asking for conversion to C#.
V4.0
No assistance in using Windows.Automation actual code.
A lot of Claude and GPT interaction to get the exe suitable and fast and still have Windows.Automation pulled into the project. (2-3hrs)