2026.3.x unable to review access requests

A fix for this issue has been implemented in version 2026.3.13.0
Implemented

2026.3.x unable to review access requests

avatar

hi, I'm currently using 2026.3.10 on Windows 11. I had/have an issue I can't consistently reproduce (yet). It started after our migration from 2026.2 to 2026.3.

After the upgrade, I initially installed 2026.3.8 and in my dashboard I saw several access requests. But when I click to review, the list is empty.
Refreshing, (un)docking or restarting RDM doesn't work.
I saw 2026.3.10 was available. Upgrading the client did fix the issue...

...until this afternoon. In my dashboard I see again several access requests, but the list for review is empty again.

What did work this time was switching to another data source (same SQL source but admin-UPN) does give me back the list.
My daily-UPN should also have the right permissions, so switched back, still got the list and I'm able to approve/deny.
Even after restart of RDM, the list is available.

So, as I'm not sure why it doesn't display sometimes and when/why it does show, I can't give you exact steps to reproduce at the moment, but it happened twice.

RDM 2026.3.13.0 + Azure SQL datasource
HUB Business

All Comments (2)

avatar

Hi Paul,

Thank you for reaching out and for reporting this issue.

We were able to reproduce the behavior you described, and we can confirm that it’s an issue that will be reported to our development team for further investigation.

We appreciate you bringing this to our attention.

Please don't hesitate to ask us any other questions.

Best regards,

Alexis Geller Peiro

avatar

Hello,

Thank you for your patience while our team looked into the issue you reported.

I'm happy to let you know that the latest version of Remote Desktop Manager (2026.3.13.0) includes a fix for this problem. You can download it from our website here:
https://devolutions.net/remote-desktop-manager/download/

Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists, or if you notice anything unusual related to the same original problem, just reply to this email with a few details, and we will be glad to look into it further.

Thank you for your collaboration.

Best regards,

Érica Poirier

A fix for this issue has been implemented in version 2026.3.13.0