This is an issue that has been going on for many versions. I tried to draw Adobe's attention to it many times, many other users also had this problem, but now there's reader 11 and it's still the same.
In the MSI installation the location of PDF icon is hardcoded as [windowsfolder]installer\[productcode]\pdffile_8.ico . If the installation is performed per-user, such as by GPO, then this location is invalid, and the result is generic Windows icon of the PDF files.
I wonder, why is this not addressed?
More generally speaking about this installation, the hardcoded icon is gross violation of best Installer practices, and more specifically, this approach makes impossible adversiting of Reader and install-on-demand. The extension .pdf should be advertised in the installation by normal Installer means. All this, as I understand, because Adobe wants to give the users a choice of Acrobat vs. Reader being the default handler of extension pdf - for those users who have both. Given the fact that percentage of such users is small, and that even among them the percentage of those who will actually appreciate and use this choice is negligible, I wonder, is it worth to sacrifice advertising, install-on-demand, and even self-repair to this choice?
In my records I see that I tried to have this issue addressed back in 2009, and I received the following reply from Adobe's Chief Software Architect Tom Malloy:
===========
Vadim,
I just want to let you know that I forwarded your message to Acrobat quality engineering. They confirm that they know of this shortcoming. It is something we would like to fix but we have not made a decision to prioritize the engineering required, at least yet.
My QE contact is checking with Acrobat program management to see if there is any additional information. If I hear anything more that is worth sharing I will pass it along.
Thanks for making the effort to get through to me. Sorry I can't give you a firm commitment regarding when we will make this better.
Regards,
Tom Malloy
Sr. Vice President
Chief Software Architect
Advanced Technology Labs
Adobe Systems, Inc.
===========
So, 3 years ago Adobe was already aware, but still haven't found the time to prioritize the engineering. Ironically, apparently there was no shortage of engineering talent to implement all these hardcoded workarounds and thus to break the installation standards.
Vadim Rapp