Forum Discussion
Azure VM - RemoteApps Mouse Focus Issue
Jeff_Heathman - we're seeing the same issue across many AVD installations, all starting on the 16th. We haven't found the common denominator yet.
We restored an AVD on Friday (from Thursday night) and the problem went away - and was back this morning. No windows updates or other Windows level updates. We're leaning towards the AVD stack.
Have you had any luck with this?
Doug Johnson - We have seen this weird focus issues as well which seems isolated to the RemoteApps. I first notice a few weeks ago after the 'Remote Desktop Services SxS Network Stack' was auto updated to 1.0.22.07.18300. I downgraded to 1.0.2206.28300 and it had been fine for a week.
However it appears the session hosts have been auto updated again this weekend to 1.0.22.08.17178 and the problem is back but it now appears intermittent as not all users are reporting a problem. The first time it happened everyone noticed!
Please can you explain to me how you downgraded? I had the same issues and i found that by changing the winstation reversedlistener to the older version the problems went away. But now the issue is that only the new version of the SxS driver is installed on the session hosts. This will result in SxSListernerChecks during boot.
I really want to know how to downgrade and lock the downgraded version. The new focus bug have a very high impact on our customers.
- Hi, did anyone figure this out?
- I would like to know too as we are having the issue also
MarcusE2 We see similar weird issues after replacing Windows 10 hosts with Windows 11 hosts. And only when our application is used as RemoteApp.
Did you find any solution to this problem?
Henrik82 Sorry I did not. It's still happening in our environment. I was hoping a newer version of the SxS network stack would fix the issue but I've just checked and we are now running 1.0.2208.17300 which installed 5 days ago.
Luckily for us its only IT who use RemoteApps at present and we are simply minimising the remoteapp when we aren't using it. Not a fix but it's a work around for us. If we had users affected, then I would have treated this as a higher priority. I think it's time for a Microsoft ticket!
