Beta

Hello everybody, We are happy to release the RDM 2026.1 BETA version. This is a major update and requires a database update. Please back up your database before installing this beta for maximum safety. Please report your issues in a separate thread to simplify the follow-up. We have some additional information depending on the data source you use: Devolutions Server users: DVLS 2026.1 beta is required Devolutions Hub Business and Hub Personal are both supported Download: https://cdn.devolutions.net/download/Devolutions.RemoteDesktopManager.Bin.2026.1.8.0.zip (universal) https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.2026.1.8.0.msi (universal) https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.win-x64.2026.1.8.0.msi (x64-optimized) https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.win-arm64.2026.1.8.0.msi (arm64-optimized) New features: Added a way for an administrator to create a preset dashboard for their users Added ControlR entry type Added Docker management console entry Added GetScreen entry type Added JWT credential entry type Added JWT decoder tool Added local backup to Hub Personal datasources Added local recording support for all free data sources Added PGP credential entry type Added PowerShell Universal entry type Added the possibility to create custom widgets for the vault dashboard, with a reordering feature Breaking changes: Extended "hide entries" options in the user preferences and "File -> Settings" to affect folders and removed the "hide expired groups" option from "File -> Settings" Removed 1Password local mode - no longer supported since 1Password 8 Removed authentication mode from "My Account Settings" for the OneIdentity entry - This information will need to be entered directly in the entry Removed Box explorer entry Removed Chrome embedded - Use Edge instead Removed GoToAssist entry Removed legacy Bitwarden synchronizer settings Removed Spiceworks entries (synchronizer and session) Removed support for Dropbox datasource - Use XML datasource instead Removed support for Google Drive datasource - Use XML datasource instead The "Parameters" section of newly added/edited "Report (custom)" entries will not be saved the same way as it was in older versions of RDM. Going back to RDM 2025.3.X.X or an earlier version of RDM and editing a "Report (custom) entry that was added/edited in 2026.1 or newer will result in the loss of the saved "Parameters" Deprecated features: Cryptocurrency cold storage entry type is deprecated Deprecated Spiceworks import - Use the generic CSV importer instead Deprecated Spiceworks tool Deprecated TrueKey entry Release notes: https://devolutions.net/remote-desktop-manager/release-notes/beta/

Hello, we are experiencing an issue with the new 1Password SSO integration that came with this Beta. We originally were having this issue on version 2026.1.6.0 64-bit. We updated to 2026.1.8.0 64-bit today and can still replicate the issue. Environment info: Windows 11 25H2 - 26200.7840 1Password for Windows 8.11.23 (81123001) 1Password SSO is configured using Entra ID, with a conditional access policy that requires a hardware token be used We have configured 1Password inside Remote Desktop Manager (RDM) by doing the following: Click File Click "My account settings" Click "My personal credentials" In the bottom left corner click 1Password Change the "Host" field to our company 1Password domain <company>.1password.com Change "Login Method" to SSO Enter Username and authenticate Transfer the encryption key from 1Password into RDM Select a credential from the Private folder as our default We have an RDP entry setup with a full host name, and "Credentials" set to "My personal credentials". See below screenshot [image] Upon trying to connect to this server, we get the below error [image] One time while doing the steps to setup 1Password in RDM, we got a 2nd "Transfer encryption key request" within 1Password. However no window ever appeared in RDM for us to input the key. I suspect that this may be related to, or is the cause of, our issue.

Upgraded to the 2026.1.8.0 beta to try out the new regex filtering for this synchronizer, however it is currently failing to run with the message "Error in deserializing body of reply message for operation 'RetrieveProperties'" shown in the logs whenever I try to run it. Downgrading back to 2025.3.32.0 immediately resolves the issue, and then it reoccurs as soon as I upgrade back to the beta. Also question about the regex filter that was added, it is labeled "Exclude by name(Regex):", does the regex need to return true or false to be excluded? Like will it discard matches for the regex I put in(needs to return true for things I want to exclude), or do I need to enter a regex that won't match for the pattern I don't want imported(needs to return false for things I want to exclude)? Can we just have it be "Filter by name(Regex)" and its 'needs to return true for things I want to include" if that makes sense.

