First of all, thanks to those who pm'd me. Let's keep the mods happy and just focus on the app itself. As I stated earlier, my install resulted in a new Acrobat menu appearing in Office 2010 and a drop-down window in Firefox. So far no one else has confirmed this is standard procedure but I doubt I'm the only one to notice them. Since I keyed in the serial after first installing it as a trial, could this be the reason? Anyone done a customized install and still get these menus? One thing I noticed is that there is no difference in file size when using Word's 'save as pdf' feature vs the new acrobat 'create pdf' command. Before, saving as a pdf would result in a larger file than if I sent the file to the acrobat printer. The app itself is lightning fast, opens instantly, and has no lag at all on a win7 64bit system. Share your thoughts guys!
Just choose to skip the registration nag. It should only ask you one or two times. FYI, it's now up on WZOR (includes CORE keygen)
Your OS is the same as mine so it should work. I installed it as a custom install (this time used core's keygen, which works great) on my laptop and the Acrobat menu appears in Office (after the "view" menu tab) the same as on my desktop. I have no idea why it's not showing up and I doubt it's got anything to do with OS or Office versions.
Ruixituh, try this. In MS Word, go to File--Options--Add-ins. At the bottom where it says Manage 'COM Add-ins' click 'Go'. In the new window if you don't see a listing for "acrobat pdfmaker office com addin" then click on 'add' and browse to: C:\program files (x86)\adobe\acrobat 10.0\pdf maker\office" and choose "PDFMOfficeAddin.dll" and set the behavior to "load at startup" and it should show up in the office menu.
Hi I have the same problem Machine = Windows 7 64 bits + Office 2010 64 bits + Acrobat X Pro, the Office add-in is a addons 32 bits and not 64 bits addons ==> you can't create a pdf from a docx file in the explorer with the right click and make a pdf ==>error File missing PDFMAKER would you like to repair the installation ? The Office add-in is a addons 64 bits doesn't exist today!
Hash for the keymaker-CORE Hi Hash for the keymaker-Core CRC32: 5A8DBF64 MD5: 12216BE253EF8F6C4DFAF1669027EF27 SHA-1: 31C37DFACBA3515D4F14356BE63042726BB652BD
The approach with v9 was as follows (assuming its the same with vX10): You should disable automatic updates (Edit -> Preferences -> Updater = "Do not download or install updates automatically") Any updates can be downloaded from the Adobe website (Downloads -> Product Updates -> select Acrobat X Pro from drop-down menu). Save updates to your HDD and start installer manually. Not sure if the manual approach is really any different since your computer must be connected to internet for the update to install. Regards
Update 9.4.1 for acrobat 9 is out. As to updating 9.0, as noted disable auto updates, manually download update, then apply, and then patch adobe.dll. Also run activation blocker as an extra precaution. That used to do it for me all the time. As to x (ver. 10) the new version is just out, and it is not adobe's usual policy to have a Patch Tuesday. Could be a few months before the first update to x pro comes out. That is a long time and one could expect some workarounds by then.
Do you have Office 2010 x86 or x64 installed? The Acrobat add-in to Office 2010 is 32-bit and will NOT work with an Office 2010 64-bit installation. This is precisely why Microsoft always recommended people install Office 32-bit - even on 64-bit systems. If your Office 2010 is 32-bit then I don't know why the add-in isn't working. Did you thoroughly uninstall any previous version of Office and Acrobat? Regards
You may find this useful, copy and make an cmd/bat file and place within the same folder as your updates... msiexec /update AcroProExupd910_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd911_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd912_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd913_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd920_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd930_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd931_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd932_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd933_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd934_all_incr.msp REBOOT=SUPRESS /QB msiexec /update AcrobatUpd940_all_incr.msp REBOOT=SUPRESS /QB pause may be of some help for you?
Yes, this would be of help, with the last line addition for 941.... However, I have bit the bullet and clean installed x pro (on top of an image which I had made last week of no adobe 9.0 at all). Knew about the upcoming x pro and so had kept an image with no adobe 9. Even with x pro, that image remains, and so if anything does not work, it is just a matter of going back and reinstalling adobe 9 pro through to 9.4.1 Hardly a matter of 20-30 mins. Frankly, the only visible diff in x pro is the faster loading time, which is accompanied by 32bit office addins not working on office 64 bit. Adobe 9 pro definitely improved in loading as one updated to 9.3... Once I got non-genuine with v 9.0 and could not open any pdf doc at all. I think I applied a leaked key on install. Updated to the latest version which I think was 9.3.2 at the time. Was caught and could not open any pdf doc. One final thing: at the time of x pro install on Tuesday, I applied a serial (posted by someone) which was accepted and also ran the activation blocker of version 9.0. That worked for me (no nags, etc) but will it work (at least till the first update comes out hopefully in Jan/Feb). The serial by itself works in install, but on a subsequent opening of adobe, got caught, even when auto update was disabled.
With my v9 installation, I never did modify the Host file and never "repatched" AdobeLM.dll after the initial install and I was always able to apply all updates manually. Not sure how or why... Maybe I was detected as non-genuine but Adobe doesn't prevent you from applying security updates anyway... Adobe does have a Patch Tuesday policy (same day as Microsoft) except it is quarterly, not monthly. They also release "out-of-cycle" security updates. Regards