ISSUE - Windows App (Android) - Input latency and frozen screens with RemoteApps and handhelds
Good morning, ladies and gentlemen,
TL;DR: Current Windows App for Android changed something in the background, causing massive latency issues while input.
an announcement from end-user point of view. We are having performance and latency issues for almost eight weeks now with the current Windows App (Android). The issues are showing massive performance latency while giving input to a RemoteApp-connected Windows Terminal Server (WS2022DC).
For troubleshooting measurements, we went through EVERYTHING... Changed GPOs for connecting only via TCP instead of UDP, cleared user profiles, even provisioned new VMs with new update states, went back to March updates.
I never thought, I had to change App version (make this in an enterprise with about 100 handhelds, specifically assigned for warehouse and delivery management) to last January to solve those issues...
We definitely need more transparent patch notes (really Microsoft? 2026 and you push updates without any release notes published, not even known issues?!) and a way to downgrade versions without re-provisioning the whole RDP client for Android...
I am looking forward to hearing from other parts of the world, using RemoteApps with Android handheld scanner and RDS2022.
Best regards,
xSOU1 | Jules
6 Comments
Hi all,
Just want to confirm we're seeing the exact same issue - input latency and frozen screens with the Windows App (Android) on over 100 Zebra handhelds. Started after one of the recent app updates.
We've had an open case with Microsoft for weeks now, and it keeps getting bounced between teams without much progress.
Unlike some of you, a manual downgrade isn't an option for us - our devices are managed, and we're the only logistics center within our group (MediaMarktSaturn) currently running the Windows App on Zebra devices, so we can't just change the version on our side. We need an actual fix from Microsoft, not a workaround.
Heyho,
if downgrading is no option (because of compliance, probably), I'd suggest searching for an alternative app which can provide the required stability for your workload.
Regarding black-coffee's comment to xtralogic rdp. Take a look at it, there's a 7-day-trial. Maybe it fulfills your requirements instead.
I can only say this much, as a PoC, I tried to push the functional version with a repackaged file to escape the Play Store limitation and the scanner worked ever since. There's no warranty regarding this method and it can cost you your Play Store account so NEVER EVER IN PRODUCTION!
Only manual integration... Touching all scanners to deploy the old app was a pain in the ...
Have a nice weekend.
Best regards,
xSOU1 | JulesDon't expect any fix from Microsofts side, since it's a free app;) We switched to using xtralogic rdp. Paid solution, but WITH support and more configuration options.
You should ask you IT partner who manages your devices to do the downgrade.
Had many issue on many Zebra devices. Only fix was a rollback to version 11.0.0.87 and manual configuration of each device :(
I am also getting the same, however we only have 8 Zebra scanners. Its very frustrating and nothing seems to help, which is leading me down the path of it being an issue with the Windows App for Android.
EDIT: MS - please join the AppConfig community and add a template for EMM and Windows App to centralize re-enrollment of MS apps...
Hey mate,
I got surprisingly a response on my mail I sent to the linked address on their play store entry of the Windows app.
I sent them all information regarding the issue, occuring on which version, a recording of the issue happening and debug logs from an affected device.
But I can confirm that since rolling back manually to the former version 11.0.0.76 (update state January 2026), the issues are gone.
To be honest? 8 devices are not that crazy instead of 70 devices, separated on three locations around Germany...
Don't give up, you got this.
Best regards,
xSOU1 | Jules