Hello, updated to the 2026.1 beta to try out the new regex filtering but I can no longer even run the vmware synchornizer, it errors with the message "Error in deserializing body of reply message for operation 'RetrieveProperties'." Uninstalling and putting the current release version resolves the issue pretty much immediately, and then it happens again as soon as I update to the beta. Also question on the regex, its labelled as "Exclude by name(Regex)". Does that mean the regex I put in needs to return true or false? Like, does it discard any matches it finds and so I need to have it return true when it matches the pattern I want to exclude, or is it I need to have it return true when it does match something I want to include? Can we just label it "Filter by name" and have it just include/discard based on it returning true/false like a normal regex field?

Hello everybody, We are happy to release RDM 2025.1 beta version. This is a major update and requires a database update. Please back up your database before installing this beta for maximum safety. Please report your issues in a separate thread to simplify the follow-up. We have some additional information depending on the data source you use: Devolutions Server users: DVLS 2025.1 beta is required . It's available here: https://devolutions.net/server/home/download/ Devolutions Hub Business and Hub Personal: The version is compatible with the RDM beta and doesn't require any additional steps. Download: https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.2025.1.11.0.msi https://cdn.devolutions.net/download/Devolutions.RemoteDesktopManager.Bin.2025.1.11.0.zip New features: Added a "local admin report" feature Added a view vault history functionality Added a way to configure the application as a git commit signing utility Added AI assistant to improve the text memo including description and comments Added an AI assistant entry to store the information and run a chat in the application Added Custom PowerShell VPN Added CyberArk SIA entry as a VPN-type entry for RDP Added CyberArk SIA entry as a VPN-type entry for SSH Added documentation support for SQLite Added Google Workspace console Added IBM5250 terminal Added new "Open with alternate credentials" feature Added portable license feature Added Service Now ticketing when using DVLS Added SSH support to CyberArk SIA Launcher Added support for Delinea Secret Server session recording Release notes: https://devolutions.net/remote-desktop-manager/release-notes/beta/

This version broke integrations with 1Password and BitWarden has similar issues. I have had to revert back to using KeePass integration for credentials. When trying to connect to an RDP session with 1Password configured it prompts the first time for my password for 1Password then throws this error. Also using the Open Session button seems to not work at all with this release. It seems very flaky getting RDP sessions to work the first time. Error with 1Password configured on first launch of any RDP session - [image] Seeing this as well after entering the 1Password unlock password - [image] This message comes up then does not allow RDP to the connection. I need to change the credentials back to KeePass ones before it works. Please address this

Hello everybody, We are happy to release the RDM 2025.3 BETA version. This is a major update and requires a database update. Please back up your database before installing this beta for maximum safety. Please report your issues in a separate thread to simplify the follow-up. We have some additional information depending on the data source you use: Devolutions Server users: DVLS 2025.3 beta is required. It's available here: https://devolutions.net/server/home/download/ Devolutions Hub Business and Hub Personal: The latest beta works with Hub. Download: https://cdn.devolutions.net/download/Devolutions.RemoteDesktopManager.Bin.2025.3.11.0.zip (universal) https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.2025.3.11.0.msi (universal) https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.win-x64.2025.3.11.0.msi (x64-optimized) https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.win-arm64.2025.3.11.0.msi (arm64-optimized) New features: Added an option to allow login to DVLS and Hub through an embedded browser Added MCP server feature (experimental) Added support for entries in vault templates Added support to Bitwarden for fetching SSH keys and using them Added synchronizer for Azure VMs Added synchronizer for JAMF Added synchronizer for NetBox Added WinGet dashboard tool Various additional smaller improvements and fixes Breaking changes: Changed default of password policy and password validation to be handled as inherited instead of going to the system settings directly - Make sure your inheritance structure is appropriate Changed the "force default template" system setting for "lock password policy", which will now lock the configuration for non-administrators rather than only doing so when in "default" mode Internal rework of the opened sessions - we no longer list external processes not opened by RDM Removed alternative view modes for the navigation pane Removed Chrome Remote Desktop entry Removed Dropbox Passwords entry Removed embedded UltraVNC support Removed Kaspersky credential integration Deprecated features: Chrome in embedded mode is deprecated and will be removed in 2026.1 - Use Edge embedded instead Marked Powershell 2.0 as deprecated - We recommend using Powershell 5 or higher Marked RDP/SSH over Delinea Secret Server proxy as deprecated - Use a normal RDP/SSH entry linked to a Secret Server credential entry with mode "Connection through proxy" Marked the certificate document entry as deprecated - Use the more feature-rich Certificate (X.509) credential instead Release notes: https://devolutions.net/remote-desktop-manager/release-notes/beta/

