Forum Discussion
KB5082063 RDP Security update
I agree with all of the above. In addition, I have a standalone PC, not part of a domain or workgroup. My user account is the Creator/Owner of the RDP files I use daily. They did not come from an external source. I created them, know them and trust them. I use them many times a day every day to access our Dev/Test, DR and Prod servers . Now I have 4 additional clicks EVERY TIME I need to access a server from my desktop.
Applying this extra warning to local and signed files actually weakens security. I created a local certificate, added it to the trust stores, and signed my own RDP files hoping to overcome this extra workload. I still get the additional 'warning'. The only difference is the publisher name instead of 'Unsigned'. I will habituate ignoring the warning because I will come to expect it every time I click my shortcut. So if ever there actually was a malicious one somehow introduced, I wouldn't notice the difference. Insert the tree among the forest analogy here if it helps.
Get rid of the additional security popup for locally-created RDP files where I am the creator owner, or have taken ownership, of the RDP file. In workgroups and domains where users aren't the owner, then having the file signed should do the same. Only show the warning for externally-originated, unsigned files where there is chance of a potential threat.