Adobe Reader XI not ready for Vista?

I wonder why there is no Adobe Reader XI ready to download. Meanwhile I got it for XP-SP3 and Win-7. Waiting long time to get a reasonable actual version under linux is normal -- but Vista?
Sincerely -- O-M

I think "not ever" is more accurate than "not ready". There aren't enough people running Vista any more for Adobe to get excited about it.
Apparently, Reader XI works for some people, but Adobe didn't test it.
Or that's what I heard.

Similar Messages

  • Adobe Reader X not responding  in Vista

    Hi, it seems that Adobe Reader is either taking too much time to load certain PDFs n (especially Secured PDFs) or crashes. Vista gives that Reader was closed due to Data Execution Prevention. I have not encountered this problem with Reader 9 before. It was way quicker.
    And is it possible to open the same page after closing a particular document in Reader X , which was possible with Adobe Reader 9.
    Thanks

    Thank you, I was able to open Reader by itself and disabled Protected Mode, now
    it works.  I don't understand why but I am happy to be able to print docs from
    email again.
    Thanks! : )

  • Adobe Reader XI not working for me (Windows 7)

    I just installed adobe reader XI and now I can't open any PDF files. The application itself won't even start properly. The default window opens but then it completely shutsdown without any indication of why it did so. No error report or anything.

    I found the solution to the program itself not opening properly on another thread on this site.  See below:
    I spoke to a colleague about what was happening, and he had me reinstall Adobe Reader XI and attempt to start it.  I then navigated to the C:\Program Files (x86)\Adobe\Reader 11.0\Reader\ folder and double-clicked the Eula.exe. It displayed the End User License Agreement window and I clicked 'Accept'. After doing that I was able to start the Reader without issue and it all seems to be working fine now.
    The above worked for me and now Reader XI will open properly and stay open.  Hope this helps someone else.

  • Adobe, CS4 is not ready for release.

    Dear Adobe,
    I have been using Premiere as my primary editor for years (I think I started on version 6). Although some versions had flaws and the occasional crash, they were reasonably competant apps which did the job.
    CS4 is not. In the 24 hours since I installed it I have seen my first-ever Blue Screen of Death on my workstation (in 18 months of working day in day out). CS4 crashes about 50% of the time on start-up. It often takes the window organisation with it, so next time I start up I get a blank work window and have to reset to default to get anything back. Then it most likely crashes again. I've had more crashes in one day trying to edit one single video than I have had in all my previous years of using Premiere put together.
    CS3 runs stably on the same system, and still appears to do so. So please do not ty to make excuses about it being some other software installed on the system's fault. CS4 is buggy as hell and that's all there is to say. (I'm on XP, service pack 3, latest drivers for video cards recently installed to see if it fixed crashes, it does not. Dual core athlon, 4 GB of memory, 8800 GTS graphics card.)
    To cap it off, the new feature which I was most looking forward to, batch export, is also unreliable. It cannot export to H264 25 fps from my 25 fps Panasonic P2 DVC PRO HD original files - it stutters and has pure green frames everywhere. The export to WMV appears to have the wrong gamma, and have bad artefacts to boot, and is glacially slow. I was hoping to be able to get rid of the need for ProCoder 3, but Media Export is unusable for website production in this release.
    My other main workhorse, magic bullet looks, has been upgraded to version 1.2 to try to work with CS4. It worked with 4.0.0 raw off the CD, but now that I've updated to the latest release, it reliably crashes CS4 whenever I try to apply it to a clip.
    The ONLY saving grace of this release is that it does not appear to have messed up my CS3 installation, so I can still do some work.
    This is utterly unacceptable in any product, but especially in one bearing a "Pro" moniker.
    I was contemplating a new workstation to speed up workflow now that everything I have moved entirely to P2-based production. CS4 has given me the strongest possible impetus to look very closely at the Mac alternatives and Final Cut Pro.
    You seriously need to fix these issues, and on a timescale of weeks, not months, if you want to retain me as a customer.
    Hywel Phillips.

    Hi,
    I've contacted Adobe support as well now, thanks for the heads-up.
    I'm using an Nvidia 8800 GTS with latest drivers. The crashes were similar in frequency before and after the driver change, as I tried that as part of my bug hunting. Ditto latest version of DirectX 9. Windows XP SP3, Athlon 64 X2 dual core, 4 GB RAM.
    Looks 1.2 seemed to work with version 4.0.0 but reliably crashes the app when I try to apply it to a clip in 4.0.1. I will try reinstalling Looks afresh as I did the install before updating to 4.0.1.
    Slow AME: I had preview "on". Silly me, in Procoder 3 or Cleaner XL it made no significant difference to render times so I kinda hoped Adobe could code it thus. Apparently not. I probably had max quality ticked as well, if that's the default out of the box. I didn't use exporter in the old version to create MP4 or WMV files, I wrote an intermediate AVI file and used that to Procoder from, plus a P2 output render for archival. Those bits seem to work fine, but the AME output quality on the MP4 and WMV files is absolutely awful, compared with output with settings as near as I can tell are the same in Procoder 3. And Procoder 3 is probably a factor of 6-10 faster, especially for the WMV.
    Thanks to all for suggestions... and for knowing that I am not alone. The Final Cut Pro option is looking more and more attractive, given that I have someone else starting to share the work editing for me and I have to give him a working system somehow. CS4, on current performance, is literally unusable on my main system and so buying a machine to run it feels like a fool's errand (especially as I'd then have to contaminate the office which a copy of Vista, something I have thus far avoided!)
    Anyone know of any discussion/comparsions between Premiere Pro and Final Cut Pro? I'm guessing FCP doesn't have nested timelines, a neat feature but one which I think I can live without. It looks like FCP can finally deal with P2 input natively now, which was the big issue for me before. Can it do multicam, anyone know?
    Cheers, Hywel.

  • Reader XI not available for Windows Vista. Why?

    I have just tried to install Reader XI, but I keep being directed to Reader X. Looking at the Technical Specs. Windows Vista is not listed. An over sight? What is going on?

    I have Reader XI on my Win 7 office computer.  I have Vista on my home computer and tried different links to get to the Reader XI download page, but I too kept getting redirected to the X download page.
    When I found the "previous versions" page http://get.adobe.com/reader/otherversions/ I tried inputing different OSs (XP, Vista and 7) and discovered XI is not available for Vista.  Obviously the auto-redirect is due to Adobe.com detecting my OS.
    I'm not overly concerned.  I mean, ver X works fine for what I need it for at home.  The only reason I came here (to the forum) was to find out 'why'.

  • I bought an ebook but when I  try to download it I receive a message stating 'Adobe reader could not open .....acsm because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wa

    Can anyone assist me? I keep receiving this message when I download my ebook ''Adobe reader could not open .....acsm because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't decoded).'
    Much appreciated

    I think you should ask in the Digital Editions forum, Adobe Digital Editions

  • Help.  How do I fix this?  Have been using adobe reader opening this template for months and now all of the sudden its not working.Adobe Reader could not open 'NSCAAInteractiveSessionPlan.pdf' because it is either not a supported file type or because the

    I coach youth soccer and use a PDF template to save my sessions in.  Today I got this message when trying to open one of my sessions.
    Adobe Reader could not open 'NSCAAInteractiveSessionPlan.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).
    How can I fix this?  I have not done anything I don't normally do.

    What is your operating system?  Reader version?

  • Why can't I open a pdf file on my desktop?  I keep getting this message: Adobe Reader could not open '8pdk_96_4.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and w

    Why can't I open a pdf file on my desktop?  I have Adobe Reader and running OS 10.10.1  I keep getting the same message: "Adobe Reader could not open '8pdk_96_4.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded)."

    I tried that.
    I saved the file 8pdk_96_4.pdf to my desktop and tried to open it using Adobe Reader but I get the same message: Adobe Reader could not open '8pdk_96_4.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

  • I keep getting an error on my MAC when i try to open any and all JPG FILES.  How do I correct  Adobe Reader could not open 'images rest 12-4.jpg' because it is either not a supported file type or because the file has been damaged (for example, it was sent

    Adobe Reader could not open 'images rest 12-4.jpg' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).
    that is the message how do i correct this problem

    It sounds like your file associations are messed up and Reader is trying to open your .jpg files. Is this correct?
    If so, you just need to change the associations to choose what application opens them. Here's how: Change File Associations in Mac OS X

  • Hi, I have a MacBook Air and try to save and open pdf document but receive this message: Adobe Reader could not open 'aw14lookbook.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an ema

    Adobe Reader could not open 'aw14lookbook.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

    Most likely http://helpx.adobe.com/acrobat/kb/pdf-error-1015-11001-update.html

  • After saved to computer, Adobe Reader could not open 'filename.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

    After saved to computer, Adobe Reader could not open 'filename.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

    What is your operating system?  Reader version?
    Saved from where?  What is the file size of the saved document?

  • Adobe Reader could not open 'Firefox 4.0-2.dmg' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

    Tried to download Firefox 4 for Macintosh three time and could not prevent Adobe Reader from interfering.

    The following document should help: Error: Adobe Reader could not open '*.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and was not correctly decoded.)
    Please update this thread if your issue is resolved.
    Thanks,
    Shashi

  • Using Maverick, error message: Adobe Reader could not open '***.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

    Receiving error message using current Maverick version: "Adobe Reader could not open '***.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).".  Is fix the same as on previous OS versions?

    Back up all data before making any changes. Please take each of the following steps until the problem is resolved.
    Step 1
    If Adobe Reader or Acrobat is installed, and the problem is just that you can't print or save PDF's displayed in Safari, you may be able to do so by moving the cursor to the the bottom edge of the page, somewhere near the middle. A black toolbar should appear under the cursor. Click the printer or disk icon.
    Step 2
    There should be a setting in its preferences of the Adobe application such as Display PDF in Browser. I don't use those applications myself, so I can't be more precise. Deselect that setting, if it's selected.
    Step 3
    If you get a message such as ""Adobe Reader blocked for this website," then from the Safari menu bar, select
    Safari ▹ Preferences... ▹ Security
    and check the box marked
    Allow Plug-ins
    Then click
    Manage Website Settings...
    and make any required changes to the security settings for the Adobe PDF plugin.
    Step 4
    Triple-click anywhere in the line of text below on this page to select it, the copy the selected text to the Clipboard by pressing the key combination command-C:
    /Library/Internet Plug-ins
    In the Finder, select
    Go ▹ Go to Folder
    from the menu bar, or press the key combination shift-command-G. Paste into the text box that opens by pressing command-V, then press return.
    From the folder that opens, move to the Trash any items that have "Adobe" or “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari.
    Step 5
    The "Silverlight" web plugin distributed by Microsoft can interfere with PDF display in Safari, so you may need to remove it, if it's present. The same goes for a plugin called "iGetter," and perhaps others—I don't have a complete list. Don't remove Silverlight if you use the "Netflix" video-streaming service.
    Step 6
    Do as in Step 4 with this line:
    ~/Library/Internet Plug-ins
    If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari.

  • Adobe Reader could not open 'cpd39346.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

    I use a Macbook Pro w/ OS X.  I am unable to open a .pdf file downloaded from the internet, Adobe always shows "@Adobe Reader could not open 'cpd39346.pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

    Are you trying to open a pdf within a browser (clicking a link)? If so, which browser?

  • I have adobe reader 11.0.09 for windows 7 pdf are opening but minimize and close icon  are not showing

    please help

    Solution found. By enabling a lockdown feature, we prevented Adobe from trying to muck about getting online. Actually NSA provides recommendations on how to lock down Adobe Reader, google "NSA recommendations for configuring Adobe Reader XI in a Windows Environment". We only used:
    HKLM\Software\Policies\Adobe\<product>\<version>\FeatureLockDown\cCloud
    bDisableADCFileStore                    REG_DWORD               Set to 1

Maybe you are looking for