I had thought this article might be somewhat related, but it isn't ( Use multiple Edge website entries with different credentials in Remote Desktop Manager) Just in an effort to have less overall entries in RDM it would be nice if we could link multiple credentials within one entry instead of having to create (web entry1)@blah.com and then (admin-web entry 2)@blah.com etc.

Hi, After upgrading to 2025.2.x, I got "The Hub version (2025.1) and the Remote Desktop Manager version (2025.2) are mismatched." What does it means and how can I fix it ? Thanks in advance. Sebastien

Hello everybody, We are happy to release the RDM 2025.2 BETA version. This is a major update and requires a database update. Please back up your database before installing this beta for maximum safety. Please report your issues in a separate thread to simplify the follow-up. We have some additional information depending on the data source you use: Devolutions Server users: DVLS 2025.2 beta is required. It's available here: https://devolutions.net/server/home/download/ Devolutions Hub Business and Hub Personal: The latest beta works with Hub. Download: https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.2025.2.12.0.msi https://cdn.devolutions.net/download/Devolutions.RemoteDesktopManager.Bin.2025.2.12.0.zip New features: Added "linked (external vault)" feature (SQL Server) Added "Pending approval" workflow including a new status and a way to configure it by default Added new permissions for editing VPN/Tunnel/Gateway and editing Session Recording configuration Added new VPN for Cloudflare WARP Added ServiceNow dashboard Added support for notifications from DVLS Added support for OneIdentity Privileged Sessions Added support for Tailscale VPN Various additional smaller improvements and fixes Release notes: https://devolutions.net/remote-desktop-manager/release-notes/beta/

Hi Hubert, When I try to modify an entry and try to modify the hostname for $NAME$.domain. Local, I got that error. I am using 2025.2.7 with Devolutions Hub Personnal. at Devolutions.Hub.Clients.HubClient.PutEntryAsync(Guid vaultId, Guid entryId, Entry entryToPut, CancellationToken cancellationToken) at Devolutions.Hub.Clients.HubClient.<>c__DisplayClass78_0.<<PutEntry>b__0>d.MoveNext() --- End of stack trace from previous location --- at Devolutions.Hub.Clients.HubClient.PutEntry(Guid vaultId, Guid entryId, Entry entryToPut) at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.SaveConnectionAsEntry(Guid dataSourceID, Guid repositoryID, Connection toSave, Connection[] currentConnections) at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.SaveConnection(Guid dataSourceID, Guid repositoryID, Connection toSave, Boolean forceNoGetCurrentConnections) at Devolutions.RemoteDesktopManager.Business.DataSources.HubConnectionDataSource.SaveConnection(ConnectionEngine engine, Connection connection) [image]

