I updated to 10.1.4 but now receive the following error message every time I try and open a pdf document "There was an error during initialiazation. Failed to load an appliaction resource (internal error). This is preventing me from using pdf's. I have removed and then re-installed 10.1.4 and also tried to repair the installation but still receive the same message. I restored back to 10.1.3 which worked perfectly but logged on this mornng for adobe to automatically update to 10.1.4 and now I have the same problem. Is there a bug in the update?
I solved my problem by un-installing again and then using adobe cleaner (found the link on another question about 10.1.4) which looks like it really does un-install everything and then re-installed. Now seems to be working okay but will be using it a lot today, so we will see
I have cleaned up my Adobe Reader and reinstalled it but the problem persists. Version 10.1.4 has reintrouced an old and very serious bug (see http://forums.adobe.com/thread/391798). It is unusable. We need a bug-free Version 10.1.5 ASAP. Thanks.
Hi Nikhil, your latest post above says, "... If you require an urgent fix for this issue, you should report it through the support team and request a hotfix for Adobe Acrobat/Reader 10.1.4 or 9.5.2." Kindly send me the hotfix for Adobe Reader 10.1.4 or let me know how to contact your Support Team ASAP. Thanks, Avner
This particular issue has been logged for tracking, while we design, build and test a proper solution. But, since each release must balance the needs of all of our customers, especially when security fixes are involved, an issue can be delayed from one update to the next. Therefore, we cannot provide an exact timeline until the fix has been officially submitted into our production build process, which unfortunately, is not the case at this time. If this issue is blocking your workflow, please try the workaround provided in the blog mentioned, while we continue to work on a fix.
Poor Nikhil Gupta is not to blame for this debacle. He has his boss. The responsible person is Adobe CEO Shantanu Narayen (see http://en.wikipedia.org/wiki/Shantanu_Narayen). I have forwarded many of the messages on this forum to Mr. Narayen. He has not made a single response. If anyone needs to take responsibility for this egregious failure, it is Mr. Narayen. But he does not care. Adobe makes much more money from Photoshop than from Adobe Reader. Take heart, however. Windows 8 has its own built-in PDF viewer (see http://www.winsupersite.com/article/windows8/windows-8-feature-focus-w indows-reader-142710). You will no longer need Adobe Reader.
Windows 8 has its own built-in PDF viewer (see http://www.winsupersite.com/article/windows8/windows-8-feature-focus-w indows-reader-142710). You will no longer need Adobe Reader.
I don't think anyone is going for that OS; people will skip it as we skipped Windows ME and Vista. And if that built-in PDF viewer is as good as the one in Mac OS, then we will continue to need Adobe Reader.
Not necessarily. The are several good non-Adobe PDF viewers out there (see http://www.techsupportalert.com/best-free-non-adobe-pdf-reader.htm#Qui ck_Selection_Guide). The fact that Adobe has yet to fix this issue is mind-blowing. You can write a note to Adobe CEO Shantanu Narayen (firstname.lastname@example.org) to thank him for his "excellent" customer service, but he is probably thinking of his Photoshop customers, who pay for their software, and not of Adobe Reader users, who don't. However, he got McAfee to pay for it by offering to push its software along with Adobe Reader (see http://get.adobe.com/reader/).
You could try if the latest Reader XI still shows the same behavior; currently only available from the Adobe FTP site ftp://ftp.adobe.com/pub/adobe/reader/win/11.x/11.0.00/
Acrobat engineering would like to inform users facing this issue that the latest Reader XI release (available for download from http://get.adobe.com/reader) fixes this problem. Users are requested to download the latest version at the earliest to avoid encountering this error going forward. As mentioned earlier, the team is working actively towards fixing the problem in earlier versions (10.x and 9.x) as well and expects to deliver a solution by Q1 2013.