Summary: The new minor release of UDS Enterprise 4.0, Build 20260428, includes a new UDS Client for Windows and a new UDS Server to adapt to the RDP security changes introduced by Microsoft. By default, the version maintains the usual connection flow, as long as Microsoft continues to allow it, and adds support for signed RDP connections in environments that want to strengthen trust in the origin of remote sessions.
The Virtual Cable development team has released a new minor release of UDS Enterprise 4.0, Build 20260428, to adapt to the new security requirements introduced by Microsoft in its Remote Desktop client, RDP.
This new version includes a new UDS Client for Windows and a new UDS Server to minimize the operational impact of the changes introduced by Microsoft following the KB5083769 security update published on April 14, 2026.
By default, and as long as Microsoft continues to allow it, UDS Enterprise will maintain the traditional behavior of RDP connections to avoid changes in the user experience and ensure operational continuity in enterprise and academic environments.
Additionally, the new version also includes support for signed RDP connections, allowing connections generated from UDS Enterprise to be recognized as coming from a known and trusted issuer in environments that choose to adopt this new trust model.
At Virtual Cable, we fully share the goal of these security measures promoted by Microsoft: to strengthen the protection of remote connections and provide users with more information and control before establishing a session.
What is changing in RDP connections?
After installing the KB5083769 update, Microsoft’s RDP client introduces new security mechanisms designed to increase trust in the origin of remote connections and provide users with more information before establishing a session.
The main changes include:
- Security warnings when opening files or starting RDP connections.
- Information about the publisher of the RDP file, indicating whether the connection comes from a known or untrusted issuer.
- Detailed information about the remote destination and the local resources that may be redirected.
- Redirections disabled by default until the user enables them manually.
- New informational messages related to potential phishing risks or untrusted connections.
These measures help reduce the risk of a user opening a malicious RDP file and ending up connected to a non-legitimate system, sharing local resources without being fully aware of it.
Impact on virtualized environments with UDS Enterprise
In organizations that use virtualized workstations with UDS Enterprise, these changes may introduce some friction into the user experience, especially in environments with intensive use of RDP connections.
Users may encounter new security warnings, additional confirmation requests, or changes in common functionality related to local resource redirection.
It is important to note that this behavior is not caused by a UDS Enterprise failure, but by a global change introduced by Microsoft in the way the RDP client works.
For this reason, at Virtual Cable we continue to recommend that redirection policies be defined and controlled from the service itself, not only from the protocol. This enables centralized, consistent management aligned with each organization’s security policies.
Precisely to reduce this impact and support operational continuity in enterprise and academic environments, Virtual Cable has added new capabilities to UDS Enterprise 4.0.
New UDS Client for Windows: operational continuity and support for signed RDP connections
To adapt to this new security model, Virtual Cable has developed a new UDS Client for Windows as part of the new minor release of UDS Enterprise 4.0.
To preserve daily operations, UDS Enterprise will maintain the usual connection flow by default, as long as Microsoft continues to allow it. This way, users can continue working as before, with no additional steps or visible changes in their connection process.
Additionally, this new version includes support for signed RDP connections. Thanks to this improvement, the RDP client can identify that the connection has been generated from a known and trusted environment, reducing warnings associated with connections whose origin cannot be properly verified.
The goal of this development is not to disable or bypass Microsoft’s protection mechanisms. On the contrary: UDS Enterprise adapts to this new model by offering two options depending on each environment’s needs: maintaining operational continuity by default or using signed RDP connections to strengthen trust in the origin of the connection.
In practice, this helps reduce friction for end users and makes day-to-day operations easier for IT teams in corporate and academic environments with intensive use of RDP connections.
Fast response from the Virtual Cable development team
After detecting the change introduced by Microsoft, the Virtual Cable development team responded immediately to analyze its impact and provide solutions for partners and customers.
As an initial measure, the team made a corrective solution available to affected environments to revert the behavior of the Microsoft client when necessary, along with the corresponding technical documentation to properly update the components involved on UDS servers.
This response has now been completed with a new minor release of UDS Enterprise 4.0, which includes a new UDS Client for Windows and a new UDS Server to adapt to this new security scenario.
What partners and customers should do
Virtual Cable partners and customers can apply the solution in the way that best fits their environment: by updating to the new minor release of UDS Enterprise 4.0 or by deploying the new UDS Client for Windows on connection devices.
To ensure that new installations include this improvement, we recommend uploading the new UDS Client to all UDS servers in the environment.
Our support team is available to assist partners and customers throughout the process and answer any technical questions related to these measures.
Security, trust, and operational continuity
The changes introduced by Microsoft represent another step forward in strengthening the security of remote connections. At Virtual Cable, we support this approach and have worked to ensure that UDS Enterprise adapts quickly, securely, flexibly, and transparently to this new scenario.
This new minor release of UDS Enterprise 4.0 enables organizations to maintain operational continuity while moving toward a more trusted RDP connection model, aligned with Microsoft’s new security requirements.
For any questions or assistance during the process, you can contact our support team: [email protected]
What is Microsoft changing in RDP connections?
Microsoft has introduced new security mechanisms in its Remote Desktop client to strengthen protection against potentially malicious RDP files. These changes show users more information before establishing the connection and may require additional confirmations.
How does this change affect UDS Enterprise?
In environments with UDS Enterprise, the new RDP security requirements may generate additional warnings or changes in the connection experience. This is not a UDS Enterprise failure, but a global change introduced by Microsoft in the RDP client.
What does the new minor release of UDS Enterprise 4.0 include?
The new minor release of UDS Enterprise 4.0, Build 20260428, includes a new UDS Client for Windows and a new UDS Server to adapt to Microsoft’s RDP security changes, while maintaining operational continuity and adding support for signed RDP connections.
What are signed RDP connections?
Signed RDP connections allow the RDP client to identify that the connection comes from a known and trusted issuer. This helps strengthen trust in the origin of the remote session and reduce warnings associated with connections whose origin cannot be properly verified.
What should Virtual Cable partners and customers do?
Partners and customers can update to the new minor release of UDS Enterprise 4.0 or deploy the new UDS Client for Windows on connection devices. We also recommend uploading the new UDS Client to all UDS servers in the environment so that new installations include this improvement.
0 Comments