are any docs available yet for configuring the Ai Assistant RDM entry, I am currently attempting to use an Azure Open Ai provider but have been unable to get a response other than errors, my first question is the providers, I see in the drop down several GPT options but the field does take text, I've been attempting to use the model name as stated on azure ' DeepSeek-R1', I have also tried using various endpoint URLs and keys found on AI Foundry but none have worked yet, I will try a model listed in the RDM provider dropdown next but I assumed it would work with any Model / Provider is this not the case? Since AI Foundry also provides multiple endpoint URLs I am left to trial and error. Any guidance would be appreciated for Azure Open AI. Thanks

Found another problem. This one is with Powershell scripts that have worked flawlessly since v2023.x. I get this error in both the installed Beta version, as well as the Portable Beta version: [image] Here is the Script I am running for your reference (error is on the line > $dataSourceList = Get-RDMDataSource): # Declare file & folder variables needed for the script $csvData = Import-Csv -Path "C:\RVTools\RDM Updates\ImportFiles.csv" $OutputPath = "C:\RVTools\RDM Updates\Completed\" # Check to see if the output path exists for the completed csv file If(!(test-path -PathType container $OutputPath)) { New-Item -ItemType Directory -Path $OutputPath } # Fetch all RDM data sources currently loaded to RDM $dataSourceList = Get-RDMDataSource # Prepare a list to hold the results $results = @() # Iterate through each row in the CSV foreach ($row in $csvData) { $deviceName = $row.VM $VMID = $row.VMID $Description = $row.Annotation $SmartResize = $row.SmartResize $customfield1 = $row.CF1 $customfield2 = $row.CF2 $customfield3 = $row.CF3 $ClientTag = $row.ClientCode $AlternateHosts = $row.IPv4 $Virtual = $row.Virtual $vCenter = $row.vCenter $VMType = $row.VMType $oldVMID = $null $oldDescription = $null $oldSmartResize = $null $oldcustomfield1 = $null $oldcustomfield2 = $null $oldcustomfield3 = $null $oldClientTag = $null $oldAlternateHosts = $null $oldVirtual = $null $oldvCenter = $null $oldVMType = $null $updateResult = "Entry Not Found / Mismatch" $updatedDataSource = $null # Display the current entry name being processed by this script Write-host "Checking For Entry: $deviceName" foreach ($dataSource in $dataSourceList) { Set-RDMCurrentDataSource -DataSource $dataSource $rdmSessions = Get-RDMSession -IncludeSubFolders | Where-Object { $_.Name -eq $deviceName } if ($rdmSessions) { foreach ($session in $rdmSessions) { # $oldDescription = $session.Description $oldAlternateHosts = $session.AlternateHosts $oldVMID = $session.VMRC.VMID $oldSmartResize = $session.VMRC.SmartResize $oldcustomfield1 = $session.MetaInformation.CustomField1Value $oldcustomfield2 = $session.MetaInformation.CustomField2Value $oldcustomfield3 = $session.MetaInformation.CustomField3Value $oldClientTag = $session.MetaInformation.Keywords $oldVirtual = $session.MetaInformation.IsVirtualMachine $oldvCenter = $session.MetaInformation.VirtualMachineName $oldVMType = $session.MetaInformation.VirtualMachineType $result = [PSCustomObject]@{ 'Entry Name' = $deviceName 'Old VM ID' = $oldVMID 'New VM ID' = $VMID # 'Old Description' = $oldDescription # 'New Description' = $Description 'Old NIC #1 vLAN' = $oldcustomfield1 'New NIC #1 vLAN' = $customfield1 'Old NIC #2 vLAN' = $oldcustomfield2 'New NIC #2 vLAN' = $customfield2 'Old NIC #3 vLAN' = $oldcustomfield3 'New NIC #3 vLAN' = $customfield3 'Old Tag' = $oldClientTag 'New Tag' = $ClientTag 'Old Alternate Hosts' = $oldAlternateHosts 'New Alternate Hosts' = $AlternateHost 'Old Is Virtual' = $oldVirtual 'New Is Virtual' = $Virtual 'Old vCenter' = $oldvCenter 'New vCenter' = $vCenter 'Old VM Type' = $oldVMType 'New VMType' = $VMType 'Update Result' = "No Change Needed" 'Updated DataSource' = $dataSource.Name } # # Check to see if Description needs to be updated or not. # if ($oldDescription -ne $Description) { # $session.Description = $Description # $result.'Update Result' = "Success" # # Write-Host "Updated ""Description"" from '$oldDescription' to '$Description' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" # } else { # Write-Host "No Change needed for ""Description"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" # } # Check to see if VM ID needs to be updated or not. if ($oldVMID -ne $VMID) { $session.VMRC.VMID = $VMID $result.'Update Result' = "Success" Write-Host "Updated ""VM Id"" from '$oldVMID' to '$VMID' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } else { Write-Host "No Change needed for ""VM Id"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } # Check to see if CustomField1 (NIC #1 VLAN) needs to be updated or not. if ($oldcustomfield1 -ne $customfield1) { $session.MetaInformation.CustomField1Value = $customfield1 $result.'Update Result' = "Success" Write-Host "Updated ""NIC #1 vLAN"" from '$oldcustomfield1' to '$customfield1' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } else { Write-Host "No Change needed for ""NIC #1 vLAN"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } # Check to see if CustomField2 (NIC #2 VLAN) needs to be updated or not. if ($oldcustomfield2 -ne $customfield2) { $session.MetaInformation.CustomField2Value = $customfield2 $result.'Update Result' = "Success" Write-Host "Updated ""NIC #2 vLAN"" from '$oldcustomfield2' to '$customfield2' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } else { Write-Host "No Change needed for ""NIC #2 vLAN"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } # Check to see if CustomField3 (NIC #3 VLAN) needs to be updated or not. if ($oldcustomfield3 -ne $customfield3) { $session.MetaInformation.CustomField3Value = $customfield3 $result.'Update Result' = "Success" Write-Host "Updated ""NIC #3 vLAN"" from '$oldcustomfield3' to '$customfield3' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } else { Write-Host "No Change needed for ""NIC #3 vLAN"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } # Check to see if Tags needs to be updated or not. if ($oldClientTag -ne $ClientTag) { $session.MetaInformation.Keywords = $ClientTag $result.'Update Result' = "Success" Write-Host "Updated ""Tags"" from '$oldClientTag' to '$ClientTag' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } else { Write-Host "No Change needed for ""Tags"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } # Check to see if Alternate hosts (IPv4 Address Reference) needs to be updated or not. if ($oldAlternateHosts -ne $AlternateHosts) { $session.AlternateHosts = $AlternateHosts $result.'Update Result' = "Success" Write-Host "Updated ""Alternate Hosts"" from '$oldAltertnateHosts' to '$AlternateHosts' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } else { Write-Host "No Change needed for ""Alternate Hosts"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } # Check to see if Machine is marked Virtual. if ($oldVirtual -ne $Virtual) { $session.MetaInformation.IsVirtualMachine = $Virtual $result.'Update Result' = "Success" Write-Host "Updated ""Is virtual machine?"" from '$oldVirtual' to '$Virtual' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } else { Write-Host "No Change needed for ""Is virtual machine?"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } # Check to see if vCenter Name needs to be updated or not. if ($oldvCenter -ne $vCenter) { $session.MetaInformation.VirtualMachineName = $vCenter $result.'Update Result' = "Success" Write-Host "Updated ""Is virtual machine?: Server"" from '$oldvCenter' to '$vCenter' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } else { Write-Host "No Change needed for ""Is virtual machine?: Server"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } # Check to see if Virtual Type needs to be updated or not. if ($oldVMType -ne $VMType) { $session.MetaInformation.VirtualMachineType = $VMType $result.'Update Result' = "Success" Write-Host "Updated ""Is virtual machine?: Type"" from '$VMType' to '$VMType' on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } else { Write-Host "No Change needed for ""Is virtual machine?: Type"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" } # Check to see if Smart Resize needs to be updated or not. if ($oldSmartResize -ne $SmartResize) { $session.VMRC.SmartResize = $SmartResize $result.'Update Result' = "Success" Write-Host "Updated ""Smart Resize"" from '$oldSmartResize' to '$SmartResize' for RDM Entry '$deviceName' in data source '$($dataSource.Name)'" Write-Host "" } else { Write-Host "No Change needed for ""Smart Resize"" on RDM Entry '$deviceName' in data source '$($dataSource.Name)'" Write-Host "" } if ($result.'Update Result' -eq "Success") { Set-RDMSession -Session $session } elseif ($result.'Update Result' -eq "No Change Needed") { # $result.'New Description' = $null $result.'New VM Id' = $null $result.'New NIC #1 vLAN' = $null $result.'New NIC #2 vLAN' = $null $result.'New NIC #3 vLAN' = $null $result.'New Tag' = $null $result.'New Smart Resize' = $null $result.'New Is Virtual' = $null $result.'New vCenter' = $null $result.'New VMType' = $null } $results += $result } # -> foreach ($sesion in $rdmSessions) closure } # -> if ($rdmSessions) close else { $results += [PSCustomObject]@{ 'Entry Name' = $deviceName # 'Old Description' = $null # 'New Description' = $null 'Old VM Id' = $null 'New VM Id' = $null 'Old NIC #1 vLAN' = $null 'New NIC #1 vLAN' = $null 'Old NIC #2 vLAN' = $null 'New NIC #2 vLAN' = $null 'Old NIC #3 vLAN' = $null 'New NIC #3 vLAN' = $null 'Old Tag' = $null 'New Tag' = $null 'Old Smart Resize' = $null 'New Smart Resize' = $null 'Old Is Virtual' = $null 'New Is Virtual' = $null 'Old vCenter' = $null 'New vCenter' = $null 'Old VM Type' = $null 'New VMType' = $null 'Update Result' = $updateResult 'Updated DataSource' = $dataSource.Name } # -> PSCustomObject closure } # else block closure } # foreach ($dataSource in $dataSourceList) closure } # foreach ($row in $csvdata) closure #Refresh the running RDM UI Update-RDMUI # Export the results to a CSV file named with the current date $timestamp = Get-Date -Format "MMddyyyy-HHmmss" $outputFileName = "C:\RVTools\RDM Updates\Completed\ImportFile.csv" $results | Export-Csv -Path $outputFileName -NoTypeInformation # Write-Host "Results have been exported to $outputFileName" HOWEVER... I found that enabling "Load RDM CmdLet" which I have never had to enable before got it working: [image] In the Portable version of v2025.1.11.0 Beta I get the same results. However, in the latest Portable v2024.3.28.0, it works perfectly fine as it has since I implemented in middle v2023 without that option checked. [image] What changed? Should this be enabled by default?

