Forum Discussion
AVD Remote App Running instance not displaying in taskbar after Client update to 1.2.3130
Good Day - I was wondering if anyone has experienced issues with Remote app programs not displaying in the taskbar after users have launched them. This is causing issues for Laptop users with single screens as they have no way to bring the remote app back up if they minimized the window to use another program. Using ALT+TAB also does not show the remote app window either. Currently they have to go back to the Windows Desktop Client and click on the app icon again to bring up a new window and connect back to their existing session. Has anyone experienced this before or has any troubleshooting steps I can try?
Our Host Pools are running Agent Version 1.0.4452.2100, FSLogix version 2.9.7979.62170
Using Azure Storage for profiles. Remote Apps are Line of Business software and O365 (Excel, Outlook, Word ect) We started seeing this after the Client updated to 1.2.3130. Rolling back has fixed it for most of our users.
40 Replies
- KrishnaNidriCopper Contributor
Doing a restart of virtual desktop helped. Brought back toolbar and other icons on reconnect.
To restart, used windows + R for run command and opened command prompt(cmd). Then applied command 'shutdown -r'.
This will take couple of minutes. Tried connecting to VD and noticed everything is back(toolbar and icons).
- KamranAhmed1Copper ContributorTry Rolling back the client version and see if it fixes the issue.
- Luis_Del_RiscoCopper Contributor
Any news from Microsoft? the issue persists independent of many of the workarounds listed here..
If anyone have news please comment
Thanks in advance
- JBowserCopper Contributor
Luis_Del_Risco Since upgrading to the latest desktop client (1.2.3213.0), we have not experienced this issue.
- TrebkeBrass ContributorThats strange indeed. We have to disable the RemoteFX GPO otherwise a few application won't show up we also still have version 1.0.4452.2100. I check with MS again. For us its fixed, but what? Something in a broker maybe..?
- TrebkeBrass Contributorjust had a call with MS and the fixed it in the Agent. So after rebooting a host it should work. We are still on 1.0.4452.2100, probably fixed with a hotfix
- LGADMIN545Copper ContributorThat's good to hear. I will make sure my pool reboots tonight and test it. It would be great if they have it resolved now.
- JimbowBrass Contributor
Mhm crazy, we have new remote client version 1.2.3213.0 and rdagent 1.0.4452.2100 too and do some reboots. Nothing changed 😄
But maybe you have a private fix on your tenant...I will activate validation environment on the host pool in our test environment. Maybe there is the fix.
- JimbowBrass Contributor
validation env rdagent 1.0.4739.800 does not work too. Strange that solved your problem
- TrebkeBrass ContributorNew update available! https://docs.microsoft.com/nl-nl/windows-server/remote/remote-desktop-services/clients/windowsdesktop-whatsnew
Tested this morning, first test are hopeful! No reaction from MS till now...only to deliver AVD-collect- JimbowBrass Contributor
No one from the workarounds doesn't work for us 😞
- fEnableRemoteFXAdvancedRemoteApp = 1
- new version 1.2.3213.0 not fixed
- 1.2.2927 not fixed, Autoupdate regkey not working in HKLM or HKCU 😞
- HiDef RAIL (alt + tab) not activated, see no thumbnail with fEnableRemoteFXAdvancedRemoteApp = 1 or fEnableRemoteFXAdvancedRemoteApp = 0
I think they changed something on the remote desktop client and backend. That's why old versions no longer work for us. I hope the new AVD Collect logs, will bring light into the dark!
- Xandven_Copper ContributorWe are getting closer to a solution. If the AVD Web Client is working ok, then
GPO: Administrative Templates/Remote Desktop Services/Remote Desktop Session Host/Remote Session Environment [Use advanced RemoteFX graphics for RemoteApp] (or the corresponding registry key) might be causing the issue if set to disabled. Try changing it to Enabled (or not configured).- James PriceCopper Contributor
Xandven_ This is the fix that we used with Microsoft Support. We deployed it to all our session hosts and it resolved the issue for now until Microsoft comes out with an update to resolve the issue. Also another workaround if you have a smaller environment is to download the Remote Desktop Client to 1.2.2927.0 if you can find it. If you have a large environment with lots of Remote Clients deployed i would suggest the GPO.
- Pedro_AravenaCopper ContributorHi James, do you have Remote Desktop Client 1.2.2927.0 download link ?
Thank you !
- JBowserCopper ContributorOur DevOps Engineer found this documentation on MS....
https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/windowsdesktop-admin
According to this documentation, it looks as though the update is controlled via registry settings.- JBowserCopper ContributorTo disable the update, we had to set the following registry key before installing the previous client.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSRDC\Policies]
"AutomaticUpdates"=dword:00000000
We'll go back in and remove this after the issue is fixed by Microsoft.
- JBowserCopper Contributor
Has anyone else now experienced the rolled back clients automatically updating to the latest release? This didn't happen before -- users were also prompted with notification that an update is available. We're now stuck in a loop of having to constantly reset and reinstall to keep users up and running. Suffice it to say, users (and paying clients) aren't happy.
We did hear back from MS that they've acknowledged this is a bug and are fixing it, but they haven't given an ETA.
- Xandven_Copper Contributor
LGADMIN545 We are seeing and increase in this issue this week. Only solution that works for us is rolling back to the Windows Remote Desktop Client v1.2.3004. Webclient and store app works fine, but as we depend on the Windows client it does not help us. We have a open ticket at high priority with Microsoft and apparently they are working on a fix.
- JBowserCopper ContributorWe have to fix that at each client machine. We have to reset user data, uninstall the desktop client, install an older desktop client to fix the issue. MS did not respond to the case we opened yesterday afternoon, but I have updated the case with our resolution.
Some of us have been on this latest client version since it was released without issue until now. I suspect MS updated some kind of service consumed by these newer client versions.
Although we haven't tested every client out there, this appeared to be limited to the desktop client only. The web client, Microsoft Store client, and iOS clients all worked as expected.- JimbowBrass Contributor
I can confirm, that WebClient and MS Store Client are working fine! MS Store Client is only showing the red MSRDC Icon on taskbar but better then nothing 😄
So, that's for sure, this issue is from newer Remote Desktop Client versions!
Ticket Status: We have sent the entire Remote Desktop Client logs via a special MS script (MS sent it to me) and are awaiting feedback.
- TrebkeBrass ContributorSame problem here. Also created a support case.
- LGADMIN545Copper ContributorIs anyone getting anything of value back from their support cases?
- TrebkeBrass Contributor
LGADMIN545 only that the productgroup is aware of the problem and there working on a fix. 1.2.3004 and lower are working fine.