Forum Discussion
Remote assistance with Quick Assist is changing
This is a real problem for us. 3/4 of our users are on 1809 LTSC; the old program is disabled and the new app doesn't work. It installs but we get the same elevation errors as above. The Already installed link either isn't there or spins forever when clicked.
We pay good money for Enterprise licensing and 1809 LTSC is still under full support. You shouldn't just unilaterally remove features from it. In fact, this was a big reason for choosing LTSC. We need it fixed.
- bouda05Jun 07, 2022Copper ContributorTotally agree with you. LTSC is only version which you can use in production and easy way to get support for users is Quick Assist. Too bad that there is no hack how to use old or new app on LTSC edition. Microsoft focus only for profit and online world in last years 😞
- jcjcjcJun 09, 2022Copper Contributor
Hi all, just wanted to let you know a workaround we have noticed when updating quick assist on 1909 to the new app.
We were getting the requires elevated permissions error after installing the new app and then opening from the start menu. However, if you open the old app, and then click the bit at the bottom saying if you've already installed it, open here, it will open the app successfully. This seems to be related to the permissions set on the WindowsApps folder in program files, it seems users don't have permission to access this which prevents the new app from opening, but if you open it through the link in the old app, it bypasses those folder permissions.- FrankPanaroJun 13, 2022Copper Contributor
I just noticed that error today also after pushing the new QA with GPO. I ended up having them do the feature update which took them to 21H2 and then the new QA worked fine, so it must reset rights to that folder I bet. Thanks for the extra info though, that explains a lot. 🙂 jcjcjc