Good morning, folks. I believe you may have a huge boo-boo in your release notes that I saw in the new beta release I updated to: "Breaking changes: Changed license validation URL from https://api.devolutions.com to https://quoting.devolutions.com . Make sure your network allows access to this URL." Shouldn't those URL's be .NET instead of .COM?

Good afternoon. Has anyone else reported the Navigation Bar automatically shrinking and having to re-expand it in order to make sense of anything that's in there? I am currently set up with this view: [image] After some clicks here and there (doesn't seem to be just one thing that makes it do it) I now have went to this view: [image] One time it did it I minimized RDM and when I expanded it, it was that new view. Another time I clicked from my Favorites list to the Navigation list. There is honestly no rhyme or reason as to why it does it.

Good morning. I thought I remember reading on one of my past posts somewhere, that the Background A/D Syncs utilizing KeePass linked credentials would be fixed by this version release. However, they still return a result code 49. [image] [image] Will this ever be something that is fixed?

Good afternoon. I was wondering if there is a way of doing a Batch Add Attachments? Maybe I am missing a setting somewhere or something, or maybe it's not possible... I highlight the entries I would like the PDF to "attach" to and the "Add Attachment" is greyed out: [image] I did the "Add Document" and it attached it under the parent folder which is fine I guess, but I would rather have it show at the attachment tab for each entry if at all possible. Maybe it's not possible to keep the size of the Database down from attaching the same file over and over and over again for 14 entries? Thanks!

