# Bug in Royal TS 26 Beta 21

**URL:** <https://community.royalapps.com/t/bug-in-royal-ts-26-beta-21/2370>\
**Category:** Royal TS (for Windows)\
**Created:** [August 17, 2026, 1:46pm UTC](https://community.royalapps.com/t/bug-in-royal-ts-26-beta-21/2370 "2026-08-17T13:46:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rene](https://community.royalapps.com/user_avatar/community.royalapps.com/rene/32/1642_2.png) [@Rene](https://community.royalapps.com/u/Rene)\
**Post date:** [August 17, 2026, 1:46pm UTC](https://community.royalapps.com/t/bug-in-royal-ts-26-beta-21/2370/1 "2026-08-17T13:46:16Z")

</div>

I possibly found a bug in Beta 21 of Royal TS for Windows version 26.

When opening an RDP connection with “Connect with options” and “Prompt for credentials” activated, Royal TS v7 correctly shows the prompt with all saved credentials.

 ![image](https://community.royalapps.com/uploads/default/original/2X/2/20462700965a87e3944974604baccedfacc1e641.png)

Doing the same in Beta 21, gives empty usernames and path columns.

 ![image](https://community.royalapps.com/uploads/default/original/2X/2/21ce7c17a99db3b62bb001a8df815ed79a0371fa.png)

Choosing one of those records and pressing OK, gives the following error message.

 ![image](https://community.royalapps.com/uploads/default/original/2X/2/2964149cc2628a7e5973a9390be436569d3832f2.png)

This did not happen with Beta 20 before.

---

<div class="post-metadata">

**Author:** ![stefan\_koell](https://community.royalapps.com/user_avatar/community.royalapps.com/stefan_koell/32/9_2.png) [@stefan\_koell](https://community.royalapps.com/u/stefan_koell)\
**Post date:** [August 17, 2026, 6:38pm UTC](https://community.royalapps.com/t/bug-in-royal-ts-26-beta-21/2370/2 "2026-08-17T18:38:59Z")

</div>

Thanks for reporting this. We’ve fixed this for the next build.

---

<div class="post-metadata">

**Author:** ![christoph\_muehlberger](https://community.royalapps.com/user_avatar/community.royalapps.com/christoph_muehlberger/32/1572_2.png) [@christoph\_muehlberger](https://community.royalapps.com/u/christoph_muehlberger)\
**Post date:** [August 19, 2026, 1:34pm UTC](https://community.royalapps.com/t/bug-in-royal-ts-26-beta-21/2370/3 "2026-08-19T13:34:24Z")

</div>

Hello Rene,

Our lead-dev Stefan looked into this, and we just finished testing the latest Royal TS V26 - Beta 22 build, which fixes the issue.

Could you please test if this fixes the issue for you as well?

You can download the latest build here:

**Install version**

[https://download.royalapps.com/royalts/royaltsinstaller\_26.0.22.0\_x64.msi](https://download.royalapps.com/royalts/royaltsinstaller_26.0.22.0_x64.msi)  
[https://download.royalapps.com/royalts/royaltsinstaller\_26.0.22.0\_arm64.msi](https://download.royalapps.com/royalts/royaltsinstaller_26.0.22.0_arm64.msi)

**Portable .zip version**  
[https://download.royalapps.com/royalts/royalts\_26.0.22.0\_x64.zip](https://download.royalapps.com/royalts/royalts_26.0.22.0_x64.zip)  
[https://download.royalapps.com/royalts/royalts\_26.0.22.0\_arm64.zip](https://download.royalapps.com/royalts/royalts_26.0.22.0_arm64.zip)

Or alternatively update via the In-App updater.

Best regards,  
Christoph

---

<div class="post-metadata">

**Author:** ![Rene](https://community.royalapps.com/user_avatar/community.royalapps.com/rene/32/1642_2.png) [@Rene](https://community.royalapps.com/u/Rene)\
**Post date:** [August 19, 2026, 1:51pm UTC](https://community.royalapps.com/t/bug-in-royal-ts-26-beta-21/2370/4 "2026-08-19T13:51:40Z")

</div>

Hello Christoph

Just downloded and testet it. I can confirm, the bug has been fixed.

Thank you very much for your effort 🤣
