Hi All
It looks for us that the Vault search/change handling has beend changed since new 2026 version.
Before 2026:
With new 2026:

Is it possible to get the old behaviour back? We have all become very accustomed to the old way of dealing with several hundred vaults, and it was very intuitive, which it no longer is.
Furthermore, the dropdown menu no longer automatically scrolls to the active vault when I open the vault selection.
Best Regards
Andreas
2ef556a7-f660-4c6e-a2b7-38c5e07d6bed.png
I have noticed something like this, too, when using search from the status bar.
Previously, after entering a search I was able to use arrow keys then enter to launch a session. I was also subsequently also able to hit tab+space to accept a windows EULA.
Neither of these are possible now without a mouse click.
Hello Andreas and JackOats,
Thank you for reporting this and for the clear details.
A new build was released yesterday, and this issue should now be fixed after updating.
In the meantime (or as an alternative), you can use Ctrl + Enter after typing your filter to trigger the same vault switch action you previously had with Enter.
If you still see the behavior after updating to the latest build, please let us know.
Best regards,
Eduard Sepulveda Lopez
Hello Andreas and JackOats,
Thank you for reporting this and for the clear details.
A new build was released yesterday, and this issue should now be fixed after updating.
In the meantime (or as an alternative), you can use Ctrl + Enter after typing your filter to trigger the same vault switch action you previously had with Enter.
If you still see the behavior after updating to the latest build, please let us know.
Best regards,
@Eduard Sepúlveda López
With RDM 2026.1.11.0, 12 and 14 still the same issue as posted in first post.
Not able to navigate with Keyboard. Also Ctrl+Enter dont work at all.
Best Regards,
Andreas
Edit: It also still not scroll to the currently active Vault in select field as it did in the 2025 Version.
Hi @Eduard Sepúlveda López
Following up on my previous post - Ive tested builds 2026.1.11.0, 2026.1.12.0, and 2026.1.14.0, and the issue persists in all of them:
Is there a ticket reference for this, or can you let me know the current status? With several hundred vaults, this is a significant workflow regression for us.
Best regards,
Andreas
Hi Andreas,
Thank you for your message and your patience.
We have confirmed the regression in the 2026 versions, and our developers are currently working on a fix. We will keep you updated and let you know as soon as the correction is available in an upcoming release.
Best regards,
Eduard Sepulveda Lopez