Good morning. Just came across something else that needs to be addressed in the beta. I verified this is an issue on both my installed version and the portable beta: [image] That screen looked like this in v2024.3.28.0: [image] The circled ones have just up and vanished from the beta.

I believe the following need to have additional paths added to the "Installation Path", as the newer versions target the following directories: VMWare Workstation: C:\Program Files (x86)\VMware\VMware Workstation VMWare Player: C:\Program Files (x86)\VMware\VMware Workstation VMWare Infrastucture Client / vShere Client: This software was discontinued by VMWare before they got bought by Broadcom SQL Server Management Studio: C:\Program Files (x86)\Microsoft SQL Server Management Studio 20\Common7\IDE Chocolatey: This installs as "choco.exe". Therefore, even though the paths are correct in RDM Installation Path lists, it looks for "chocolatey.exe" and does not recognize the program is installed. Thanks!

Hi, I think there is an issue when we edit entries. Please check screenshot below. [image] [image] Can you reproduce the issue ?

Good morning. Just upgraded to v2025.1.11.0. First off, want to say THANK YOU for finally pushing the update to show User Vault Expiring entries. This is EXTREMELY helpful. However, I have found an issue with ONE item and that's the "Checkouts" List. [image] As you can see, I have everything (except one Never) set to "If not empty": [image] The list shows 0 checkouts so therefore, it shouldn't be displayed. Otherwise, haven't found any issues with the Dashboard for either System or User vault. Showing my user vault settings for reference here: [image] Only suggestion I can think of, is maybe (if feasible) is to have a growing window? You can see my Expiring entries has a scroll bar. It would be nice to see them all without having to scroll. Maybe an option in settings to show how many entries appear in all the windows?

