answering only modifies registry keys inside HKCU, for some reason Foxit Reader prompts for UAC. While this modification of default application occurs even without elevated privileges i.e. (Naturally users never remember answering.) It seems that the UAC prompt is caused when Foxit Reader checks whether it's the default viewer for PDF files or not and the user answers.

Here's a solution both with and without using the ADM template. It's still possible to maintain Foxit Reader deployment without the ADM template, but it would have made solving this a lot easier. Has anyone here already researched this? What is it trying to modify? Will using the group policy template (or a particular setting in it) prevent Foxit Reader from doing this? Or would it be possible to just change/add some registry key that would satisfy Foxit Reader on its startup? The main problem here is the reduced user experience (and all the unnecessary helpdesk tickets). I believe there shouldn't be anything that would need elevated rights, since Foxit Reader starts just fine even if the UAC prompt is closed. Lately (I'd say versions > 8.0) there has been more problems after updates: occasionally the Foxit Reader prompts for UAC when a user starts it. Foxit Reader installed & updated nicely (via Computer Configuration > Policies > Software Settings > Software installation) and worked just fine for years. for this purpose), the group policy templates (. Therefore, while the Foxit Reader has been deployed via Group Policy using the MSI package (provided by Foxit Software Inc. In a couple of AD environments there has been no reason to centrally modify or force any setting of Foxit Reader.

Foxit reader update settings