Another one... Problem in both installed and portable version. Website entries no longer pass username and password to the entry. The autofill button on the top of the toolbar (key looking icon) doesn't work either like it used to when the issue persisted. I have tried both Inherited from the parent folder that has KeePass entries linked, as well as Username and Password variables. Neither work. However, loading the database in v2024.3.28.0 portable works perfectly fine as expected.

Another problem found... Website entries. If you have the option to "Force https" enabled, RDM automatically adds three https:// to whatever URL is listed. [image] If you uncheck that option and correct the URL listed, it operates as normal: [image]

Hello, since the update two days ago (2024.3.16.0 64-bit), the application has been crashing frequently. This happens when I try to establish an RDP connection. I didn't have this problem with the previous beta. Fehlerhafter Anwendungsname: RemoteDesktopManager.exe, Version: 2024.3.16.0, Zeitstempel: 0x66e80000 Fehlerhafter Modulname: mstscax.dll, Version: 10.0.27729.1000, Zeitstempel: 0x46937feb Ausnahmecode: 0xc0000409 Fehleroffset: 0x0000000000001d91 Fehlerhafte Prozess-ID: 0x3168 Fehlerhafte Anwendungsstartzeit: 0x1DB2C428F9C482D Fehlerhafter Anwendungspfad: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe Fehlerhafter Modulpfad: C:\WINDOWS\system32\mstscax.dll Berichts-ID: 95101a55-4f84-4030-a731-205b4a5ca102 Vollständiger Name des fehlerhaften Pakets: Fehlerhafte paketbezogene Anwendungs-ID: Best regards, Oliver Braun

After installing the Beta 2024.3.5 the KeePass plugin DLL file is no longer compatible with KeePass 2.x. I was prompted to upgrade the plugin and did so then when launching KeePass get the following message about incompatibility and the plugin is disabled. This needs to be addressed ASAP as I use KeePass as my credential manager for RDP sessions daily. Issue launching KeePass - [image]